-
Notifications
You must be signed in to change notification settings - Fork 50
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
openpmd-api backend forgets modes m>1 #310
Comments
Hi, |
Thanks for reporting this! |
Hi @soerenjalas, can you please post a tiny example file and python example that demonstrates this for debugging? I looked at the code but cannot spot an obvious bug right away. |
Hi all, The file contains an (empty) hdf5 output from fbpic with 3 modes. Running, d = OpenPMDTimeSeries('.', backend='h5py')
d.get_field(iteration=0, field='rho', m=2) works fine, but d = OpenPMDTimeSeries('.', backend='openpmd-api')
d.get_field(iteration=0, field='rho', m=2) raises an OpenPMDException as if the file didn't contain mode 2.
It looks like on the viewer side the code for h5py and openpmd-api is quite analogue, could this be an issue within the api? Tested with this constellation: |
Thank you for the details, this is great! |
Hi,
this might a bit of an edge case issue but it caused a bit of confusion for me so I thought it might be good to document. I have the case where I load a timeseries (fbpic) in a jupyter notebook via
d = LpaDiagnostics('lab_diags/hdf5', backend='openpmd-api')
, and retrieve the fields withd.get_field()
. Now I changed reran the simulation (going from 2 to 3 theta modes). After rerunning the cell to import the timeseries get_field() still returns the old fields now. Withbackend='h5py'
I get the new data as expected.Is there some sort of caching going on with the openpmd-api that needs to be cleared?
The text was updated successfully, but these errors were encountered: