Ticket #9263 (closed: fixed)
Point Detectors Treated as Monitor
| Reported by: | Owen Arnold | Owned by: | Owen Arnold |
|---|---|---|---|
| Priority: | blocker | Milestone: | Release 3.2 |
| Component: | Reflectometry | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Tester: | Martyn Gigg |
Description (last modified by Karl Palmen) (diff)
Run the following in MantidPlot
Load(Filename=r'//isis/inst$/Instruments$/NDXPOLREF/Instrument/data/cycle_13_5/POLREF00011040.nxs',OutputWorkspace='POLREF00011040', LoadMonitors=True)
Then open the detector table on the monitors workspace and you'll see the Point detector (detector id 1001) turning up there, but not appearing the the detector workspace.
Looking at LoadNexusMonitors and the HDFView of the nexus file above, it looks like an inconsistency in the file format is causing this issue. LoadNexusMonitors uses fixUDets to fix detector id to spectrum mapping. This looks to marry up the SPEC and UDET array in the isis_vms_compat group. The file lists 4 NXMonitor types, but the UDET table only seems to have entries corresponding to 3. SPEC contains 1-4, so when the SPEC index 4 is used to lookup UDET it finds the first detector rather than the last monitor (id=1001) and this bug propagates through the rest of the loading routines.
Change History
comment:2 Changed 7 years ago by Owen Arnold
- Status changed from assigned to verify
- Resolution set to fixed
Comment from user after he fixed the wiring table:
"It's fixed now. I had extended the monitor count down one line too far. -Tim"
comment:4 Changed 7 years ago by Martyn Gigg
- Status changed from verify to verifying
- Tester set to Martyn Gigg
