-
Notifications
You must be signed in to change notification settings - Fork 15
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
Improvement on state #119
Improvement on state #119
Conversation
scemama
commented
May 11, 2023
- The state id is used as an index for the file names, so it is preferable to use state_id as an index instead of an integer.
- I added energy to store the energy of the state
|
OK
I was just implementing this in QP for multi-state calculations. I am writing files in Fortran, and reading the produced files in Python. I got very confused: In the Fortran world, it is natural to consider the ground state as state 1, and the first excited state as state 2, because these are the indices used for that in all the arrays that contain multiple states. For example, I always have loops like:
so it is natural to set the state id as Also, it is the index in the arrays
Oh no! you are right, it doesn't work. I will fix it. |
I see what you mean, but this is related to QP. There might be codes (e.g. linear response TD-DFT) which store info about their excited states in a separate array, so there state_id=1 would be the first excited state in their Fortran array, but in the |
Now index type it works with scalar values :-) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, thanks!