Ticket #2524 (closed: fixed)

Opened 10 years ago

Last modified 5 years ago

DspacemaptoCal problem with VULCAN input

Reported by: Vickie Lynch Owned by: Vickie Lynch
Priority: major Milestone: Iteration 28
Component: Mantid Keywords:
Cc: zikovskyjl@… Blocked By:
Blocking: Tester: Stuart Campbell

Description

VULCAN data looks worse after Dspacemap is applied.

Attachments

Dspace_VULCAN.png​ (321.9 KB) - added by Vickie Lynch 10 years ago.
VULCAN_noCorrection.png​ (334.0 KB) - added by Vickie Lynch 10 years ago.

Change History

comment:1 Changed 10 years ago by Vickie Lynch

  • Status changed from new to accepted

comment:2 Changed 10 years ago by Vickie Lynch

(In [9664]) Refs #2524 l2 must be the center of the Rectangular Detector if VULCAN Corrections are read in DspacemaptoCal

Changed 10 years ago by Vickie Lynch

Changed 10 years ago by Vickie Lynch

comment:3 Changed 10 years ago by Vickie Lynch

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

VULCAN correction file corrects the TOF to the center of the Rectangular Detector. Added checkbox to AlignDetectors to use parent of each detector pixel for l2. Also corrected DspacemaptoCal for the factor to be a power of 10. Results attached in Dspace_VULCAN.png use the corrections and those in VULCAN-noCorrection.png do not. Will update WIKI with these options.

comment:4 Changed 10 years ago by Vickie Lynch

(In [9665]) Refs #2524 Fix doxygen warnings for my changes

comment:5 Changed 9 years ago by Stuart Campbell

  • Status changed from verify to verifying
  • Tester set to Stuart Campbell

comment:6 Changed 9 years ago by Stuart Campbell

using the script on #2523 to test.

comment:7 Changed 9 years ago by Stuart Campbell

  • Status changed from verifying to closed

Output look like picture.

comment:8 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​3371

Note: See TracTickets for help on using tickets.