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

feat/bug: Update SST1 i0 correction #18

Open
pdudenas opened this issue Oct 25, 2021 · 4 comments · Fixed by #67
Open

feat/bug: Update SST1 i0 correction #18

pdudenas opened this issue Oct 25, 2021 · 4 comments · Fixed by #67

Comments

@pdudenas
Copy link
Collaborator

Some of the headerdict keys used in the correction step for the SST1 loadSingleImage function are from ALS 11.0.1.2 and don't work for SST1 data. This is part of a larger issue on normalization. To do this properly we need to read in the sample Au mesh current and a calibration scan under the same conditions.

@pdudenas pdudenas changed the title Update SST1 i0 correction feat/bug: Update SST1 i0 correction Oct 25, 2021
@pbeaucage
Copy link
Collaborator

This would be really great! I think the place I would start with it would be in the Databroker loader since we have (theoretically) infinite access there to any scan (so you can just specify a scan number for the calibration). The Au mesh is pretty easy in DB as well.

@EliotGann
Copy link
Collaborator

In the future this will be much easier with a preprocessor for diode calibrations... working on that now on the acquisition side. then there will be a new stream just like the dark stream now, which just includes the calibration scan

@pbeaucage
Copy link
Collaborator

I0 correction, albeit without a i0 / diode correction term, is implemented in commit 45cdfe9 along with support for getting monitor values at all points.

@pbeaucage
Copy link
Collaborator

pbeaucage commented Jun 5, 2022

OK, so we have i0 now in the form of the mesh reading. The thing we really need, though, at least I think so in a mildly sleep deprived state, is to multiply the measured mesh(E,pol,slitconfig) by the ratio (diode/mesh)(E,pol,slitconfig) for an open beam diode scan so as to get the true i0.

What is the best way to get that function in? There are several good options:

  • have the user do the matching of slitconfig and provide a scan number in E/pol space. Our loader can munge that scan into (diode/mesh)(E) and make i0 from that ratio
  • have a preparation process generate a LUT of (diode/mesh)(E,pol) as a h5 or nc file and have the user provide (or loader grab from somewhere) the appropriate LUT.
  • something else entirely.

@pdudenas @EliotGann

@BijalBPatel BijalBPatel linked a pull request Feb 14, 2023 that will close this issue
@BijalBPatel BijalBPatel reopened this Feb 16, 2023
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

Successfully merging a pull request may close this issue.

4 participants