ML_MODE values not recognized in VASP 6.4.0

Problems running VASP: crashes, internal errors, "wrong" results.


Moderators: Global Moderator, Moderator

Post Reply
Message
Author
maxime_legrand
Newbie
Newbie
Posts: 6
Joined: Wed Oct 23, 2024 11:17 am

ML_MODE values not recognized in VASP 6.4.0

#1 Post by maxime_legrand » Tue Jun 24, 2025 11:06 am

Good morning,

I am currently trying to test a MLFF for some NEB calculations. I can specify any values (train, select, run,...) to ML_MODE and it is not recognized.

I am using these modules:

module load flavor/vasp/vtst flavor/hdf5/parallel gnu/11 mpi/openmpi/4 openblas/0.3.23 lapack/netlib/3.11.0 fftw3/vanilla/3.3.10 scalapack/netlib/2.2.0 hdf5/1.14.0 vasp/6.4.0

Which load without any conflicts. I also tested it in vanilla (only module load vasp/6.4.0) or with depretacted tag ML_ISTART, same issue.

Note that the same procedure works for version 6.4.2, but only in vanilla.

Maybe did I miss something regarding this specific version ?

Thanks in advance for your help !


merzuk.kaltak
Administrator
Administrator
Posts: 316
Joined: Mon Sep 24, 2018 9:39 am

Re: ML_MODE values not recognized in VASP 6.4.0

#2 Post by merzuk.kaltak » Wed Jun 25, 2025 12:52 pm

Dear Maxime Legrand,

The issue is due to the MLFF part in vasp.
There have been some changes in the MLFF part of vasp after 6.4.0 as pointed out on our known issues page.
You might also read following forum post regard this issue:
https://www.vasp.at/forum/viewtopic.php?p=31139#p31139


maxime_legrand
Newbie
Newbie
Posts: 6
Joined: Wed Oct 23, 2024 11:17 am

Re: ML_MODE values not recognized in VASP 6.4.0

#3 Post by maxime_legrand » Thu Jun 26, 2025 8:00 am

Dear Merzuk,

I couldn't figure out in which section of known issues it was located. Nevertheless, should I simply use a newer version of VASP in order to get rid of this issue ?

Thanks,


merzuk.kaltak
Administrator
Administrator
Posts: 316
Joined: Mon Sep 24, 2018 9:39 am

Re: ML_MODE values not recognized in VASP 6.4.0

#4 Post by merzuk.kaltak » Thu Jun 26, 2025 11:38 am

Yes, please use a more recent version of vasp, since there corresponding code path has changed after 6.4.0.


Post Reply