-
Notifications
You must be signed in to change notification settings - Fork 9
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
reproduce #38
Comments
Hi @wawpaopao , did you use the processed ATAC-seq CTCF ChIP and Hi-C provided from Zenodo https://zenodo.org/record/7226561? If that is correct, you can check your loss curve, it should converge at around 0.15. The original model is trained for about a day on 4 V100s with batch size of 8. You can check your machine setup and make sure you leave sufficient time for training. |
I might have some differences in training time. I trained for 60 epochs, so the total batch size would be 8 * 4, right? |
So, the total number of samples is approximately 5000. Using 4 NVIDIA RTX 3090 GPUs, it takes about 5 minutes per epoch. |
I adjusted the batch_size to 32, and on a single 3090 GPU, I was able to replicate the results fairly well within about 10 epochs. Thank you.However, we can also observe that the batch size has a significant impact on the results. |
hello!
I am currently engaged in replicating the C.Origami model and have encountered some difficulties.
I have diligently replicated the training process detailed on GitHub, employing the same datasets and code across two distinct servers, and have done multiple times. I've noticed considerable randomness in the training process, and the weights saved automatically by PyTorchlightning do not seem to effectively predict the Hi-C matrices in the training, validation, and test datasets. Using the checkpoints provided on GitHub, I found that there were no issues with the predictions.
I am curious to know if there have been previous reports of such variability, and if not, I plan to continue repeating my experiments to understand this phenomenon better.
thanks!
The text was updated successfully, but these errors were encountered: