Skip to content
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

frontend: Survey planning match QGC functionality when outlining area - vertex distance overlay #1459

Open
1 task done
vshie opened this issue Nov 22, 2024 · 5 comments
Open
1 task done
Labels
enhancement New feature or request map mission-planning ui UI related issues

Comments

@vshie
Copy link

vshie commented Nov 22, 2024

Current behaviour

Current you can drag survey area corners around the map, but no size or position context is given - it is therefore difficult to be precise when planning a survey on a known location or of a known area.

Expected or desired behaviour

image Overlay distances between all vertexes when moving any vertex

Prerequisites

  • I have checked to make sure that a similar request has not already been filed or fixed.
@vshie vshie added enhancement New feature or request ui UI related issues labels Nov 22, 2024
@rafaellehmkuhl
Copy link
Member

rafaellehmkuhl commented Nov 26, 2024

This + area calculation + estimated time (based on set speed and without wind).

@vshie @Williangalvani @joaoantoniocardoso are you guys aware of any model for estimative of boat speed on wind that is acceptable and not so complex?

@joaoantoniocardoso
Copy link
Member

joaoantoniocardoso commented Nov 27, 2024

are you guys aware of any model for estimative of boat speed on wind that is acceptable and not so complex

I didn't explore much this part in my thesis, but the simplest option I can think of is the following:

$$ V_{boat}(t) \approx \sqrt[3]{K P_{motor,in}(t)} $$

where:

$$ K \propto \frac{1}{ \frac{1}{2} C_{friction} \rho S } \eta_{motor} $$

The interference of the wind/water is totally out of the scope of my experience... My first thought would be something like:

$$ V_{boat,real}(t) \approx V_{boat}(t) - f\left( V_{wind}(t) \right) - f\left( V_{water}(t) \right) $$

These functions f can be something like:

$$ f(x) = c x $$

where c is some geometry-related coefficient.

For me, this last part would perform very badly, as the drag would depend a lot on the angle of the forces because of the complex geometry...

Now.. is this simple?

@vshie
Copy link
Author

vshie commented Nov 27, 2024

that seems radically more complicated then we should do?? I would simply assume a constant speed over ground, because after all we're running a vehicle that works to maintain the waypoint speed! So it's just a matter of dividing total distance by waypoint speed - our pivot turns don't add much time. If it takes longer than that, your battery was low enough, or the conditions crazy enough, that vehicle could not maintain speed!

This issue was more about making the tool give useful feedback to the user about the size of the area they were mapping....

@joaoantoniocardoso
Copy link
Member

hahahah that makes a lot of sense -- if the boat is powerful enough to navigate the conditions and has a velocity control loop (which it does), then the wind/current speeds shouldn't affect the boat, then, it's just a matter of speed = distance / time :)

@rafaellehmkuhl
Copy link
Member

Totally @vshie. My bad for distorting the topic of the issue 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request map mission-planning ui UI related issues
Projects
None yet
Development

No branches or pull requests

3 participants