-
Notifications
You must be signed in to change notification settings - Fork 15
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
Running VASP interactively throws a BrokenPipeError #218
Comments
At least it is not directly related, i.e. it is not the same error. The lammps calculations stop in the |
Hmm. The code snippet with |
I noticed that if I run it for a single step (i=1), it doesn't throw an error. For i=2, it throws this warning:
Seems to me that the job isn't running interactively? The |
Can you post your INCAR file ? I assume if you comment out the A typical INCAR should include:
|
@jan-janssen you're right. It works if I do not specify The INCAR file with
while the INCAR file without it looks the same as what you commented. |
I now end up with this warning while calling
and this error after:
Am I not specifying something in the input? PS. I'm sorry for the long comments. It's also my first time running VASP in pyiron. |
@raynol-dsouza Can you open a pull request which motives the |
@sudarsan-surendralal Can you take a look at |
@jan-janssen what's the way to find out if a job is interactive or not? We can ignore this check only for interactive calculations |
Hi everyone, I just wanted to see if I could get some inputs on this particular bug. For context, I use I'm still using an older version of pyiron since there was some issue with the compatibility of Any suggestions on how to tackle this? Is updating to newer codebases the only way to go? My versions of code: |
Hi @hari-ushankar, Can you share a code snippet of how you define I have reworked protocols within the |
Hi @raynol-dsouza , Thanks for following up. Here is a code snippet of how I run
The job I define above runs to 150 iterations and then throws the BrokenPipeError. Here is the stack trace from that run (in
Also, to add a normal VASP interactive job runs fine on a node and the cluster queue system. Only when run with the ProtocolQMMM, this behaviour happens. I think it could be also related to how reference jobs are copied over when a Protocol job is run. This was the discussion from the Some insights and tips would be appreciated. |
Hi @hari-ushankar, I created a new branch on
I did however change a few parameters:
-- since these were inputs to the protocol, but they weren't specified in the snippet you sent. -- I changed the -- the code commented out wasn't necessary for the test, however, will be necessary when you'll be running on your cluster. Do note the changes in the VASP reference job. There was a bug that was raised in this issue, but fixed in #220. This is how I would define the VASP reference jobs now. It would be great if you could run a test job using the branch |
Hi @raynol-dsouza , I tried running the example script you sent to check if things work fine. But I have run into an issue with creating jobs using the new git repos. For context, I have my new git repos stashed in a separate dir, and I
The code fails here:
Does this occur because of how jobs are created in the old |
I believe the issue comes from the line:
I had run into a similar issue a while ago, but I think it was addressed in a PR, I do not know which one. Could you make sure that
and check if this works? |
My
Initially, I tried with It didn't work that's why I switched to this is the error log:
Edit: I tried using
|
|
pyiron_base's version:
|
commit e3aa971b8f3d7758af42257f4c4276fdd33f2c6c
This looks more like a database issue to me. @pmrv @muh-hassani any inputs? I cannot reproduce these errors on both, my local machine and my Garching account.
What output do you get if you just use |
I get all the potentials associated with Al, the list goes on:
|
Hmm. The potentials list seems to be outdated as well. I'm afraid I cannot be of much help at the moment. Let's wait till @pmrv and @muh-hassani have a look at these errors. |
@hari-ushankar from pyiron_atomistics import Project
import pyiron_contrib
pr = Project('test-QMMM')
# setting up structure and species
host = 'Al'
solute = 'Ni'
bulk_struct = pr.create.structure.bulk(host, cubic=True).repeat((1, 1, 8)) # a simple structure
sol_struct = pr.create.structure.bulk(solute, cubic=True).repeat((1, 1, 8)) # a simple structure
ref_lammps = pr.create.job.Lammps('ref_lammps')
ref_lammps.structure = bulk_struct.copy()
ref_lammps.potential_list The list I get, is different than what you have:
Can you check your |
Hi @muh-hassani , Thanks for the suggestion. I did install But I think I get the error when I save the job using For context, I'm manually adding package paths into my jupyter notebook to run my pyiron jobs. But I'm still using the old pyiron repo and maybe this is causing the issue? I'm a little bit worried that moving to pyiron_atomistics and using the recent codebase will break the original ProtocolQMMM code. I suppose I'll try updating pyiron on conda and see if it resolves the issue. |
The following code:
throws the following error:
Has anyone come across this error before? Is this related to #216?
The text was updated successfully, but these errors were encountered: