-
Notifications
You must be signed in to change notification settings - Fork 5
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
Set up of Siesta code is wrong. #42
Comments
ok, thanks for reporting! Edit: Indeed, the validation of file paths for codes is a contentious issue aiidateam/aiida-core#868 but here it would have helped |
Sorry @ltalirz but I have no idea about the mechanism. When you install siesta, the executable is in the Obj folder of the siesta package. However in the quantum mobile all the executables seem to be in /usr/local/bin. I guess you copy them automatically after installation. |
Indeed - I see the executables are now copied one by one https://github.com/marvel-nccr/ansible-role-siesta/blob/ab36d895eba05504d0ede8589ff9fbb6ca862148/tasks/main.yml#L81-L132 (I guess this was introduced by Alberto). Simply removing the /Obj postfix should resolve the issue. |
...mmm... I'm not understanding. The siesta executable is in the folder /usr/local/bin, so I think everything is correct from the siesta role. The problem comes in the setting up of the code in aiida. Is it done here: ansible-role-aiida/tasks/plugins/aiida-siesta.yml Lines 13 to 26 in 9ee58f9
The item.name is correct. What is the item.folder? I'm very confused |
|
Ok, now I understood. So this |
Not even sure if the issue is here, but the code
siesta-v4.1-rc1-siesta
available from the aiida set up in the quantum mobile (last version at least) contains a wrong remote absolute path. It showslocal/Obj
instead oflocal/bin
.This makes aiida_siesta unusable in the quantum mobile.
The text was updated successfully, but these errors were encountered: