Turn-Your-Head Approach for IsoBased algorithms GSoC 2026

[azad2003-ai]

issue:
Route segments that cross land or other constraints are omitted from routing without replacement. This leads to depletion of routes in complicated environments.

e.g. rotate route segment by some degrees until it is in the water; chose direction on a random basis

FROM python:3.13

Update system dependencies

RUN apt-get update
&& apt-get upgrade -y
&& apt-get dist-upgrade -y
&& apt-get clean
&& apt autoremove -y
&& rm -rf /var/lib/apt/lists/*

WORKDIR /app

COPY ./WeatherRoutingTool ./WeatherRoutingTool

COPY ./pyproject.toml ./requirements.txt ./requirements-without-deps.txt ./cli.py ./

RUN pip install . && pip install --no-deps -r requirements-without-deps.txt

ENTRYPOINT [ "python", "/app/cli.py",
"--file", "/app/wrt_work_dir/config.json",
"--info-log-file", "/app/wrt_work_dir/logs/info.log" ]

[ashoknarayan]

Hi @azad2003-ai, thanks for opening this issue.
I’m interested in contributing incrementally towards this.

I plan to start by adding tests that capture the current route depletion behavior when segments intersect land, followed by a small refactor to make recovery strategies pluggable (keeping default behavior unchanged).

Once that’s in place, I’d like to prototype a minimal deterministic “turn-your-head” recovery approach behind a feature flag.

Please let me know if this sounds reasonable or if there’s a preferred starting point.