Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bad termination when setting out_mat_hs=true/True. #5389

Open
16 tasks
ErjieWu opened this issue Nov 1, 2024 · 6 comments · May be fixed by #5489
Open
16 tasks

Bad termination when setting out_mat_hs=true/True. #5389

ErjieWu opened this issue Nov 1, 2024 · 6 comments · May be fixed by #5489
Assignees
Labels
Questions Raise your quesiton! We will answer it.

Comments

@ErjieWu
Copy link
Collaborator

ErjieWu commented Nov 1, 2024

Describe the bug

When running ABACUS with input parameter out_mat_hs=1, it works normally. But if I set out_mat_hs=True or true, it will throw a termination as follows:
Image

Expected behavior

No response

To Reproduce

The full INPUT file is:

INPUT_PARAMETERS
# Created by Atomic Simulation Enviroment
ntype                                   1
ecutwfc                                 100
scf_nmax                                100
smearing_method                         gaussian
smearing_sigma                          0.002
basis_type                              lcao
ks_solver                               genelpa
mixing_type                             pulay
mixing_beta                             0.7
scf_thr                                 1e-07
symmetry                                0
calculation                             scf
force_thr                               0.001
kspacing                                0.08
lspinorb                                0
dft_functional                          hse
init_chg                                file
out_mat_hs                              true

STRU:

ATOMIC_SPECIES
Si  28.085        Si_ONCV_PBE-1.0.upf

NUMERICAL_ORBITAL
Si_gga_7au_100Ry_2s2p1d.orb

LATTICE_CONSTANT
1.8897261258369282

LATTICE_VECTORS
5.4437020000      0.0000000000      0.0000000000
0.0000000000      5.4437020000      0.0000000000
0.0000000000      0.0000000000      5.4437020000

ATOMIC_POSITIONS
Direct

Si
0.0000000000
8
0.9998180000 0.9930840000 0.0002490000 1 1 1 v 0.0 0.0 0.0 mag 0.0
0.9988170000 0.5025970000 0.5036740000 1 1 1 v 0.0 0.0 0.0 mag 0.0
0.4969490000 0.5004760000 0.0053650000 1 1 1 v 0.0 0.0 0.0 mag 0.0
0.5033170000 0.9987410000 0.4977020000 1 1 1 v 0.0 0.0 0.0 mag 0.0
0.7471640000 0.2589800000 0.7582050000 1 1 1 v 0.0 0.0 0.0 mag 0.0
0.2489230000 0.2472750000 0.2563730000 1 1 1 v 0.0 0.0 0.0 mag 0.0
0.2531180000 0.7474660000 0.7389000000 1 1 1 v 0.0 0.0 0.0 mag 0.0
0.7518960000 0.7513820000 0.2395340000 1 1 1 v 0.0 0.0 0.0 mag 0.0

Environment

No response

Additional Context

No response

Task list for Issue attackers (only for developers)

  • Verify the issue is not a duplicate.
  • Describe the bug.
  • Steps to reproduce.
  • Expected behavior.
  • Error message.
  • Environment details.
  • Additional context.
  • Assign a priority level (low, medium, high, urgent).
  • Assign the issue to a team member.
  • Label the issue with relevant tags.
  • Identify possible related issues.
  • Create a unit test or automated test to reproduce the bug (if applicable).
  • Fix the bug.
  • Test the fix.
  • Update documentation (if necessary).
  • Close the issue and inform the reporter (if applicable).
@kirk0830
Copy link
Collaborator

kirk0830 commented Nov 1, 2024

you should use 1 instead of true, the throw of stoi means converting from string to integer.

@mohanchen mohanchen added the Bugs Bugs that only solvable with sufficient knowledge of DFT label Nov 1, 2024
@mohanchen
Copy link
Collaborator

@mohanchen mohanchen added Questions Raise your quesiton! We will answer it. and removed Bugs Bugs that only solvable with sufficient knowledge of DFT labels Nov 2, 2024
@mohanchen
Copy link
Collaborator

A nice question, it seems that you need to put 1 or 0, as described in the online document.

@mohanchen mohanchen self-assigned this Nov 2, 2024
@kirk0830
Copy link
Collaborator

kirk0830 commented Nov 2, 2024

A nice question, it seems that you need to put 1 or 0, as described in the online document.

@mohanchen other users used to have suggestions on this, maybe a simple function supporting 1, T, True, .TRUE., etc can solve this more gracefully, and this is what the solution of VASP.

@ErjieWu
Copy link
Collaborator Author

ErjieWu commented Nov 5, 2024

Image

A nice question, it seems that you need to put 1 or 0, as described in the online document.

The online document may have some issues as it requires users to use Boolean variable.

@kirk0830
Copy link
Collaborator

kirk0830 commented Nov 6, 2024

@ErjieWu ouch, thanks, now I realize what the real problem is. I will reopen this issue. Thanks for your comments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Questions Raise your quesiton! We will answer it.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants