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

"Person" class in semantic segmentation input #23

Closed
TheDarkKnight1998 opened this issue May 12, 2021 · 2 comments
Closed

"Person" class in semantic segmentation input #23

TheDarkKnight1998 opened this issue May 12, 2021 · 2 comments

Comments

@TheDarkKnight1998
Copy link

Why do the ten categories of semantic segmentation results not include pedestrians? Do they serve as background?

@JunweiLiang
Copy link
Owner

Originally in the next-prediction repo, we use ADE20K model and only these most common 10 classes are used in preprocessing, which does not include "person" class since person features are covered in another module. See here. Since in the ActEV dataset these are the most common classes except for person class and to keep the same preprocessing, I put the person class into the background (id 0). This is a bit hacky. You can easily change this by adding an entry in the scene36_64_id2name_top10.json file ("13" is person class for ADE20K) for training and testing but may not see a performance difference.

@JunweiLiang JunweiLiang changed the title Test input questions "Person" class in semantic segmentation input May 12, 2021
@TheDarkKnight1998
Copy link
Author

Thank you for your explanation!

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