Post by iconPost by nsp | 2017-12-13 | 12:11:16

I just saw some weird stuff in + 18hours in zezo. there's significant diferences in wind direction As an example 46º 17,8 S 43º 56,2 E.

Something that is out of control, or it results from the new charts versus old interpolation?

commenticon 11 Comments
Post by iconPost by nsp | 2017-12-13 | 12:12:23
Differences of 15�TWD and also in TWS
What i mean is differences between the values in the projected route and the ones in the area at that exact moment.
Post by iconPost by zezo | 2017-12-13 | 12:27:49
Please check in 5 minutes.
Post by iconPost by nsp | 2017-12-13 | 12:56:49
Differences increased:
35º TWD
9 knts TWS

Impossible to do the projected route
Post by iconPost by zezo | 2017-12-13 | 13:11:48
The wind data in the chart (numbers at the cursor) is not interpolated, so it's only exact at 3-hour intervals - on the dark isochrones and exactly between them. For every other black dot you'll see a difference because the router interpolates the wind and the user interface does not.

But the track tool does too, so it generally matches the server-side track.

I should fix it and save me a ton of time answering this question, same probably goes for the VR interpolation method.
Post by iconPost by nsp | 2017-12-13 | 13:11:23
i saw your answer in the other thread :)

but it increased..

I understand what is interplation Cvetan, but when zezo "designs" a rooute it has into consideration the interpotated data,

sooooooooo...the numbers should be the same in the chart and in the boxes of the several points of your route. the point in my route at 18 hours has a diference of 35º in twd related to the chart.And also 9knts in TWS. so intead of being there at 135 I will be at 100 twa which means that all route could be wrong in this moment.

And it's the first time i see this kind of difference.
Post by iconPost by zezo | 2017-12-13 | 13:23:04
There are no differences in stable wind field, like the trade winds in Leg 2 for example. With a rapidly moving and developing low pressure system you can expect to see huge differences between subsequent GFS outputs (and between weather conditions 3 hours apart)

Similar for the center of a high-pressure system where the wind direction will vary wildly (speed has lower bound of 4kts, as we know)
Post by iconPost by MichelleWhy | 2017-12-13 | 13:12:23
I'm a bit lost now. The router showing GFS:6z just now and an hour too early?!
Post by iconPost by zezo | 2017-12-13 | 13:16:39
GFS 6Z is ready at 11Z. See this

6Z is the moment of the starting conditions snapshot/start of the run, then it takes 5 hours to crunch the numbers. There are several explanations in the forum.
Post by iconPost by MichelleWhy | 2017-12-13 | 13:24:19
Must be tired of reading all this stuff with the wrong data, sorry Cvetan. It confused me quite a lot. I was sure the update was 12z. Thanks for the clarification.
Post by iconPost by zezo | 2017-12-13 | 14:53:32
It's partially my own fault. I should probably get everything in sync and minimize the number of support calls, but:

- I have to divide my time between real life and the game. And then in the game between router development, all kind of non-router tech support and political discussions.

- As I just explained in another topic, I can only get the winds in sync with the official VR client, not with the VR server. And there is visible difference between those two at times, with the server being closer to the router than to the client. Which will still raise support questions because I can't match two sets of data simultaneously.
Post by iconPost by nsp | 2017-12-13 | 13:28:13
Ok Cvetan. Thank you, I was kind of seeing me heading into the hellhole in a really bad angle.

Topics list
Copyright 2009 by ZEZO.ORG. All Rights Reserved.