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

How is the transformation of annotations in the original dataset into hierarchical JSON files done? #9

Open
tslyellow opened this issue Nov 29, 2024 · 1 comment

Comments

@tslyellow
Copy link

For example, in the FSOD dataset, the annotations downloaded from the FSOD official website only include fsod_test.json and fsod_train.json. However, in the annotations downloaded from the link you provided, there are six JSON files:
fsod_test_fixed_l1.json,
fsod_test_fixed_l2.json,
fsod_test_fixed_l3.json,
fsod_test_miu_fixed_2more_miu_final.json,
original_fsod_test.json,
original_fsod_train.json.
Which script was used to convert fsod_test_fixed_l1.json, fsod_test_fixed_l2.json, and fsod_test_fixed_l3.json?
Could you please inform me?
image
image

@OatmealLiu
Copy link
Contributor

Hi. We annotated the L1 level of FSOD dataset to get a 3-level semantic hierarchy (GT). The L2-/L3-level class names are from the orginal FSOD dataset. We simply tidy them up into a unified JSON file with our newly annotated L1 level. Since this process is not related to the method proposed in this work per se, we do not include the simple processing code.

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