LOCPROJ in v6.5.1

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


Moderators: Global Moderator, Moderator

Post Reply
Message
Author
daniel_kaplan
Newbie
Newbie
Posts: 2
Joined: Thu Mar 21, 2024 2:41 pm

LOCPROJ in v6.5.1

#1 Post by daniel_kaplan » Sun Dec 21, 2025 7:47 pm

Hello all,
I'm encountering the following issue when specifying LOCPROJ using a range specification of sites, i.e.,

Code: Select all

LOCPROJ = 1-6 : s p : Hy

As opposed to

Code: Select all

LOCPROJ = 1 2 3 4 5 6 ...

.

Specifying using 1-6 returns

LPRJ_READER: ERROR: site index of function: 9 out of range: -6

While the latter works (apparently).

Any advice? POSCAR and INCAR are attached.

You do not have the required permissions to view the files attached to this post.

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

Re: LOCPROJ in v6.5.1

#2 Post by ferenc_karsai » Mon Dec 22, 2025 2:15 pm

Please upload all necessary files according to the forum guidelines.


daniel_kaplan
Newbie
Newbie
Posts: 2
Joined: Thu Mar 21, 2024 2:41 pm

Re: LOCPROJ in v6.5.1

#3 Post by daniel_kaplan » Tue Dec 23, 2025 3:23 am

See the attached.

You do not have the required permissions to view the files attached to this post.

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

Re: LOCPROJ in v6.5.1

#4 Post by ferenc_karsai » Tue Dec 23, 2025 8:30 am

Thanks for reporting that. I could reproduce the behavior with VASP.6.5.1 and also with our latest development version.
I see the LOCPROJ description says that "1-6" should be a permitted way of setting the atomic sites.

I will report this problem to a colleague who works on the LOCPROJ file. He is now on christmas holidays so it will take a while until he will be able to work on a fix.

Until that please specify each atomic site explicitely.


henrique_miranda
Global Moderator
Global Moderator
Posts: 578
Joined: Mon Nov 04, 2019 12:41 pm
Contact:

Re: LOCPROJ in v6.5.1

#5 Post by henrique_miranda » Fri Jan 23, 2026 9:56 am

Sorry for my delayed answer.
Indeed this is wrong behaviour from our parser.
We will try to fix it as soon as possible.

In the meantime a workaround is to use (add spaces around the dash):

Code: Select all

LOCPROJ = 1 - 6 : s p : Hy

Post Reply