Closed jwhite242 closed 1 year ago
Hi @jwhite242 and @davidbloss
David, can you help Jeremy here. That installation method is not the one I normally use for a public install of ATS. I believe Jeremy is working off of your install notes.
Jeremy, python 3.8.2 is the correct python to use, so that is good.
However, the 'main' branch of ATS is in a state of flux. Can you use the 'python3' branch which is the latest python3 stable release. IE, can you add a
git checkout python3
To your method after you do the clone.
This doesn't solve the issue you are seeing (I confirm I saw the something similar when I attempted your commands)
Jeremy, here are commands I would do for a local install, based on what you posted, But would like @davidbloss to check in here with his input on the best way to do this.
git clone git@github.com:LLNL/ATS.git ats3_source cd ats3_source git checkout python3 cd .. python3 -m virtualenv --system-site-packages --python=python3.8 'pwd'/ats3_install ./ats3_install/bin/python -m pip install 'pwd'/ats3_source
In the above there are backticks around the pwd. The above may get you going, I am not sure of the impact of my pip command versus yours with the 'pip install' option.
Also, if you need help installing the ATSLLNL extensions, chat me up please.
@davidbloss Can you review the install instructions, particularly on RZVernal. Left message in teams. But my prior 'virtualenv' and 'pip install' methods are not working on rzvernal.
Hey Shawn, finally got back into this and got to a point where those missing extensions are the holdup instead of python2-3 porting of our other bits. So where do I get those LLNL extensions to start exercising the schedulers/machines?
Hi Jeremy
https://lc.llnl.gov/gitlab/dawson/atsllnl ssh://git@czgitlab.llnl.gov:7999/dawson/atsllnl.git
And hang on, I am preparing a presentation for SWING and am currently documeting how to install the python3 version of ATS in a private space.
I have verified it works for the core ATS in this repo. I am now verifying it works with the extensions. Will get back to you in a bit with how I do this.
@jwhite242 Hey Jeremy, I began looking at this issue and was able to recreate it. Just wanted to double check that this is something that needs attention and isn't potentially fixed in one of your incoming PRs.
So, it wasn't really urgent or anything, I was just trying that option because it was there in the docs and wanted to see what the workflow difference might be. If that's not an option you all want to support in ATS that's totally fine; I've been successfully using it just as a normal package in a virtual environment for some time now and can certainly continue on that way.
Edit: also, no, I've not tackled this issue in that set of PR's.
If this is not a necessary install method, and a user can install and test in other ways, we can just update the documentation and close this out. Energy better spent elsewhere.
Not sure what the root of the issue is here given i can import the module in question manually in the interpreter, but using the project install option is currently not very happy. I used the python 3.8.2 module on the LLNL toss3 machines so you can hopefully reproduce it? Anyway, cloning, then attempting to install into an alternate directory gives this enormous stack pointing to something that's definitely built in to the python install. Following the steps on the readme leads to:
pip installing into a virtualenv seems to work ok still, but wanted to try out this option to compare the workflow differences for everyone (unless that's not supported anymore, which is fine too).
Much appreciate any help sorting this (and/or me) out!