Ticket #5628 (closed: fixed)
Update and Ship POLREF IDF
| Reported by: | Owen Arnold | Owned by: | Owen Arnold |
|---|---|---|---|
| Priority: | critical | Milestone: | Release 2.2 |
| Component: | Mantid | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Tester: | Stuart Campbell |
Description (last modified by Owen Arnold) (diff)
Due to updates in the POLREF instrument configuration, we need a new IDF for POLREF.
- Produce a working IDF with the new OSMOND line detector component.
- Ensure that the dates in the IDF apply for the installation date ~10th July 2012 onwards, corresponding to the cycle start at ISIS.
- Ship the IDF with Mantid in the next release.
Change History
comment:1 Changed 8 years ago by Owen Arnold
- Status changed from new to accepted
- Priority changed from blocker to critical
- Description modified (diff)
comment:2 Changed 8 years ago by Owen Arnold
refs #5628. New IDF.
Changeset: 6d3fa172c535155b8d61cb79d606b65dfaff2b1e
comment:3 Changed 8 years ago by Owen Arnold
- Status changed from accepted to verify
- Resolution set to fixed
Tester: Tim Charlton, is already using this IDF with new data from POLREF. However, we should do a thorough check of the new definition. I suggest AT LEAST doing the following:
- Run LoadEmptyInstrment with the new Definition File, and check that no errors are given.
- Use the instrument view to verify that the new detector "OSMOND" appears and contains 640 pixels oriented along the z (up) axis.
- Take some data from the latest cycle on POLREF and load it into mantid. Check that the correct instrument definition is being used (as of 16th July 2012). Check the detector table for detector ids, and sensible theta values etc.
comment:4 Changed 8 years ago by Owen Arnold
As a note for future development:
There has been some mention of updating the IDF in the future to account for a slight horizontal offset in the pixels owing the the fact that the detector is curved. This does not seem to be a priority.
comment:5 Changed 8 years ago by Dereck Kachere
- Status changed from verify to verifying
- Tester set to Dereck Kachere
comment:6 Changed 8 years ago by Dereck Kachere
- Status changed from verifying to verify
- Tester Dereck Kachere deleted
- Run LoadEmptyInstrument is functional.
- "OSMOND" DOES NOT APPEAR IN INSTRUMENT VIEW.
- Looking at the data from the latest cycle of POLREF though, it looks like the number of locations in the IDF equates to the number of detector IDs (where Phi=0)
comment:7 Changed 8 years ago by Stuart Campbell
- Status changed from verify to verifying
- Tester set to Stuart Campbell
comment:8 Changed 8 years ago by Stuart Campbell
- Status changed from verifying to reopened
- Resolution fixed deleted
The new IDF looks ok, but if you load a file then it finds 2 IDFs that have valid dates, POLREF_Definition.xml and POLREF_DefinitionOSMOND.xml.
So it loads the first one.
comment:10 Changed 8 years ago by Owen Arnold
refs #5628. Final date the old IDF.
Changeset: 3631b885bb68ac09765ac423fb832e7cc6e81c88
comment:11 Changed 8 years ago by Owen Arnold
- Status changed from accepted to verify
- Resolution set to fixed
comment:13 Changed 8 years ago by Stuart Campbell
- Status changed from verifying to closed
Loading file now loads correct IDF (verified from log messages and workspace tree).
OSMOND appears in instrument tree view.
comment:14 Changed 8 years ago by Owen Arnold
refs #5628. Final date the old IDF.
Changeset: 3631b885bb68ac09765ac423fb832e7cc6e81c88
comment:15 Changed 8 years ago by Owen Arnold
refs #5628. Final date the old IDF.
Changeset: 3631b885bb68ac09765ac423fb832e7cc6e81c88
comment:16 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 6474
