(This example follows on from the previous Combined topic.
Each day, while on passage, you will be updating your vessels current location by creating a new position report, downloading new weather data, and updating your weather routes.
Here is an updated position report, following on from the previous page.
Note that the actual position is not exactly on the isochronal weather route. Neither the weather forecasts, or the model of the vessels performance (polar diagram) will exactly match reality. Close is about all you can expect. This is a good match.
If the position report was far off the projected path, then you could evaluate if adjusting the polar diagram would be warranted. You will want to iterate slowly, over time, making improvements to the polar diagram.
After downloading fresh weather data, a new weather routing solution space was created. This is now showing a different solution from the previous days routes.
With this new weather data, the system is now calculating that there is a better route to the target point used in the previous example. Here is a second image with the cursor closer to the strategic route:
This highlights that, all we can do is make the best tactical decisions we can, at the time, with the best data and algorithms available. Weather forecasts change over time, and always contain uncertainty. This is just the way it is. This forecast is showing a patch of light wind has moved north from the previous forecasts. This has pushed the optimized route north, into stronger winds.
Using the new weather forecast data, the newly optimized route is suggesting that it is time to jibe. Both of the above paths have roughly the same short term path. This is, again, ideal. We can follow that short term tactical path, download fresh data the next day and make a new set of decisions at that point.
There is an important point which should be noted. Based on the previous days weather forecast, we made the best decision we could at the time. Now, with fresh data, 24 hours later, we see that it is time to change the plan and jibe. What we don’t know is: was there a better route that we missed? Updating your weather data more frequently when in areas where the weather systems are changing rapidly is encouraged.
After analyzing the full solution space, just as before, an intermediate target is created and the solver run again to generate a path.
This new path can now be associated with the vessel again:
When you attach a weather routing path to a vessel, the system first looks to see if the vessel is currently following a weather route. If it is, then that route is updated to reflect the new path.
If the vessel is not currently following a weather route, then a new route is created, initialized with the points from the solvers path, and then the vessel is modified to follow this new weather route.
If you want to save the current weather routing path associated with a vessel, before attaching a new path, open the vessel editor and change the First, follow weather route menu to indicate None. In doing this, when you attach a new weather route to the vessel, a new route will be created.
You may want to create more than one weather route in this manner, if you want to have a small number of historic routes to compare. Perhaps you end up with two routes, and alternate between them. This would let you always see the current optimized path and the previous days.
If you make a mistake along the way, remember that undo is available to you.
LuckGrib Weather Routing is currently only available on macOS. Support for iOS and iPadOS is under development.