New Grib Presentation

[Ptizef]

Originally Posted by rgleason

When I turn off pressure it particles still freezes.

Also when I uncheck pressure in the expanded menu, it does not turn off pressure. I have to go into settings to turn off pressure this is not as intended.

Thanks Sean.

Rick, Sean

I tested the file with my weak netbook under windows 8.1
Without particles it run without any problems
With particles, O freeze after three or four time steps maximum
For me it's clearly particles which create the freeze.
I have given up for a while to use this option on my small device as it is very power demanding

a remark Dirk : don't' forget there is an option in the settings to make "always visible" the pressure isobars. If this parameters is set, the expanded menu will never hide it. I you don't want this behaviour, just uncheck this parameter

Jean Pierre

[Ptizef]

Originally Posted by cagney

I'm missing one little thing. The ability to display 500 mb contour lines, similar to what normal 500 mb wx charts display. This will help understand patterns and future developments. It should be possible to display 500 mb contour lines and surface isobars at the same time.
Thomas

Hi Thomas

sorry for my misunderstanding but what do you mean exactly by 500 mb contour lines ?
it's possible to display surface isobars but that would imply mixing 500 mb and surface data ?

Thanks
Jean Pierre

[Ptizef]

Originally Posted by CarCode

I agree however the last commits of Ptizef are a little bit buggy when compiled for Mac OS X and so I have to make here some changes to make them run as intended.
Gerhard

Gerard

It would be very useful for all to know what changes you have to made and for which bug
With Windows and Linux as far as I know it work as expected

thanks
Jean Pierre

[CarCode]

Originally Posted by Ptizef

Gerard

It would be very useful for all to know what changes you have to made and for which bug
With Windows and Linux as far as I know it work as expected

thanks
Jean Pierre

JP,
reading your post #436 above it seems not to run with Windows as expected however.
Because I use wxWidgets 3.1.0 and Mac OS X Yosemite with Xcode 6.3.2 my changes are especially for this environment and therefore of no importance for others. Some examples:

- The values odc.m_dParticleDensity = 4.0*exp(m_sParticleDensity->GetValue() / 2.0 - 3);
and
m_sParticleDensity->SetValue(2.0*(log(odc.m_dParticleDensity/4.0) + 3));
don't work here and has been changed simply to
odc.m_dParticleDensity = m_sParticleDensity->GetValue();
and
m_sParticleDensity->SetValue(odc.m_dParticleDensity);

- In function void GribSettingsDialog::SetSettingsDialogSize() the size values or variables makes no sense here and was changed.

- To avoid asserts sizer flags was changed or deleted. This is mostly:
Horizontal alignment flags are ignored with wxEXPAND.
Horizontal alignment flags are ignored in horizontal sizers.
Vertical alignment flags are ignored in vertical sizers.

- I still have a problem not solved with wxSlider. Only the values min, max and actual of ParticleDensity slider are shown in data settings windows where no particle data is and slider, checkbox and text is therefore correctly hidden. Seems to be a bug of wxWidgets and I have to dynamically change the flags of wxSlider to suppress the shown value text.

Gerhard

[Ptizef]

Thanks Gerard
JP

[rgleason]

Jean Pierre

Dirk : don't' forget there is an option in the settings to make "always visible" the pressure isobars. If this parameters is set, the expanded menu will never hide it. I you don't want this behaviour, just uncheck this parameter

Yes, thank you. I forgot.

I agree that what freezes is the Particles function.

It freezes on my Dell Inspiron XPS L502x Laptop which is actually pretty powerful, most powerful one I have. Intel i7-2720qm cpu at 2.20 ghz with 8 gb ram All the hardware passes diag tests recently. Using the Nvidia Graphics Geforce GT 540M card rather than the Intel HD, this is set in the Nvidia program for particular software to use Nvidia card.

I do not recall it doing that before.

[CarCode]

JP,

by the way a similiar bug is in Dave's Mac version 4.1.602 in Options window (see image). This was not in Dave's Mac version 4.0.0 because there was no such hidden sliders.

So it is an old bug in wxWidgets in the way wxSlider is deactivated in Mac OS X because Dave uses wxWidgets 3.0.2 and I use 3.1.0.

Gerhard

[CarCode]

Originally Posted by CarCode

So it is an old bug in wxWidgets in the way wxSlider is deactivated in Mac OS X because Dave uses wxWidgets 3.0.2 and I use 3.1.0.

I just found out this wxWidgets bug is known since 3 years for Mac OS X and has never been fixed nor exists any workaround.

Gerhard

[rgleason]

Very interesting Gerhard, there is definitely a problem because it has frozen on 4 out of 5 grib files now and I can get it to repeat. It happens on bigger files I think. To me it feels like it is running out of memory or there is some memory leak. I've tried different # days 4, 8, 16 and different resolution and data, lots of data and less data, and that does not seem to make a difference. The file that did not crash opencpn was on the small side (3 days).

Particles crashes Opencpn 4.1.602 if there are enough grib frames.

[CarCode]

Rick,
this has nohing to do with the wxSlider bug for Mac OS X.
Gerhard

[seandepagnier]

Originally Posted by rgleason

Very interesting Gerhard, there is definitely a problem because it has frozen on 4 out of 5 grib files now and I can get it to repeat. It happens on bigger files I think. To me it feels like it is running out of memory or there is some memory leak. I've tried different # days 4, 8, 16 and different resolution and data, lots of data and less data, and that does not seem to make a difference. The file that did not crash opencpn was on the small side (3 days).

Particles crashes Opencpn 4.1.602 if there are enough grib frames.

Can you see how much ram opencpn is using while you make it crash? Maybe the particles leaks memory.

Are you saying it crashes with gribs with lots of time slices, but not if there is only one slice despite the area the grib covers? Can you post the file that is most easy to make it crash, what do you need to do?

[seandepagnier]

Originally Posted by rgleason

Very interesting Gerhard, there is definitely a problem because it has frozen on 4 out of 5 grib files now and I can get it to repeat. It happens on bigger files I think. To me it feels like it is running out of memory or there is some memory leak. I've tried different # days 4, 8, 16 and different resolution and data, lots of data and less data, and that does not seem to make a difference. The file that did not crash opencpn was on the small side (3 days).

Particles crashes Opencpn 4.1.602 if there are enough grib frames.

Can you see how much ram opencpn is using while you make it crash? Maybe the particles leaks memory.

Are you saying it crashes with gribs with lots of time slices, but not if there is only one slice despite the area the grib covers? Can you post the file that is most easy to make it crash, what do you need to do?

[Baikal]

Originally Posted by boat_alexandra

Can you see how much ram opencpn is using while you make it crash? Maybe the particles leaks memory.

Are you saying it crashes with gribs with lots of time slices, but not if there is only one slice despite the area the grib covers? Can you post the file that is most easy to make it crash, what do you need to do?

Record video from the screen as this error occurs and how much memory uses
https://www.dropbox.com/sh/8mgecd365...Ex9xFcBta?dl=0

[seandepagnier]

Baikal,

Thanks for the video, but with my connection I cannot access it.

[CarCode]

Originally Posted by CarCode

I just found out this wxWidgets bug is known since 3 years for Mac OS X and has never been fixed nor exists any workaround.

Gerhard

I was on error, this bug exists since 10 years already for the Mac port of wxWidgets and not since 3 years.
Igor has made a patch now for wxWidgets bug#2388 and so there are only 387 other bugs left now for the Mac port. Delete the .doc extension.

Gerhard