Ticket #4945 (closed: fixed)
SANS2D NEXUS: Investigate proton_charge garbage log entries in nexus files
| Reported by: | Anders Markvardsen | Owned by: | Anders Markvardsen |
|---|---|---|---|
| Priority: | critical | Milestone: | Release 2.2 |
| Component: | Mantid | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Tester: | Martyn Gigg |
Description
Loading lSANS2D00011971.nxs then the first three entries in the proton-charge log are:
-9223372036.854776 0.000257224
1.507000 0.00117489
1.607000 0.00118184
However opening this event nexus file in HDF view shows (framelog->proton_charge)
1.507000 0.00117489
1.607000 0.00118184
So for some reason an extra rubbish top log entry is added
Change History
comment:2 Changed 9 years ago by Anders Markvardsen
Addition warning with sans2d time entries wrong. re #4945
User will see a message: "Found entries in the proton_charge sample log with invalid pulse time!" when loading loading sans2d00011971. The sans group have asked for more warnings to be displayed so in addtion when adding sans2d files (where this is relevant for now) the following warning is displayed:
::SANS::WARNING: Time increments in the proton charge log of SANS2D00011971 are suspicious large. For example at time difference of 9223372038.36 seconds has been observed.
Changeset: 82460e79e4559da81604a8c101fbcffde6b0cabd
comment:3 Changed 9 years ago by Anders Markvardsen
Minor change to output comment. re #4945
Changeset: 1ef8e137edaade60c58a6844ed5f35ab80dca40e
comment:4 Changed 9 years ago by Anders Markvardsen
Change the time to "2 weeks" before extra warning. re #4945
Changeset: 82defa567e6f312abb20c74fa786944b3f4f94c6
comment:5 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.1 to Release 2.2
Moved at end of release 2.1
comment:6 Changed 8 years ago by Anders Markvardsen
- Status changed from new to accepted
- Summary changed from ISIS NEXUS: Adding extra proton_charge garbage log enry to SANS2D NEXUS: Investigate proton_charge garbage log entries in nexus files
comment:7 Changed 8 years ago by Anders Markvardsen
- Status changed from accepted to verify
- Resolution set to fixed
This investigation started with sans2d data could not be reduced. It was identified that the garbage entries was written to the nexus files, which was then found to be due to a faulty card on the beamline.
To help more easily observe if this happens again on isis sans instruments an additional warning is displayed if similar faulty data are loaded.
comment:8 Changed 8 years ago by Martyn Gigg
- Status changed from verify to verifying
- Tester set to Martyn Gigg
comment:10 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 5791
Turn out to be a fault with an additional detector card on the beamline of SANS2D activated recently.
More specifically this for SANS2D00011971.nxs resulted in in SANS2D00011971.nxs, in framelog the times around entry number 3587 in HDFview of Nexus file are:
3586 359.905
3587 -1.29755361E10
3588 360.005
In SANS2D00011971 out of 8439 entries two times are recorded wrongly.