New Grib Presentation

[rgleason]

Then I tried
GFS20140513154304278-3-6-12hr.grb.doc (23.8 KB, 0 views)

using the same
weather_routing_p from about v3.3.1618 and grib_pi from v3.3.1418
and setting up four different routings in wx-rte with 3hr, 4hr, 6hr and 12 hr intervals with same boat specs & polars, and start and finish.

These seem to fail too.

[rgleason]

I've had to recreate the routing and Climatology is Grey checked in Wx-Rte. There seems to be no way to get it unchecked. Why? I don't have Climatology loaded or in the directory. This causes an error every time I compute.

Ok, I added Climatology back to plugins and loaded it and the greyed out checkbox now became accessible and I could uncheck climatology.

If this box is greyed out, I think it should not be functional and not cause an error.

[rgleason]

Similar results from
GFS20140513162104482-3-6-12-moving.grb.doc (23.3 KB, 0 views)

12hr failed.
6hr grib failed
4hr grib failed.
3 hr grib failed.

[rgleason]

The next set of tests uses:
grib_win32_pi_v22_ov331712_compiled-5-13-14_pi.dll
weather_routing_win32_pi_v_ov331618_pi.dll (same one as before)
with compiled release version of Opencpn 3.3.1712

First using
GFS20140513161004424-3hr.grb.doc (59.8 KB, 0 views)
Grib Failed for 12hr, 6hr, 4hr, and 3hr.

GFS20140513154304278-3-6-12hr.grb.doc (23.8 KB, 0 views)
Reset all
Grib Failed for 12hr, 6hr, 4hr, and 3hr.

GFS20140513161204438-3hr-moviing.grb.doc (58.6 KB, 0 views)
Reset all
Grib Failed for 12hr, 6hr, 4hr, and 3hr.

GFS20140513162104482-3-6-12-moving.grb.doc (23.3 KB, 0 views)
Reset all
Grib Failed for 12hr, 6hr, 4hr, and 3hr.

[seandepagnier]

I think we established that interpolate mode does not work for moving gribs, and also weather routing does not work for them at this moment.

[rgleason]

Yes, I believe so, my last sequences all failed, although earlier I did have wx-rte with the earlier grib_pi3.3.1418 working (with Opencpn.exe 3.3.1618) and I do not know what has changed. Perhaps it is due to the newer Opencpn.exe v3.3.1712? -Hard to believe.

[rgleason]

After my 5 hour session this morning, I had to go back to it...
Using
grib_win32_pi_v22_ov331418.dll
weather_routing_win32_pi_v_ov331618_pi.dll (same one as before)
with compiled release version of Opencpn 3.3.1618

with
GFS20140513161204438-3hr-moviing.grb.doc (58.6 KB, 0 views)

We got partial routings!

12 hr "failed" no routing at all
6hr "grib failed" - partial routing (shown in attached screen, was the longest)
4hr "grib failed" - partial routing (shorter)
3hr "grib failed", - partial routing (shorter)

See attached please. -So what is it about grib_pi v3.3.418 that allows it to work at least partially, and what would allow it to complete?

[rgleason]

Using
grib_win32_pi_v22_ov331418.dll
weather_routing_win32_pi_v_ov331618_pi.dll (same one as before)
with compiled release version of Opencpn 3.3.1618

We got complete routings!

12 hr "complete"
6hr "complete"
4hr "grib failed" - no routing
3hr "complete"

See attached please. -So what is it about grib_pi v3.3.418 that allows it "complete" on three (not on 4 hours) when you have a simple (3 hour interval only) grib?

with
GFS20140513161204438-3hr-moviing.grb.doc (58.6 KB, 0 views)

[rgleason]

Using
grib_win32_pi_v22_ov331418.dll
weather_routing_win32_pi_v_ov331618_pi.dll (same one as before)
with compiled release version of Opencpn 3.3.1618

We got partial routings!

12 hr "grib failed"
6hr "grib failed"
4hr "grib failed" - no routing
3hr "grib failed"

See attached please. -So what is it about grib_pi v3.3.418 that allows it partial routings on three (not on 4 hours) when you have a non-moving (3 hr, 6hr, 12 hr intervals) grib?

with

GFS20140513154304278-3-6-12hr.grb.doc (23.8 KB, 0 views)

[rgleason]

Using
grib_win32_pi_v22_ov331418.dll
weather_routing_win32_pi_v_ov331618_pi.dll (same one as before)
with compiled release version of Opencpn 3.3.1618

We got complete routings!

12 hr "complete"
6hr "complete"
4hr "grib failed" - no routing at all!
3hr "complete"

with
GFS20140513161004424-3hr.grb.doc (59.8 KB, 0 views)

See attached please. -So what is it about grib_pi v3.3.418 that allows it complete on three weather_routing intervals (but not on 4 hours) when you have a simple non-moving 3 hr interval grib?

THIS IS USING THE EARLIER GRIB v3.3.1418

[rgleason]

So, this morning, to summarize. What works is:
Weather_routing_pi v3.3.1618
Grib_pi v3.3.1418
Grib files that have a single interval, such as 3hrs.
Grib files that have a single interval and are moving or walking.
Under these conditions weather_routing is works.

--Notes
It appears that the weather_routing interval set at 4 hours is problematic.

Sometimes other multiple grib intervals (eg 3hrs for 2days, then 6hrs for 2 days, etc) combined with some weather_routing interpolated interval will cause Opencpn to crash and send a report, (always using Grib_pi v3.3.1712) and sometimes even wipe out the weather_routing settings file. This does not happen all the time and I have not reliably been able to repeat the conditions, but it does happen fairly frequently with certain settings, otherwise you will actually get some partial runs as I have shown above.

I agree with Sean, there are two problems:

1. Grib_pi letting weather_routing interpolate to its hearts desire without messing up the grib user interface.

2. Weather_routing_pi needs the ability to handle what I call multiple interval gribs which have this kind of interval setup:
3hrs until 48 hours (48/3=16 <--must be integer)
6hrs until 72 hours ( (72-48)/6= 4 <--must be an integer)
12hrs until 168 hours or 7 days ( (168-72)/12= 4 <--must be an integer)

3. Weather_routing needs the ability to interpolate multiple interval grib files.

4. Grib_pi needs to allow Weather_routing to interpolate multiple interval grib files.

5. Weather_routing needs to handle moving gribs with multiple intervals as it does single interval moving gribs.

6. Weather_routing needs to provide an error message when the walking grib area does not correspond with the calculated boat location with a short message such as
"Moving grib area failure" or something else with better description.

This may be simple to do, a one liner as Pavel says, but I think it is a bit more than that because this is not that simple a problem.

The grib_pi v3.3.1418 is working much better than the current one.

[rgleason]

The current beta grib_pi v3.3.1713
1. Shows a message when loading a moving grib, that it cannot be interpolated.
2. Does not turn off interpolation if it is on.
3. Does not show all frames of the grib, skips many, showing nothing, both with interpolation checked and off.

Comment: It is certainly possible to interpolate between two moving gribs.
You would find the overlapping area and do the interpolation on that area. It would involve more math and more time, but it is certainly possible. In fact this is probably what Sean does with weather_routing does to interpolate moving gribs.

This would leave an border area that was not interpolated and if the boat's route ends up in that zone, there would be a failure (for weather_routing) in the calculation of some sort.

[rgleason]

The current beta grib_pi v3.3.1713 works well on non-moving gribs
-3hr simple interval,
-3hr,6hr,12hr multi interval.
I slowed the interval down to 1 per second and it works fine.

Moving gribs are hit and miss with interpolate checked and with it unchecked.
There is a message when an moving grib is loaded

It should be possible to interpolate a moving gribs overlappping area.

[CarCode]

When zooming the chart with zyGrib one will get more and more wind arrows (smaller distance between arrows).
Several users and myself wants to have the same feature for the grib plugin.

[Baikal]

Originally Posted by CarCode

When zooming the chart with zyGrib one will get more and more wind arrows (smaller distance between arrows).
Several users and myself wants to have the same feature for the grib plugin.

Join wishes
+1