You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix ZOOM NormaliseByCurrent bug - Ensure period logs are added to monitor workspaces in line with Event workspaces (#39983)
### Description of work
A change was made in #39322
that uses the `current_period` log to calculate the proton charge.
This `current_period` log is added to all event workspaces that have
certain logs associated with period data, even if the data only has one
period:https://github.com/mantidproject/mantid/blob/583bca96a8f7b721c2efb5a024b0832f0d60d8e5/Framework/DataHandling/src/LoadEventNexus.cpp#L958
When loading monitors into a separate workspace as part of
`LoadEventNexus`, `LoadNexusMonitors` in contrast does NOT add this
property for workspaces that have only 1 period. This PR changes this so
that the function enabling the `splitMutiPeriodHistrogramData` function
to operates on all workspaces with periods of >0.
Closes#39831
- When loading monitors with period data (``LoadNexusMonitors2``), period sample logs are now added to the resultant workspace; This is in line with the creation of Event Workspaces. This fixes a bug that occurred when ``NormaliseByCurrent`` was used on the monitor workspace.
0 commit comments