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

Mismatch in input wavefunction and output wavefunction even if they are in the same time step #48

Open
jc-oist opened this issue Nov 24, 2019 · 1 comment

Comments

@jc-oist
Copy link

jc-oist commented Nov 24, 2019

The bug can be replicated as follows:

  1. Perform a ground state and real time evolution, with more than 1 time step in real time evolution. Retrieve the wfc_ev_0 and wfc_evi_0 wavefunctions and create a new data.h5 file using this.
  2. Now only perform the real time evolution using the new data.h5 file. Retrieve the 'new' wfc_ev_0 and wfc_evi_0 wavefucntions.
  3. Compare the density profile of these two wavefunctions, you will see two different density profiles. There should be no difference between the density profiles since they should be the same wavefunctions both in time step = 0.
@leios
Copy link
Member

leios commented Nov 24, 2019

Note that this only seems to be an issue when the wavefunctions are written to the HDF5 file via the provided python scripts in write_data.py.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants