-
Notifications
You must be signed in to change notification settings - Fork 3
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
loss is nan #4
Comments
same question.can give me some advice? |
Same question and the accuracy is quite low. |
As other FSCIL methods do, we used FSCIL Benchmark Settings proposed in FSCIL. If you have an issue, It would be helpful to use the data split index file from the [link](https://github.com/xyutao/fscil, which is widely used in FSCIL to benchmark scenarios. |
We mean there are some wrong of your code. The loss is nan and the ACC is quite low, only 1-2%. |
I've found that it is due to the Torch version. Try using the Torch version 1.12 or 1.11. I conducted all the experiments using Torch version 1.12. |
Slove the problem that loss is nan, but the ACC is still low, I use the default parameters. Session 1, test Acc 23.831 Session 2, test Acc 22.143 Session 3, test Acc 19.693 Session 4, test Acc 18.600 Session 5, test Acc 16.918 Session 6, test Acc 15.978 Session 7, test Acc 15.095 Session 8, test Acc 13.840 Base Session Best Epoch 4 [25.567, 23.831, 22.143, 19.693, 18.6, 16.918, 15.978, 15.095, 13.84] |
FileNotFoundError: [Errno 2] No such file or directory: '/data/pgh2874/FSCIL/Ours/dataloader/miniimagenet/map_clsloc.txt' |
Low accuracy can result from the different TiMM versions. I recommend using For the FileNotFoundError, I've uploaded the map_clsloc.txt file to this repository. Make sure to change the directory path to match your directory path. |
Thanks for your work, I have a problem with running default params, loss is nan like:
Session 0, epo 1, lrc=0.0002,total loss=nan, loss_CE=nan, loss_ED=nan, loss_SKD=nan, acc=0.0160: 86%|██████████████████████████████████████████████▍ | 202/235 [04:08<00:40, 1.22s/it
The text was updated successfully, but these errors were encountered: