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

Why are there many instances of using from fsdet import ... in the code instead of leveraging the equivalent definitions within iFS-RCNN? #9

Open
lxp-2003-12-01 opened this issue Feb 25, 2025 · 0 comments

Comments

@lxp-2003-12-01
Copy link

Hello respected author,

I noticed that in many parts of the code, components from the fsdet library are imported, such as in train_net.py:
from fsdet.config import get_cfg, set_global_cfg
from fsdet.engine import DefaultTrainer, default_argument_parser, default_setup
from fsdet.evaluation import (
COCOEvaluator, DatasetEvaluators, LVISEvaluator, PascalVOCDetectionEvaluator, verify_results
)

However, equivalent definitions for these components also exist within the iFS-RCNN codebase. Should I replace all imports from fsdet with the corresponding implementations from iFS-RCNN? I am confused about why the iFS-RCNN code defines these modules but does not use them directly. Could you kindly explain the rationale behind this design choice? Thank you very much for your time and guidance.

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

1 participant