Weather Routing

[rgleason]

Sean, I thank you for being persistent!

[seandepagnier]

Could you pull the grib enhancements branch.. I think that had the needed changes not weather routing

[rgleason]

Ok willl do right now, just saw this.

[rgleason]

That did it.

git pull sean grib_enhancements

Will compile next

C:\Data-Dart\Up-Soft\Navigation\opencpn-git>git fetch --all
Fetching origin
Fetching sean
Fetching ptizef

C:\Data-Dart\Up-Soft\Navigation\opencpn-git>git branch -a
  master  
  origin/master
* sean/grib_enhancements
etc
  remotes/sean/grib_enhancements
  remotes/sean/master
  remotes/sean/stable

C:\Data-Dart\Up-Soft\Navigation\opencpn-git>git pull sean grib_enhancements
From git://github.com/seandepagnier/OpenCPN
 * branch            grib_enhancements -> FETCH_HEAD
Updating 793cb26..5561ed9
Fast-forward
 include/gshhs.h                      | 6 +++---
 plugins/grib_pi/src/GribUIDialog.cpp | 2 ++
 src/gshhs.cpp                        | 2 +-
 3 files changed, 6 insertions(+), 4 deletions(-)

[rgleason]

Did the git pull then did git clone for weather_routing for good measure.
I can see its getting there.

[cagney]

The latest code compile OK on Kubuntu amd 64 12.10.
I had a crash i the middle of creating a ~400M route.

route.png Views: 283 Size: 90.2 KB ID: 58941" style="margin: 2px" />

Thomas

[PjotrC]

Originally Posted by rgleason

What are those columns that you'd like?

Also do you find the Tree view for Gribs useful, or would it be okay to just have a drop down selector with a button to browse to a new directory?

In principle I could do without the GRIB Control Dialog at all. Anyway, it might start as minimized, always selectiing the first (or closest to current time) GRIB record from the newest file in the configured directory.
I usually view the GRIB data as tabular columns in the Route Properties, and I view the GRIB chart by selecting a waypoint in the waypoints list for the route. The "Sync to Route" feature then ensures that GRIB barbs shown correspond to the ETA of the selected waypoint. I can step waypoint-by-waypoint to examine the situation.
This is usally more convenient than stepping through GRIB records via GRIB Control, but not always.

Please note that this is still the Route Properties Dialog, so it does center the chart on selected waypoint, and continuously adjusts everything properly for the Active Route...

What columns to include? Generally - as few as possible, to minimize space taken by the dialog. I think this means what I have now:

- waypoint name
- leg distance
- ETA (including daylight status)
- Nearest tide event, if tides enabled
- Speed for the leg
- Wind forecast for next leg (including point-of-sail info)
- Sea current for next leg (with drift effect info), if enabled

Drift column includes 4 values:
- sea current speed in knots
- sea current direction
- net speed effect on boat in knots (+ or -) along route leg
- net set effect on boat's course (e.g. if boat speed=0, this equals sea current direction)

whatever is available next is nice to have:

- precipitation (if not shown on GRIB chart as shading)
- sea state forecast for next leg

If I would program this again today, I would consider the following improvements:

- I would extend dayligt status info to include moon phase
- I would display tide status as relative e.g. HW+3 or LW-1, instead of giving time of nearest HW or LW
- maybe I would show the speed for next leg, instead of speed for past leg
- maybe I would change the method of calculation for sea current effect

I attach another example, showing use of combined wind and sea current GRIB (from a previous test version).

For long distance planning, I could do with 12 static monthly wind and sea current GRIBS, with data just as in the pilot charts.

To view precipitation properly, I have now to use Ugrib...

Good luck in your work!

P.

[rgleason]

Maybe I should just go find something to run Linux that would be good for the boat!
Pjotrc are you another talented programmer, having built your own system?
Thomas why does it always seem so simple for you guys?
I can see Sean has been very patient with this effort.
I'm going to try to figure out what is causing the problem here.

[seandepagnier]

Originally Posted by rgleason

Did the git pull then did git clone for weather_routing for good measure.
I can see its getting there.

I tried something else, maybe it works on windows now. Need both branches.

Originally Posted by cagney

The latest code compile OK on Kubuntu amd 64 12.10.
I had a crash i the middle of creating a ~400M route.
Thomas

