We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug When I run the 03-Training-with-HugeCTR.ipynb notebook, the training step does not print out the accuracy and loss metrics.
We can avoid this
model.compile() model.summary() model.fit(max_iter=2000, display=100, eval_interval=200, snapshot=1900) model.graph_to_json(graph_config_file=MODEL_DIR + "1/movielens.json")
OR
.py
!python model.py
Second option might be problematic for the hugectr unit test because of !.
!
Steps/Code to reproduce bug please run 03-Training-with-HugeCTR.ipynb
Expected behavior A clear and concise description of what you expected to happen.
Environment details (please complete the following information):
docker pull
docker run
merlin-training:22.04 container is used
merlin-training:22.04
The text was updated successfully, but these errors were encountered:
@benfred and @karlhigley can you please advice? I will create a PR accordingly. thanks.
Sorry, something went wrong.
The first option sounds good to me
Successfully merging a pull request may close this issue.
Describe the bug
When I run the 03-Training-with-HugeCTR.ipynb notebook, the training step does not print out the accuracy and loss metrics.
We can avoid this
OR
.py
file and run the following in another cell:Second option might be problematic for the hugectr unit test because of
!
.Steps/Code to reproduce bug
please run 03-Training-with-HugeCTR.ipynb
Expected behavior
A clear and concise description of what you expected to happen.
Environment details (please complete the following information):
docker pull
&docker run
commands usedmerlin-training:22.04
container is usedThe text was updated successfully, but these errors were encountered: