[JUNGFRAU] [Correct] Add thresholding for ROI projections

Description

FXE asked us to extend the ROI projection we already integrated with a threshold, zeroing out pixels below that threshold before reducing the ROI to a 1D curve. This gets rid of a lot of remaining noise (see the screenshot below).

How Has This Been Tested?

Ran the notebook interactively on p3279 r275, with ROI definition [3, 405, 450, 0, 1024, -2] (supplied by Yohei), with no thresholding and with the threshold set to 1.

Relevant Documents (optional)

Average of the projected ROI spectrum over the whole run, with / without thresholding:

Types of changes

• New feature (non-breaking change which adds functionality)

Checklist:

• My code follows the code style of this project.

Reviewers

@ahmedk @schmidtp @uemuray

Another test case, p3435, r199, with no threshold or with threshold set to 2:

added 1 commit

• 497c877c - Set default threshold to 2

Compare with previous version

I see that you left the default threshold to 2. How often do you think this threshold value will need to be changed? Same rate as the ROI or different?

Yohei suggested 2 as a default - apparently they're unlikely to use this for emitted photon energies below 4 keV, so 2 is at most half a photon. If they want a different threshold, it sounds like requesting it at the same time as the ROIs should work.

Yohei also told me that they'll only need one threshold for all ROIs, so that's what I've implemented, to keep it simple.

LGTM

added 1 commit

• 16e33505 - Record threshold as RUN data in files

Compare with previous version

I just remembered that I store the other ROI parameters in the output files, so I've added the threshold to this as well. It's accessible like this:

run['FXE_XAD_JF1M/ROIPROC/JNGFR01'].run_value('roi1.threshold')

merged

mentioned in commit 492698d6

changed milestone to %3.11.2

changed milestone to %3.11.3