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

Add mechanism for setting sample and detector bank offset in Zoom workflow #59

Merged
merged 8 commits into from
Feb 1, 2024

Conversation

SimonHeybrock
Copy link
Member

@SimonHeybrock SimonHeybrock commented Jan 30, 2024

Related to #52 (but not a fix since the end goal is to parse the file that contains this info).

@@ -69,6 +69,8 @@
" sans.isis.CalibrationFilename: '192tubeCalibration_11-02-2019_r5_10lines.nxs',\n",
" sans.isis.Filename[sans.types.SampleRun]: 'ZOOM00034786.nxs',\n",
" sans.isis.Filename[sans.types.EmptyBeamRun]: 'ZOOM00034787.nxs',\n",
" sans.isis.SampleOffset: sc.vector([0.0, 0.0, 0.11], unit='m'),\n",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these mostly required because of the IDF mechanism in Mantid/ISIS?
Will the situation be better at ESS with the nexus geometry, or are we expecting the geometry in the files to not be updated for every experiment and often be out of date?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think ECDC wants to keep files up to date, but if that will be actually true in practice...


from ..types import RawData, RunType

PixelMask = NewType('PixelMask', sc.Variable)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is also defined in masking.py. Should it be defined only once?

PixelMask = NewType('PixelMask', sc.Variable)


class ConfiguredRawData(sciline.Scope[RunType, sc.DataArray], sc.DataArray):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about the name. Immediately it wasn't very clear what it was meant to represent.
What kind of other configurations are we expecting apart from custom offsets? Should we have a name that is specific to applying offsets?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you have a suggestion?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RawDataWithComponentUserOffsets?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we also rename the provider? I guess configure_raw_data made more sense when the output was called ConfiguredRawData?

@SimonHeybrock SimonHeybrock merged commit dd185ff into main Feb 1, 2024
3 checks passed
@SimonHeybrock SimonHeybrock deleted the user-position-config branch February 1, 2024 13:10
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 this pull request may close these issues.

2 participants