-
Notifications
You must be signed in to change notification settings - Fork 2
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
requirements.txt is missing #3
Comments
The requirements.txt file has been added to the repository. |
Thank you, however I am getting the following error:
On a side note (that might be an issue on my side), I am experiencing issue with some packages (pillow, scikit_learn, ...) that needs to be built from source (on Ubuntu 20.04.6 LTS) in the required versions as the wheel seems not to be available. How was the Maybe it would be worth updating to latest, if it can be verified that the results of the benchmark stays consistent. |
The requirements.txt was generated using pipreqs (https://pypi.org/project/pipreqs/). I fixed the dependency errors in the new requirements.txt and verified that all these requirements can be downloaded and installed using "pip install -r requirementx.txt". As I mentioned in the requirements.txt, "lightning" was only used for the lightning version of the ENOT baseline, which we ended up not using for the evaluation (we used the pure pytorch version). For clarity and to resolve dependency issues, I have removed this version of ENOT. In general, the benchmark code uses only basic math operations from torch and numpy. All benchmark parameters are downloaded from Google Drive. Therefore, it is not critical to have exactly the same version as long as numpy and torch perform math operations in the same way in all versions. There is plotting and metric code for some benchmark pairs in the mixtures_benchmark_visualization_eot.ipynb notebook. You can compare it with the output you get in your Python environment. The results should be the same if your torch/numpy version has the same random generators, and may be slightly different if not. |
The README suggests to
but the file seems not to have been included in this repository.
The text was updated successfully, but these errors were encountered: