-
Notifications
You must be signed in to change notification settings - Fork 199
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
CI: Test New v. Legacy BTD in BTD_ReducedSliceDiag
#3371
Conversation
When I compare the legacy BTD output with the new BTD output in the Python analysis (see files changed in this PR), I get Ez arrays of different shapes:
Note that the new BTD array with plotfile and openPMD formats agree with each other up to machine precision, so that's consistent. I cannot yet compare those with the legacy array because of the mismatch in the shapes. Do you have any hints on where the snapshot = './lab_frame_data/snapshots/snapshot00003'
header = './lab_frame_data/snapshots/Header'
allrd, info = read_raw_data.read_lab_snapshot(snapshot, header)
Ez_legacy = allrd['Ez'] |
BTD_ReducedSliceDiag
BTD_ReducedSliceDiag
BTD_ReducedSliceDiag
BTD_ReducedSliceDiag
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.
Thanks for working on these tests! They look good to me
BTD_ReducedSliceDiag
BTD_ReducedSliceDiag
BTD_ReducedSliceDiag
BTD_ReducedSliceDiag
* CI: Test New BTD in `BTD_ReducedSliceDiag` * Compare Legacy BTD vs. New BTD * Fix Bug in Loading of openPMD Array Data * Fix CI Analysis
Keep adding more CI coverage of the new BTD, see #3300. Similar to #3327.
Main changes:
BTD_ReducedSliceDiag
, evaluated on the BTD plotfile dataTo-do:
ions
species is not written to output (new BTD): clarified, see comments in BTD: Issue w/ Particle Output of Back-Transformed Diagnostics #3420.Note:
We cannot compare legacy BTD data with new BTD data (either plotfile or openPMD), because the array shapes are different (see comment below). As far as I understood from @RTSandberg, this is a known discrepancy and it is not expected to be taken care of any time soon.