Dear Prof. is it possible to "Not enough known energies to fit CE" on maps.log even after 60 ab-initio calculations?
I am using your example in Al,Ti fcc structure and vasp as ab calculator.
below are what I did:
makelat Al,Ti fcc
cd AlTi_fcc
maps -d &
touch ready
…
touch ready
cd 0
runstruct_vasp
…
…
and finally
pollmach runstruct_vasp
Thanks Prof. for the reply, later I realized the same.
Now I am on the way to calculate the Phonon spectrums (trying both, spring model and bond stiffness vs bond length) . I am following Rev. Mod. Phys 74, 11 (2002). Will you recommend me any other papers directly related to the code?
I’m not sure how you finally addressed the problem, but I’m having the same thing here. I went to 240 structures using the same lines given above, and it still shows "Not enough known energies to fit CE".
Each folder has an empty error file as well. There is no fit.out in the root directory.
The way I carried out these calculations was: feeding the code (after interactive testing) below to a job submission script:
maps -d &
pollmach runstruct_vasp
From the output log of the stdout when it runs out of walltime, quite frequently, such error messages show up:
Running in /nfs/02/utl0268/terencelz/local/ATAT/AlTi_fcc/137
Finding best cluster expansion...
done!
sort: write failed: standard output: Broken pipe
sort: write error
Done running in /nfs/02/utl0268/terencelz/local/ATAT/AlTi_fcc/137
Finding best cluster expansion...
done!
Finding best structure...
done!
If I let it run in the interactive "debugging" mode, these errors don’t show up. I assume it’s just an IO error and doesn’t matter? Or it could be the culprit.
I tried it on another supercomputer (recompiling and installing atat) and it still went all the way to more than one hundred structures without being enough.
If each numbered sub directory has file called error in it, that means the code saw an error in the vasp output files and the energy was ignored by maps. If there are no errors in your vasp runs then delete the "error" files and maps should work normally. Btw, iwill soon post an update for the run struct_vasp command that prevents this problem in the first place.
Thank you very much for the help. maps is finally moving. I saw the empty error file was mentioned in the manual, but I was not able to make the connection back then.
Maybe instead of touching an empty error file, write some words in it… So that one will not interpret it as no error when seeing one.
I’m not sure if this is the reason that triggered it, but I enabled KPAR > 1 parallelism and VASP always gives me warnings about this.
checkerr_vasp has this cryptic "errmsg" function I have no idea what is…
I’ve fix the problem in the " Beta version of the latest update " on ATAT web page. Version 3.14 and after should not have this problem (which was due, as you noticed, to VASP now displaying a warning whenever the NPAR parameter may not be optimal…)
It will update the log once the search loop is complete. For 200 structure it may take some time… Sorry. If search seems to restart multiple times, perhaps try to limit the composition range where ground states have to be exact with -c0 and -c1 option.