New Linux build and altered distribution system ready. Please try it out and report back answers to the simple questions below. If I get enough successful responses on a variety of Linux systems in the next 24 hours, I’ll call 1.0.
Download from the Linux column of here. If that fails, try curl -O "http://www.psicode.org/downloads/Psi4conda2-latest-Linux.sh". If that fails, try curl -O "http://www.psicode.org/downloads/Psi4conda2-latest-Linux.sh" --keepalive-time 2.
(1) Did any of the three download routes ([a] button, [b] curl, [c] curl w/keepalive) fail?
Clicking on Linux button works for me, but took a very long time (like a minute) and I had no indication it was doing anything for the majority of that time (Chrome’s loading indicator spun for like a second).
I think your directions are fine, with the exception that a total noob might not know to make the script executable (or call it with the bash command).
I’d also be happy to test a new 1.0rc2 tarball/tag by packaging it up for Debian/Ubuntu if you’d make one. There’s been quite a few changes since 1.0rc.
Clicking on the button worked, but the download took quite a long time and I could not execute the script: ERROR: size of Psi4conda2-latest-Linux.sh should be 280582635 bytes curl didn’t work either giving the following error curl: (18) transfer closed with 228880096 bytes remaining to read
Seconding the please try out the --keepalive-time 2 curl variant, @robertodr. It’s not conda that’s hard-pressed to serve up the 280mb, as this is a download from psicode.org, it’s just large in general, and the keepalive was the way I found around it. Would be good to know if keepalive works for all.
@ryanmrichard, we decided your problem was an interfering PSIDATADIR already set. You’ll still have to squash this in a real working environment, but I uploaded a new installer that will do the install tests correctly even if set. Thanks for uncovering this!
OK, I can download successfully on the Tromsø cluster:
2. CentOS release 6.7
3. glibc version 2.12
4. CheMPS2 testing failed with this:
RuntimeError:
Fatal Error: DMRG_CASPT2 is not a valid option.
Error occurred in file: /scratch/cdsgroup/conda-builds/work/src/lib/liboptions/liboptions.h on line: 59
I obtained no output attesting that either PCMSolver or v2RDM_CASSCF were tested. Though running by hand one of the PCM tests showed that everything works just fine.
5. Despite the location of psi4conda being added to PATHldd -v psi4 returns ldd: ./psi4: No such file or directory
But which psi4 points to the correct executable…
6. Installation instructions are clear enough, IMHO
7. Everything in this step worked like a charm
So did the download never work on the one machine and the Tromso cluster was a different, successful attempt? That’s sad that keepalive wasn’t a universal fix. Did you try other values than 2?
On (5), it has to be ldd -v $(which psi4) if you don’t navigate. I fixed the directions now.
On (4), I think I’ll separate out the tests, so if one doesn’t work, you’ll still see results from the others. I’m still trying to figure out why DMRG_CASPT2 was invalid.
Ok, @mbanck, Psi4+CheMPS2 is healed, and 1.0rc2 tag is pushed.
I had to fiddle with our versioning to keep it monotonic with this tag– basically, this tag will compute to 1.0rc200 and subsequent commits will increment.
If I do push 1.0 proper in the next day or two, is that going to cause havoc with your workflow?
I just uploaded a new installer, @robertodr, so please give it a try if you have a chance, along with the updated ldd line. I don’t understand the caspt2 error, so would like to see it resolved.
I’ve got responses from wholly successful me on gatech pace, partially successful Ryan, partially successful Roberto, and wholly successful Sahan. Any other Linux clusters out there?
No it never worked, but I was trying it during a conference and it might have been a problem with the Internet connection. I tried values other than 2 and they didn’t work.
Everything works wonderfully with the new installer! I managed to download from the webpage, so I guess there really was some issue with the internet connection at the conference.
2. I am on Ubuntu 15.10
3. glibc version 2.21 (Ubuntu GLIBC 2.21-0ubuntu4.3)
4. All tests passed.
5. ldd -v $(which psi4) returns:
