-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
About Dataset collate fn #58
Comments
Hi, I'm really confused about what the question is here. Please say: 1) what you did (e.g. a partial code containing what is registered) 2) what you expected 3) what went wrong. For example, I think you mentioned wanting to use your own
|
Thanks for fast replying!
I changed these parts from imagenet.py (I changed only the name. not the working code) In the second picture, actually, I changed this part,
and changed part's collated_fn_name is not the same as the 3rd picture's register_collated_fn name.
|
Hello! thanks for sharing the great work!
I have some questions about the dataset.py code.
I rewrite the imagenet.py in dataset/classification to make my own dataset.
I changed only the name of def and 'register_collated_fn', 'register_dataset'.
I found that my collated_fn def name and 'register_collated_fn' are not the same, and the collated name in dataset.py line 45~47 and 'register_collate_fn' are different either. I wonder if those things call the other collate_fn (not collated_fn in my code) in the training and validation phase? if so, is called collated_fn exactly the same as imagenet.py collated_fn? or working as same as imagenet.py collated_fn? May it make any performance difference by using default collate_fn instead of imagenet_collate_fn?
here is my dataset.py
CBIS-DDSM_4class_sampled.zip
and my yaml file is here
0707_mobilevits_real_defualt_lr0.0001_cosine_advanced_multiscale.zip
The text was updated successfully, but these errors were encountered: