-
Notifications
You must be signed in to change notification settings - Fork 1
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
Question about dataset #6
Comments
Of course,
|
Thank you so much for the explanation and fixing the bug. Regarding estimate.py, can i just modify the code to not use gt.txt when i want to evaluate the algorithm on real data that was not generated via Unreal Engine? I am assuming that only estimated x and y and best_score will be used during algorithm runtime/optimization and pose.z, pose.qw, pose.qx, pose.qy, pose.qz can just be set to 0 for example? |
Yeah, you can modify the code in |
In this project, the height value z can be set to zero? |
Setting z to 0 most likely will cause the RMSE to be large due to discrepancy between true z and what you set I am assuming. In real scenario z can be estimated from some other sensor such as Barometer. I am still new to this repo and trying to figure things out but when i briefly tested ORBSLAM3 (which is similar to ORBSLAM2 used for relative position in this repo) there is going to be relative z value, but not super sure how that'll be reflected into overall optimization and final abs_res.txt. |
can you please elaborate more on dataset side of things? specifically about satellite images:
when a filename is 0_x0_y0.png is x0 and y0 latitude and longitude respectively? or are they just pixel coordinates based on original satellite image? based on example dataset i feel like it's pixel coordinates, but just wanted to make sure.
If it's pixel coordinates then i probably need to have a mapping from pixel coordinates of satellite imagery to actual geolocation, correct?
what exactly is gt.txt under uav folder and where does that come from? From quick look AbsLoc/estimate.py seems like it's being used to get the pose and publish it to slam? but i thought the estimated absolute pose actually gets published into slam. a bit confused here, since i thought the absolute pose being sent to orbslam2 is 2-dof and it comes from superpoint matches
The text was updated successfully, but these errors were encountered: