Open Gilletarom opened 10 months ago
Yes this is certainly possible, but these features must be simple and effective. Actually WR is quite flexible as it stands, using the configuration > constraints which allow consideration of wave ht and wind and comfort etc.
Rick,
For information :
I had created a route with WR. It occurred to me, with this route, to have it tested by WR as if it were a route created manually by a user.
On this test, WR was not able to check the route.
I haven't repeated this type of test, but it intrigued me (and worried me, but this is the first time I'm talking about it).
Gilletarom
Le 08/09/2023 à 22:51, Rick Gleason a écrit :
Yes this is certainly possible, but these features must be simple and effective. Actually WR is quite flexible as it stands, using the configuration > constraints which allow consideration of wave ht and wind and comfort etc.
— Reply to this email directly, view it on GitHub https://github.com/rgleason/weather_routing_pi/issues/143#issuecomment-1712208494, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABRFTZ6VO746CBSXYO4WTT3XZOAMFANCNFSM6AAAAAA4Q3S5AA. You are receiving this because you authored the thread.Message ID: @.***>
I wanted to test the comparison between two routes by comparing the property windows of each of these two routes.
BUT : Currently, OpenCPN does not allow two properties windows to be opened in parallel. You have to open one, then close it, then open the other.
It is not practical.
Yes, only 1 properties window can be opened, and nothing else can be done until closed, it is a closed mode. This is normal. Nothing we can do.
No, this way of approaching the problem which consists of saying: "It's like that and there's nothing we can do about it" is unacceptable. On the other hand, I can understand that the time available to resolve this is insufficient.
Please explain in one simple sentence what you want to do, not how to do it though.
Then explain in one simple sentence how you think it might be accomplished.
Gilletarom,
This has become more of a discussion, and is not a single issue.
On this test, WR was not able to check the route.
Yes, that is correct. WR creates routes, it does not check them.
WR is a plugin that had one skill: "Create routes to go as fast as possible from a starting point to an ending point." BUT Now, he theoretically has a second skill: "To analyze a route created manually by the user" and:
As things currently stand, the operation of this second skill is as follows:
The user must complete the parameters of this search configuration, in particular by including the expected departure time
The user must trigger the calculations for this "Search Configuration".
If the route is not viable, the error(s) that are displayed resemble the errors encountered by WR to find the best route.
If the route is viable, a meteo-trace is created to know the travel times of each segment and the times of passage on each waypoint of the route.
If the route is not viable, you must display the list of the impossibilities to meet:
If the route is viable, then: