Skip to content

why hardcoded prediction split nuscene data number of frames? #74

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.

Sign up for GitHub

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

Jump to bottom
Open
pengzhenghao opened this issue Mar 26, 2024 · 3 comments
Open

why hardcoded prediction split nuscene data number of frames? #74

pengzhenghao opened this issue Mar 26, 2024 · 3 comments
Labels
question Further information is requested

Comments

@pengzhenghao
Copy link
Member

Screenshot from 2024-03-26 16-31-39

I think here we should use a while loop to back / forward search frames:

Screenshot from 2024-03-26 16-33-34
@pengzhenghao pengzhenghao changed the title why hardcoded prediction split nuscene data number of frame? why hardcoded prediction split nuscene data number of frames? Mar 26, 2024
@QuanyiLi
Copy link
Member

@Alan-LanFeng Not sure if this is done by you..

@QuanyiLi QuanyiLi added the question Further information is requested label Mar 29, 2024
@Alan-LanFeng
Copy link
Collaborator

@QuanyiLi No, didn't touch this part.

@QuanyiLi
Copy link
Member

@pengzhenghao It is made by me. If you use while to select all past frames and future frames. The whole scenario will be selected into this scenario description file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pengzhenghao @QuanyiLi @Alan-LanFeng