Opened 16 years ago

Closed 15 years ago

#2 closed feature (fixed)

NxM detector size in SANS Reduction

Reported by: srkline Owned by: srkline
Priority: major Milestone:
Component: SANS Reduction Keywords:
Cc: Blocking:


Fri Jan 05 09:04:05 2007 butler - Ticket created

Subject: nxn reduction capability

Again as discussed in the December meeting, Steve is to verify that the
implementation of nxn detectors is complete in the reduction macros.
Also will start to look into how best to implement choosing the type of
detector being used. In the short term the feature will likely be used
by other facilities rather than us, so just choosing which facility the
data came from may be appropriate. However, when we implement a higher
resolution detector (for VSANS for example) which type of data from the
same instrument may be required. Priority is set to 3 here mainly for
the first part (verifying that the implementation is complete) as it
impacts our ability to establish a viable collaboration.

reference RT:

Change History (1)

comment:1 Changed 15 years ago by srkline

  • Resolution set to fixed
  • Status changed from new to closed

As far as I can tell, the code for reduction is now NxM generic - the detector need not be square, either. The number of pixels in the X and Y directions on the detector are now global variables that are set by the raw data loader. Until I hear from Ken that there's any bit of code that I missed, I consider this closed. The RT ticket is also closed.


Note: See TracTickets for help on using tickets.