Thanks for the report.. First of all.. go into configuration and uncheck inverted routes (the bug is somewhere with that and it's relatively complex logic) It only really applies if you route around and island and reach the back side after the routes from either side meet up. Hopefully you can make routes without crashing now.

As for fixing it, I need to be able to reproduce it. Due to the complexity of the algorithm (look at routemap.cpp) I cannot determine the reason from a line number. The actual bug is probably in a completely different place. Could you give me the starting position, lat/lon, and what boat you used (boat.xml from ~/.opencpn/boat.xml) and and what degree steps. Also if you loaded a csv polar I would need that as well. Also the grib file used and starting time.

I don't get any crashes so I am wondering if this is because of 64bits.

Originally Posted by PjotrC

In principle I could do without the GRIB Control Dialog at all. Anyway, it might start as minimized, always selectiing the first (or closest to current time) GRIB record from the newest file in the configured directory.
I usually view the GRIB data as tabular columns in the Route Properties, and I view the GRIB chart by selecting a waypoint in the waypoints list for the route. The "Sync to Route" feature then ensures that GRIB barbs shown correspond to the ETA of the selected waypoint. I can step waypoint-by-waypoint to examine the situation.
This is usally more convenient than stepping through GRIB records via GRIB Control, but not always.

So, whatever point is selected in the list, it draws everywhere grib data at that time? I thought it might be interesting to draw the wind barbs according to the route map so you can see the wind over the whole passage as it would occur.. so wind barbs change in time and space.. but some people may find this confusing. In any case, with the current timeline slider, it draws the position along the route as the grib changes.

Please note that this is still the Route Properties Dialog, so it does center the chart on selected waypoint, and continuously adjusts everything properly for the Active Route...

So you mean the route properties already in the main program? There is currently no correct way for a plugin to communicate with the route properties dialog

What columns to include? Generally - as few as possible, to minimize space taken by the dialog. I think this means what I have now:

- waypoint name
- leg distance
- ETA (including daylight status)
- Nearest tide event, if tides enabled
- Speed for the leg
- Wind forecast for next leg (including point-of-sail info)
- Sea current for next leg (with drift effect info), if enabled

Drift column includes 4 values:
- sea current speed in knots
- sea current direction
- net speed effect on boat in knots (+ or -) along route leg
- net set effect on boat's course (e.g. if boat speed=0, this equals sea current direction)

whatever is available next is nice to have:

- precipitation (if not shown on GRIB chart as shading)
- sea state forecast for next leg

If I would program this again today, I would consider the following improvements:

- I would extend dayligt status info to include moon phase

Maybe integrate with celestial plugin to get this data..

- I would display tide status as relative e.g. HW+3 or LW-1, instead of giving time of nearest HW or LW
- maybe I would show the speed for next leg, instead of speed for past leg
- maybe I would change the method of calculation for sea current effect

Yes, well ultimately the user should be able to select which columns they want.

I attach another example, showing use of combined wind and sea current GRIB (from a previous test version).

For long distance planning, I could do with 12 static monthly wind and sea current GRIBS, with data just as in the pilot charts.

Do you have these gribs available? I would like to experiment with them.

To view precipitation properly, I have now to use Ugrib...

Good luck in your work!

P.

Precipitation is supported in the new grib plugins

[rgleason]

Sean It compiled! I'm psyched. I've started a grib file. (Should it be agrib starting now and running into the future-?)

Then brought up Weather_routing. Pretty darn neat! Everything is there.

I've put to boat inside the grib area. Tried hitting start even though it does not have a destination and it fails. What am I doing wrong here?

Thanks for your perseverance!

[rgleason]

Sean I hate to do this to you....
I picked an old Grib and brought it up. Then move the boat within the grib area.
Then set a destination for the boat, go to here (with right click).

Then I brought up Weather_routing. And picked start.
Shortly I got many messages saying it had computed the course, one right after another. I selected Break and copiied the Call Stack.

I am sure it is something I've done wrong.

THIS IS COOL I'm so excited! I'm going to keep banging away at it.

[rgleason]

Got it running isochrones. Then a small step error and it could not complete.
Some images and a call stack.

[rgleason]

After, above, hit continue. Shows this --almost like a fence was drawn so it would not compute isochrones towards the "goto" point, but the macro is still running...

[rgleason]

Moved goto so it was a direct route to it without going around any land, hit reset and Start. It still did not seem to want to calc out to Nantucket, and then the compute window came up.

[rgleason]

I got it to complete a route out into the atlantic.
When it completed I got multiple Computation complleted. Destination Reached.
Could hit break, take Call stack.
Hit Continue, breaks by itself, Tack call stack.
So there are two files.