bur report: ML_ISTART=3, ^@ in System name of ML_ABN

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

Moderators: Global Moderator, Moderator

Post Reply
Message
Author
jianli_shao1
Newbie
Newbie
Posts: 4
Joined: Fri Jul 03, 2020 2:29 am

bur report: ML_ISTART=3, ^@ in System name of ML_ABN

#1 Post by jianli_shao1 » Wed Nov 16, 2022 5:12 am

VASP version: 6.3.2
RUN job: testsuite/tests/ML_FeCrNi_ISTART3

Hi,
When i run testjob with ML_ISTART=3, the "System name" in ML_ABN from the second system will starts to appear garbled text, like

Code: Select all

     
     Configuration num.     14
==================================================
     System name
--------------------------------------------------
     ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
==================================================

ferenc_karsai
Global Moderator
Global Moderator
Posts: 422
Joined: Mon Nov 04, 2019 12:44 pm

Re: bur report: ML_ISTART=3, ^@ in System name of ML_ABN

#2 Post by ferenc_karsai » Wed Nov 16, 2022 8:38 am

Thank you very much for reporting that.

Yes that happens also if I run the calculation. But the data is ok and also the rest. So for a quick fix just rename the files in the ML_ABN file.

I will fix that problem until the next update of the code.

ferenc_karsai
Global Moderator
Global Moderator
Posts: 422
Joined: Mon Nov 04, 2019 12:44 pm

Re: bur report: ML_ISTART=3, ^@ in System name of ML_ABN

#3 Post by ferenc_karsai » Wed Nov 16, 2022 2:55 pm

So I've fixed it in the code.

The fix will be in the next update, but since it is a one liner so I can post the fix here:

In the file ml_ff_abinitio.F change the line 2041 from

MLH_TMP%AB%SZNAM2_INPUT(1:ML_SUPER_HANDLE%AB%NSYS_ALLOCAE)=ML_SUPER_HANDLE%AB%SZNAM2_INPUT(1:ML_SUPER_HANDLE%AB%NSYS_ALLOCATE)

to

MLH_TMP%AB%SZNAM2_INPUT(1:ML_SUPER_HANDLE%AB%MCONF_ALLOCATE)=ML_SUPER_HANDLE%AB%SZNAM2_INPUT(1:ML_SUPER_HANDLE%AB%MCONF_ALLOCATE)


Thanks again for making us aware of this problem.

Post Reply