-
Notifications
You must be signed in to change notification settings - Fork 147
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
[BUG]: requirements.txt in log-parsing-models for training and tuning models folder #1227
Comments
Hi @nyck33! Thanks for submitting this issue - our team has been notified and we'll get back to you as soon as we can! |
Actually I made a conda env with the requirements.txt in the log-parsing-models folder but it's first cell requires torch which is not on that file
That's extremely confusing when you put a requirements.txt in a folder with a notebook, looks like almost every folder has a requirements.txt or .yml which makes it seem like "build your env using this to run this notebook" right? Please fix the entire training-tuning-scripts folder if they require fixing but just trying to run the log-parsing-training.ipynb and seeing |
- Replace `requirements.txt`files (pip) with `requirements.yml` (conda environment). - Update dependency versions. Closes #1226 Closes #1227 ## By Submitting this PR I confirm: - I am familiar with the [Contributing Guidelines](https://github.com/nv-morpheus/Morpheus/blob/main/docs/source/developer_guide/contributing.md). - When the PR is ready for review, new or existing tests cover these changes. - When the PR is ready for review, the documentation is up to date with these changes. Authors: - Eli Fajardo (https://github.com/efajardo-nv) Approvers: - Michael Demoret (https://github.com/mdemoret-nv) URL: #1256
Version
23.11
Which installation method(s) does this occur on?
Docker
Describe the bug.
When I cd to
I open requirements.txt and see
Minimum reproducible example
Relevant log output
Just a minor typo
Full env printout
Not sure why it's not there, in the dev container.
Other/Misc.
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: