-
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
SPHInX restart_from_charge_density surprisingly starts from atomic density #418
Comments
I don't really understand the phrase here. |
When I restart SPHInX jobs based on previous charge density, the function |
Ah ok so the atomic density is the estimated charge density based on the atomic configuration then. I didn't get the vocabulary but now I understand the problem. Let me see what VASP does and I'll decide what to do 😎 |
So VASP raises an error so I'll fix it in SPHInX then. /u/system/SLES12/soft/pyiron/dev/anaconda3/lib/python3.8/shutil.py in copyfile(src, dst, follow_symlinks)
262 os.symlink(os.readlink(src), dst)
263 else:
--> 264 with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
265 # macOS
266 if _HAS_FCOPYFILE:
FileNotFoundError: [Errno 2] No such file or directory: '/cmmc/u/samsstud/RESEARCH/2021/1108/PYIRON/RESTART/vasp_init_hdf5/vasp_init/CHGCAR' |
@sudarsan-surendralal VASP raises the error above when |
Thanks for pointing this out @samwaseda. I've implemented a generic check in #422. Can you have a look at this? If you like it we can also apply them in #420. |
Summary
SPHInX
restart_from_charge_density
silently switches to restart from atomic densities if the code believes that no reliable density is available. That produces surprising behavior. It would be better to stop with a warning.pyiron Version and Platform
developer version on cmti, as of November 2021.
Expected Behavior
Stop with a clear error message.
Actual Behavior
pyiron submits job with a different type of charge initialization
Steps to Reproduce
It's not entirely clear to me under which circumstances this happens. It was observed by @skatnagallu
I understand this happens when the main loop was never reached, or when the rho.sxb cannot be found for whatever reason.
The silent workaround seems to be from @samwaseda
The text was updated successfully, but these errors were encountered: