Bulletin Board

hello,

i am a problem with importation NOAA grid
i haven't the same wind in Vrtool and in virtual regatta

for example, in vrtool the wind is : 5.6N and 164° and in virtual regatta, i have : 5.4n and 164°.
in the next square, i have more diffenence. 7.4noeud in vrtool and 6.5 in regatta !!

what is the problem ? can you explain ? i never have the same speed valors between regatta and vrtools but the angle are always good !

thank you

sorry for my poor english, i'm french !!

hum. yeah.. seems to differ from normal game wind schedule
Not sure how
http://www.tecepe.com.br/wiki/index.php?title=NOAAWinds

Just newly user and registered.
Really impressive tool.

Angles are always accurate against VR, only speeds have a difference that looks like a rounding discrepancy :

I did a calculation base on row degrib data.
u = -1.25m/s
v = 1.74 m/s

VR gets 4.3 Nds / 144°
VR Tools gets 3.7 Nds / 144°

Using u=-1 m/s and v=2 m/s you get 4.3 Nds like VirtualRegatta !!!!

don't know how to change this (currently using "game windspeed rounded" option in degrip import config....). will test the other options and keep you posted.

regarding wind speed calculations.
from NOAA, you get u and v components of speed in m/s
to get VR values from NOAA, you need to apply the following :
calculate speed in km/h : x=sqrt(u*u + v*v) * 3.6
round it at 1 km/h : y=int(x+0.5)
convert to Nds : z = y / 1.852
round to 0.1 Nds : int(10*z+0.5)/10
compared this with 30-40 various cells and it works

As far as I know, VR is calculating in km/h, then 'y' should be used for calculations and final for display purposes.

Hope Omar could implement in a future release

Thanks Omar for VRTool

Berg, I case of game winds (rounded), U and V components are converted
to wind speed (in km/h) and direction in degrees. The wind speed is rounded
to the nearest integer, and converted to knots.
I don't see where this method differs from the one you describe...

Omar,
I think the difference comes from when you make the rounding.
It looks like VR make km/h rounding after calculating square root of u and v, if you make it before you do not get the same result. The difference is small (up to 0.2-0.3Nds) but visible.

Ok Berg. I found the problem. It was not in the rounding itself,
but there was another bug

Version 2.09 will correct this soon. Thanks for the help

You are welcome Omar.
Happy to be for some little help.