Ticket #9416 (closed: fixed)
Updated groupping file for Chronus
| Reported by: | Anders Markvardsen | Owned by: | Anders Markvardsen |
|---|---|---|---|
| Priority: | major | Milestone: | Release 3.2 |
| Component: | Muon | Keywords: | |
| Cc: | francis.pratt@… | Blocked By: | |
| Blocking: | Tester: | Nick Draper |
Description
Francis noticed grouping file was incorrect for Chronus.
Attached is the correct one
Attachments
Change History
Changed 6 years ago by Anders Markvardsen
- Attachment CHRONUS_Detector_Grouping_LF_608.2.xml added
with two detectors taken out
comment:2 Changed 6 years ago by Anders Markvardsen
With reference to the second attached file francis writes:
I found the problem, there are a couple of faulty detectors that have been flagged up in the Wimda exclude list (398 and 518). Is there a separate mechanism for excluding faulty detectors in Mantid? Otherwise just deleting these two from the grouping table will have the same effect (as in attached grouping file).
comment:3 Changed 6 years ago by Anders Markvardsen
- Status changed from assigned to inprogress
Updated default groupping file for chronus. re #9416
Changeset: 5297cc04904572870e4151d6053a0ebec69b65ab
comment:4 Changed 6 years ago by Anders Markvardsen
- Status changed from inprogress to verify
- Resolution set to fixed
To test:
- Open MuonAnalysis in MantidPlot
- Browse for .nxs file in
isis\inst$\NDXCHRONUS\Instrument\data\cycle_13_5
- Hopefully you will see a plot
- Go to groupping tab
Which should have two rows in Group Table with the 'fwd' group having Ndet=304 and 'bwd' group having Ndet=302
comment:5 Changed 6 years ago by Nick Draper
- Status changed from verify to verifying
- Tester set to Nick Draper
comment:7 Changed 6 years ago by Nick Draper
- Status changed from verifying to closed
Merge remote-tracking branch 'origin/feature/9416_chronus_groupping'
Full changeset: 52a98559d5caf6578372001c1819f18f9cac6a9b
