-
Notifications
You must be signed in to change notification settings - Fork 8
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
training iterations #1
Comments
I have the same question.I modify parameters in configs/lego/test1_events.txt,changed N_iters (5000001 to 500001) and lrate_ Decay_ Steps (50000000 to 5000000), however, the image rendered based on readme is pure pink purple.Have you resolved this question? |
Hello, sorry for the delay. |
@circle-DING , could you please share the results? |
I'll share pretrained models today for easier reproduction |
Due to limited computing resources, I'm sorry that I didn't train for 510^6 iterations. I stopped training at slightly over 510^5 iterations, which happens to be the correct approach you suggested. |
Thank you for your reply and help! |
However, I found that if the number of iterations is set at 5x10^5 of the paper, the PSNR will not achieve the effect of the paper. I trained the lego scene with four 3090s, iterated 1 million times, and the PSNR was just 20, but in the paper it was 25 |
However, I found that if the number of iterations is set at 5x10^5 of the paper, the PSNR will not achieve the effect of the paper. I trained the lego scene with four 3090s, iterated 1 million times, and the PSNR was just 20, but in the paper it was 25 |
However, I found that if the number of iterations is set at 5x10^5 of the paper, the PSNR will not achieve the effect of the paper. I trained the lego scene with four 3090s, iterated 1 million times, and the PSNR was just 20, but in the paper it was 25 |
I'm writing to update you on our recent training efforts. Due to limited lab resources, we utilized a 3090 Ti GPU, aiming for 5x10^5 iterations, in line with the paper's recommendation, despite the config suggesting 5x10^6.
Upon pausing around 5x10^5 iterations, our PSNR results on data/lego/est1_events_color_bg09 were around 21, falling short of the expected outcomes mentioned in the paper. Given the time constraints and the results obtained, we've temporarily halted further training.
I would appreciate any advice or insights on how to proceed or improve our results.
At 2024-03-06 19:00:22, "jzyu" ***@***.***> wrote:
@circle-DING , could you please share the results?
However, I found that if the number of iterations is set at 5x10^5 of the paper, the PSNR will not achieve the effect of the paper. I trained the lego scene with four 3090s, iterated 1 million times, and the PSNR was just 20, but in the paper it was 25
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Hello, thank you for your question and sorry for the delay. Could you briefly write how you compute PSNR on your side? Just to be safe, let me briefly recap the evaluation procedure from my side. The correct number of iterations is 5 * 10^5. The logged PSNR should NOT be used for evaluation as it is derived from the training event-based loss of the current mini-batch. The numbers reported in the paper are computed after training for about 5 * 10^5 iterations using the procedure described in metric/README.md. To help the process, please also find the converged pretrained models uploaded here ( I hope this helps. If you have more questions, I'm available and will respond rather quickly. |
Nice work, I have a question about the training.
In your paper, you train the model for 5 * 10^5 iterations. However, N_iters in config.txt is set to 5000001. What is the correct number of parameters?
The text was updated successfully, but these errors were encountered: