ML ICRITERIA: Difference between revisions

From VASP Wiki
No edit summary
No edit summary
Line 7: Line 7:
The following options are possible for {{TAG|ML_ICRITERIA}}:
The following options are possible for {{TAG|ML_ICRITERIA}}:
* {{TAG|ML_ICRITERIA}} = 0: No update of the threshold {{TAG|ML_CTIFOR}} is done.
* {{TAG|ML_ICRITERIA}} = 0: No update of the threshold {{TAG|ML_CTIFOR}} is done.
* {{TAG|ML_ICRITERIA}} = 1: Update of criteria using average of the Bayesian errors of the forces from history (see description of method below).
* {{TAG|ML_ICRITERIA}} = 1: Update of criteria using average of the Bayesian errors of the forces from history (see description of method [[Machine learning force field calculations: Basics#Threshold for error of forces|here]]).
* {{TAG|ML_ICRITERIA}} = 2: Update of criteria using gliding average of Bayesian errors (probably more robust but '''not well tested''').  
* {{TAG|ML_ICRITERIA}} = 2: Update of criteria using gliding average of Bayesian errors (probably more robust but '''not well tested''').  



Revision as of 08:13, 25 February 2022

ML_ICRITERIA = [integer]
Default: ML_ICRITERIA = 1 

Description: Decides whether (ML_ICRITERIA>0) or how the Bayesian error threshold (ML_CTIFOR) is updated within the machine learning force field method. ML_CTIFOR determines whether a first principles calculations is performed.


The usage of this tag in combination with the learning algorithms is described here: here.

The following options are possible for ML_ICRITERIA:

  • ML_ICRITERIA = 0: No update of the threshold ML_CTIFOR is done.
  • ML_ICRITERIA = 1: Update of criteria using average of the Bayesian errors of the forces from history (see description of method here).
  • ML_ICRITERIA = 2: Update of criteria using gliding average of Bayesian errors (probably more robust but not well tested).

Related Tags and Sections

ML_LMLFF, ML_CTIFOR, ML_CSLOPE, ML_CSIG, ML_MHIS, ML_XMIX

Examples that use this tag