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

JRDB-Traj only include stationary robot? #1

Open
Fujiry0 opened this issue Mar 19, 2024 · 2 comments
Open

JRDB-Traj only include stationary robot? #1

Fujiry0 opened this issue Mar 19, 2024 · 2 comments

Comments

@Fujiry0
Copy link

Fujiry0 commented Mar 19, 2024

Hi! @SaeedSaadatnejad @yanggao2000
Thank you for your excellent work!
I would like to know whether the JRDB-traj only includes the stationary robot. I found the scenes preprocessed in the train_traj_extractor.py do not include scenes where the robot is in motion (For example clark-center-2019-02-28_0 are excluded). On the other hand, the scenes preprocessed in the test_traj_extractor.py seem to include scenes where the robot is moving (For example, nvidia-aud-2019-01-25_0).

Thanks in advance.

# List of file names to process
file_names = [
'bytes-cafe-2019-02-07_0',
'huang-lane-2019-02-12_0',
'gates-basement-elevators-2019-01-17_1',
'hewlett-packard-intersection-2019-01-24_0',
'jordan-hall-2019-04-22_0',
'packard-poster-session-2019-03-20_2',
'stlc-111-2019-04-19_0',
'svl-meeting-gates-2-2019-04-08_0',
'svl-meeting-gates-2-2019-04-08_1',
'tressider-2019-03-16_1',
'gates-ai-lab-2019-02-08_0',
'packard-poster-session-2019-03-20_1',
'tressider-2019-03-16_0',
]

file_names = [
######alphabeta-order of test set
'cubberly-auditorium-2019-04-22_1',
'discovery-walk-2019-02-28_0',
'discovery-walk-2019-02-28_1',
'food-trucks-2019-02-12_0',
'gates-ai-lab-2019-04-17_0',
'gates-basement-elevators-2019-01-17_0',
'gates-foyer-2019-01-17_0',
'gates-to-clark-2019-02-28_0',
'hewlett-class-2019-01-23_0',
'hewlett-class-2019-01-23_1',
'huang-2-2019-01-25_1',
'huang-intersection-2019-01-22_0',
'indoor-coupa-cafe-2019-02-06_0',
'lomita-serra-intersection-2019-01-30_0',
'meyer-green-2019-03-16_1',
'nvidia-aud-2019-01-25_0',
'nvidia-aud-2019-04-18_1',
'nvidia-aud-2019-04-18_2',
'outdoor-coupa-cafe-2019-02-06_0',
'quarry-road-2019-02-28_0',
'serra-street-2019-01-30_0',
'stlc-111-2019-04-19_1',
'stlc-111-2019-04-19_2',
'tressider-2019-03-16_2',
'tressider-2019-04-26_0',
'tressider-2019-04-26_1',
'tressider-2019-04-26_3'
]

@SaeedSaadatnejad
Copy link
Contributor

Hi thank you.
In training, we used only scenes with the stationary robot, finding them to be more manageable for the model to train on. However, if you wish to train on other scenes, you can easily do so by adding their names to the list in train_traj_extractor.py

@Fujiry0
Copy link
Author

Fujiry0 commented Mar 20, 2024

Thank you for your reply!

In training, we used only scenes with the stationary robot, finding them to be more manageable for the model to train on.

That makes sense because the model has to predict the future trajectories of other people and the robot's ego motion at the same time in the scenes where the robot is moving. I asked because I thought the trajectory was represented by the scene-centered coordinate and could not find any code for coordinate transformation from robot-centered coordinate to scene-centered coordinate. I understand the model is trained on the robot-centered coordinate.

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