Ticket #1803 (closed: fixed)
Obtain example of Muon IDFs valid between different periods
| Reported by: | Anders Markvardsen | Owned by: | Anders Markvardsen |
|---|---|---|---|
| Priority: | major | Milestone: | Iteration 27 |
| Component: | Mantid | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Tester: | Michael Whitty |
Description
For one of the Muon instruments obtain instrument definition files (IDFs) valid between different time periods due to upgrades of instruments.
Decide how we will handle the case of having multiple IDFs. For instance, how to insure the correct IDF and corresponding parameter file is loaded when user select a raw file or Nexus file.
Once we have a multi-IDF example it seems to make sense to change the IDF notation from
<instrument name="CSP" date-time="yyyy-mm-ddThh:mm:ss">
to (currently the data-time is not used by Mantid)
<instrument name="CSP" from-date="yyyy-mm-ddThh:mm:ss"
to-date="yyyy-mm-ddThh:mm:ss">
Change History
comment:2 Changed 10 years ago by Nick Draper
- Milestone changed from Iteration 26 to Iteration 27
Bulk move of tickets to iteration 27, if your ticket is essential for Iteration 26 then move it back.
comment:5 Changed 10 years ago by Anders Markvardsen
Note the code for allowing multiple IDFs was implemented in #1997.
comment:7 Changed 10 years ago by Anders Markvardsen
- Status changed from accepted to verify
- Resolution set to fixed
comment:8 Changed 10 years ago by Michael Whitty
- Status changed from verify to verifying
- Tester set to Michael Whitty
comment:9 Changed 10 years ago by Michael Whitty
- Status changed from verifying to closed
this has been done.
comment:10 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 2650
Still waiting for multiple Muon IDF example but how to implement multi IDF handling discuss and ticket created #1997