Opened 14 years ago

Closed 13 years ago

#181 closed bug (fixed)

T_wide used in calculations

Reported by: ajj Owned by: ajj
Priority: minor Milestone: USANS Reduction 2.3 Release
Component: Analysis Keywords:
Cc: Blocking:


Check whether use of T_wide in calculations for normalization is correct.

This is a problem when data isn't measured out far enough in Q.

Change History (4)

comment:1 Changed 13 years ago by srkline

  • Milestone changed from USANS Reduction Wish List to USANS Reduction 2.3 Release

comment:2 Changed 13 years ago by srkline

T_Wide should be normalized by the monitor count, but it isn't.

The T_wide value is found from a running average of angles > 2.0

Do we need intervention if this is not present say manually enter a value, or use the "lowest" 5 points available, and display a warning message that T_wide may be suspect. It's clear from a plot of the raw data if the transmission detector counts have leveled off, so suggest that the users look at that.

comment:3 Changed 13 years ago by srkline

don't just normalize - either look for and ignore zeros, or normalize the sum of trans counts by the sum of monitor counts

comment:4 Changed 13 years ago by srkline

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

now normalized to the monitor counts. Also, when data > 2 degrees is not present, a warning is presented and the last 4 data points of whatever is present is used (and appears to be not too bad).


Note: See TracTickets for help on using tickets.