-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grammar misses tacks #1299
Comments
on the image, we see TWA plotted. Tacks should be easy to detect. |
The relevant data to reproduce this can be obtained using
for the boat With this slice of data, 5 maneuvers are detected:
We have to add 2 hours to these times to get the corresponding time in the web interface. |
In commit
We can notice that there are plenty of states segmented as "not in race". What we could try to do is to prohibit those states if segmentation fails. |
In branch jo-issue-1299-bak00 https://github.com/jpilet/anemomind/tree/jo-issue-1299-bak00, my approach is to repeatedly retry doing segmentation+calibration with settings that gradually encourage more and more maneuvers. Clearly a duct-tape solution, but, well, maybe it is useful... |
When I run
I get:
however, when looking at the trajectory, it is clear that the boat was sailing upwind and did many tacks:
https://www.anemolab.com/map/5acf5b95adaa5da9ab9d06a8?l=0.5173728794325196,0.3543986648664027,0.0018089042551497903&c=5acf5b95adaa5da9ab9d06a82018-06-02T10:11:392018-06-02T18:20:14&t=1527938531523
To obtain the results above, I had to do #1297 and #1296.
I guess it is because of the following reason. The boat is a quick boat, but does not sail very close to the wind: 50 TWA, 16-20 AWA. With a TWA of 50, maybe the system does not consider the boat is sailing upwind. I am not sure, it is just a guess.
The text was updated successfully, but these errors were encountered: