Ticket #3270 (closed: fixed)

Opened 9 years ago

Last modified 5 years ago

EQSANS: beam center is at the wrong position

Reported by: Mathieu Doucet Owned by: Mathieu Doucet
Priority: major Milestone: Iteration 29
Component: Mantid Keywords:
Cc: Blocked By:
Blocking: Tester: Martyn Gigg

Description

The pixel (0,0) is at the wrong position (should be the lower right quadrant). The default center is not exactly the center of the detector, which needs to be corrected for.

Change History

comment:1 Changed 9 years ago by Mathieu Doucet

  • Status changed from new to accepted

comment:2 Changed 9 years ago by Mathieu Doucet

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

(In [12895]) Fix beam center and pixel coordinates. Fixes #3270

comment:3 Changed 9 years ago by Mathieu Doucet

  • Milestone changed from Iteration 30 to Iteration 29

comment:4 Changed 9 years ago by Martyn Gigg

  • Status changed from verify to reopened
  • Resolution fixed deleted

This change has broken the EQSANS system test. It may just need the reference result updating?

comment:5 Changed 9 years ago by Mathieu Doucet

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

(In [12905]) Fix the system test. Fixes #3270

comment:6 Changed 9 years ago by Steve Williams

  • Status changed from verify to verifying
  • Tester set to Steve Williams

comment:7 Changed 9 years ago by Steve Williams

  • Status changed from verifying to verify
  • Tester Steve Williams deleted

Someone else please test this I have to leave for the day

comment:8 Changed 9 years ago by Martyn Gigg

  • Status changed from verify to verifying
  • Tester set to Martyn Gigg

comment:9 Changed 9 years ago by Martyn Gigg

  • Status changed from verifying to closed

Mathieu is happy that the new reference result is correct and the detector seems to be at the correct coordinates after the MoveInstrumentComponent call.

comment:10 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​4117

Note: See TracTickets for help on using tickets.