-
Notifications
You must be signed in to change notification settings - Fork 32
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
pymolcas location #8
Comments
Richard, there are still some issues with trying to be compatible with both MOLCAS and OpenMOLCAS. |
Thank you for the reply. I realized that, for some reason, in certain directories my MOLCAS environment variable was being reset to the default path. But this issue appears to be resolved by explicitly defining the MOLCAS variable in my bash input script. |
I am a new SHARC user and also new to OpenMOLCAS. I was able to successfully build OpenMOLCAS (v18.09) and SHARC v2.1. With both programs built, I tried to walk through the SHARC tutorial. I made it to page 19 without any issues. But when I tried to run run.sh in ICOND_00000 I received the following error in QM.out:
This error is associated with the molcas_input.py script lines 1021-1027:
if os.path.isfile(os.path.join(INFOS['molcas'],'bin','pymolcas')): string+='\n$MOLCAS/bin/pymolcas MOLCAS.input &> $CurrDir/MOLCAS.log\n\n' elif os.path.isfile(os.path.join(INFOS['molcas'],'bin','molcas.exe')): string+='\n$MOLCAS/bin/molcas.exe MOLCAS.input &> $CurrDir/MOLCAS.log\n\n' else: print 'Could not find MOLCAS driver in %s' % os.path.join(INFOS['molcas'],'bin') sys.exit(1)
My environment variable $MOLCAS points to a /build directory. According to this error, I should have pymolcas in /build/bin. However, pymolcas is actually located in my conda virtual environment /bin. I have tried just copying pymolcas into /build/bin but that just results in further errors associated with file paths. My question is, where should OpenMOLCAS have built pymolcas?
Please let me know if there is any additional information I can provide to clarify my issue.
Thank you
The text was updated successfully, but these errors were encountered: