Ticket #2569 (closed: fixed)

Opened 10 years ago

Last modified 5 years ago

LoadEventNexus: run_start: use the second pulse or an average

Reported by: Janik Zikovsky Owned by: Janik Zikovsky
Priority: minor Milestone: Iteration 28
Component: Mantid Keywords:
Cc: Blocked By:
Blocking: Tester: Vickie Lynch

Description

... because sometimes DAS gives a times 0 as the first pulse.

Change History

comment:1 Changed 10 years ago by Janik Zikovsky

  • Status changed from new to accepted

comment:2 Changed 10 years ago by Janik Zikovsky

  • Status changed from accepted to verify
  • Resolution set to fixed

(In [9743]) Fixes #2569: use the second pulse time to find the run_start of event nexus.

comment:3 Changed 10 years ago by Peter Peterson

  • Status changed from verify to reopened
  • Resolution fixed deleted

NOM_629_event.nxs started in 1990 so FilterByTime_Start/_Stop breaks the gd_prtn_chrg when you load the first 480 seconds.

comment:4 Changed 10 years ago by Janik Zikovsky

  • Status changed from reopened to accepted

comment:5 Changed 10 years ago by Janik Zikovsky

  • Status changed from accepted to verify
  • Resolution set to fixed

(In [10171]) Fixes #2569: Another fix for DAS' 0 pulse time bug.

comment:6 Changed 9 years ago by Vickie Lynch

  • Status changed from verify to verifying
  • Tester set to Vickie Lynch

comment:7 Changed 9 years ago by Vickie Lynch

  • Status changed from verifying to closed

NOM_629_event.nxs works now with FilterByTime_Start=480. run_start is correct.

comment:8 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​3416

Note: See TracTickets for help on using tickets.