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

DEBUG log not informative? #1

Open
jabowery opened this issue Feb 19, 2024 · 1 comment
Open

DEBUG log not informative? #1

jabowery opened this issue Feb 19, 2024 · 1 comment

Comments

@jabowery
Copy link

I executed multiple_train_sa_run.py and generated the attached log which shows no difference in the length of the description from start to finish. Perhaps it is due to the fact that I use conda rather than pip to install dependencies. I prefer conda for a variety of reasons and have attached the environment.yml file which, you will notice, has no version constraints so as to solve for the "best" version alignments accodring to conda.

Is the log intended to show no change in the length?

multiple_train_sa_run.log
environment.yml.txt

@matanabudy
Copy link
Owner

Hi! Thank you for your question. This is not an issue; rather, what you are observing is that the training has quickly found the optimal solution and is no longer improving. This usually occurs when the noise level is low. To make the training more challenging, consider changing the noise level to medium in config.py:

NOISE_LEVEL_TO_TRAIN = NoiseLevel.MEDIUM

Additionally, you can use train_sa.py to observe the training process in a simpler manner, as it trains using only one process.

I hope this helps! Feel free to ask any follow-up questions.

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

2 participants