discrepancy between twa from ploted line and recomendation
Post by iconPost by L1 | 2017-03-19 | 19:08:56

HI, i love your tool and have been using it for a while.

Yesterday - maybe a day earlier it started to provide different value for plotted line and recommendation.

here it propose a rout at 283 / TWA 95

http://telegra.ph/file/020224fb5b96d22931ac3.png

but if you match the track proposed with the red and green dotted line it show
route 283 : TWA 120

http://telegra.ph/file/0747f0ad96a9d3e1aafb1.png

Its TWA 95 VS TWA 120 ( here it is 95 the accurate value for the route.

KR.

commenticon 9 Comments
Post by iconPost by L1 | 2017-03-19 | 19:16:44
actually it propose 2 winds at current position

http://telegra.ph/file/89d37ad26e2590de73294.png
From map : 42,9° / 6,57kt
From routing : 17° / 7kt
Post by iconPost by zezo | 2017-03-20 | 13:01:31
The router and web interface use different data, so it's possible for them to get out of sync. I haven't noticed global problems with the site, but it's possible that the confusion happens in the browser.

For example changing your PC clock/date would confuse the caching.

In such cases it's worth cleaning the browser cache first (or trying different browser/PC for the test). Does not fix all problems, but helps sometimes.
Post by iconPost by zezo | 2017-03-20 | 13:05:29
There is also the problem that the heading, wind and TWA in the suggestion don't add to 360 most of the time. This known problem with no easy fix. The router usually has a 5-degree noise in the first step or two, so the actual output may look like TWA 65 55 60 60 60 60 ....

I try to filter that effect and the suggestion could be "TWA 60" for 1 hour, but there is no correct heading/twa combination because the wind is changing in time and space.
Post by iconPost by zezo | 2017-03-20 | 13:07:56
And third, recently I've been seeing larger differences than expected between the game and the interface. Maybe from the start of the St. Tropez race. It's possible that VR have changed something in the wind interpolation algorithm and that will have to be investigated further if the differences persist.
Post by iconPost by L1 | 2017-03-20 | 23:45:56
thanks.
Post by iconPost by L1 | 2017-03-20 | 23:52:37
actually for 'now' position things have come back to normal but i now see 'future' différences for ex
<a url="http://telegra.ph/file/5a38f4c22eb21313890a1.png"> http://telegra.ph/file/5a38f4c22eb21313890a1.png </a>

where at +39h
its 18kn vs 12 knd. maybe as you say i have a batch bogus data. i will clear all and see what happens.
Post by iconPost by L1bis | 2017-03-21 | 00:06:02
it did change after ditching the cache but its still different


http://telegra.ph/file/cb8205182f61b143b1198.png

16kn vs 11kn
Post by iconPost by zezo | 2017-03-21 | 00:11:18
There was a weather update in progress 5 minutes before your post. Which could cause differences, or it could be something else. Can you check again pls?
Post by iconPost by l1ter | 2017-03-21 | 01:50:43
yes still different

http://telegra.ph/file/26b17125204ad993bd6d0.png

all 3 screen shot there
http://telegra.ph/zezo-03-20
border
Topics list
Posts
border
60
border
border
7
border
border
26
border
border
53
border
border
42
border
border
12
border
border
Copyright 2009 by ZEZO.ORG. All Rights Reserved.