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

Traversability value saturation #310

Open
Matthewjsiv opened this issue Aug 19, 2024 · 1 comment
Open

Traversability value saturation #310

Matthewjsiv opened this issue Aug 19, 2024 · 1 comment

Comments

@Matthewjsiv
Copy link

Thanks for your work on open sourcing this and making it easy to run! I just had a quick clarification question regarding the traversability supervision signal.

I noticed on both of the outdoor bags that the value published to "/wild_visual_navigation_node/instant_traversability" are generally saturated in the range of .98-1.0. I am wondering if this is expected or I have something set up wrong on my end, as in the paper it is mentioned that the values are calibrated based on the platform to stretch between 0-1.0.

Additionally, I was wondering if you guys are planning on releasing anymore bags with more diverse robot-environment interactions, for example the experiments in Figs 1&11 from the 2024 paper.

Thanks again!

@mmattamala
Copy link
Collaborator

mmattamala commented Sep 6, 2024

Hi @Matthewjsiv, apologies for the very late reply.
If I remember correctly, the sequences in the rosbags are not hard enough to be make that distinguishable. If you want to make it more sensitive, you can change the parameters of the sigmoid function, which unfortunately we did not expose in the config files:

self._supervision_generator = SupervisionGenerator(
device=self._ros_params.device,
kf_process_cov=0.1,
kf_meas_cov=10,
kf_outlier_rejection="huber",
kf_outlier_rejection_delta=0.5,
sigmoid_slope=20,
sigmoid_cutoff=0.25, # 0.2
untraversable_thr=self._ros_params.untraversable_thr, # 0.1
time_horizon=0.05,
graph_max_length=1,
)

Regarding the rosbags, we are not planning to publicly release more bags at the moment. There are other ongoing projects (especially on @JonasFrey96's side) which involve more interesting data to be released but we don't have a timeline for this I'm afraid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants