Ticket #5882 (closed: fixed)
NormaliseByCurrent: remove or filter prominent ISIS-specific warning
| Reported by: | Russell Taylor | Owned by: | Owen Arnold |
|---|---|---|---|
| Priority: | minor | Milestone: | Release 2.4 |
| Component: | Mantid | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Tester: | Andrei Savici |
Description
Every time you run NormaliseByCurrent on SNS data you now get a log message, at warning level: "No nperiods property. If this is multi-period data, then you will be normalising against the wrong current."
This is meaningless for SNS users as there's no concept of periods, so it should be suppressed in this situation.
Change History
comment:2 Changed 8 years ago by Nick Draper
- Status changed from new to assigned
- Owner set to Owen Arnold
Maybe change this to info level or lower
comment:4 Changed 8 years ago by Owen Arnold
Nick suggests that Facility checking would not be a good option. I agree.
I'm going to de-escalate the log from Warning to Information. Note that this means that users will not be able to see it with the default Mantid settings (set to Notice.) We may want to re-escalate it to Notice, if this causes trouble in the future.
comment:5 Changed 8 years ago by Owen Arnold
refs #5882. De-escalate log level.
Changeset: 514256fe2f8c77fdcbd7f06e56062ee46c1933de
comment:6 Changed 8 years ago by Owen Arnold
- Status changed from accepted to verify
- Resolution set to fixed
comment:7 Changed 8 years ago by Owen Arnold
refs #5882. De-escalate log level.
Changeset: 514256fe2f8c77fdcbd7f06e56062ee46c1933de
comment:8 Changed 8 years ago by Andrei Savici
- Status changed from verify to verifying
- Tester set to Andrei Savici
comment:10 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 6728
Moved to release 2.4