Ticket #1727 (closed: duplicate)
Geometry files: support changing instrument geometry in time
Reported by: | Janik Zikovsky | Owned by: | Anders Markvardsen |
---|---|---|---|
Priority: | major | Milestone: | Iteration 27 |
Component: | Mantid | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: | Nick Draper |
Description
- There needs to be more than one file per instrument.
- Geometry filename needs to be more flexible. For example, SNAP_Definition_2010-10-13.xml should be a valid file.
- A routine to find the appropriate geometry for a given run date/time, based on the geometry date, needs to be written and used in the loading algorithms.
- In the end, if a user loads run 22 when there were 10 detectors, the instrument needs to be correct for THAT run; later run 400 may have more detectors, load THAT geometry.
Change History
comment:1 Changed 10 years ago by Nick Draper
- Owner set to Anders Markvardsen
- Status changed from new to assigned
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:4 Changed 10 years ago by Anders Markvardsen
- Status changed from accepted to verify
- Resolution set to duplicate
This was implemented in #1997.
Note: See
TracTickets for help on using
tickets.