back_prop_dssc_correction

@karnem This notebook is used for correcting DSSC. It was changed directly in the production service and then I modified it to make sure it correctly runs and show better messages in case of no offset(which was the case when the notebook failed before.)

@samartse

unmarked as a Work In Progress

added 1 commit

• 77a3e215 - sequences default -1

Compare with previous version

added 1 commit

• 77a3e215 - sequences default -1

Compare with previous version

added 1 commit

• 77a3e215 - sequences default -1

Compare with previous version

added 1 commit

• a6156792 - working DSSC correction notebook version

Compare with previous version

changed the description

added 1 commit

• f633be9a - MR comments

Compare with previous version

dsscofflinecorrection.pdf @karnem the report for the run that had issues in the beginning

changed the description

Apart small comments LGTM.

By the "last constant in the database" meant really the constants acquired in the same session, just before the measured run, or after it. we have discussed it. Not the really last one from "yesterday" to be applied for the measurements collected half a year ago...

If the darks are acquired in another session (after detector powering off), they can not be in principle used with the data from new measurement session.

Okay that is very different then from what I understood. This means then that the flag should be True as before

added 1 commit

• 011914d7 - set dir_creation bool to true

Compare with previous version