Opened 15 years ago
Closed 12 years ago
#33 closed task (wontfix)
2D error matrix
Reported by: | srkline | Owned by: | kline |
---|---|---|---|
Priority: | major | Milestone: | SANS Reduction 5.2 Release |
Component: | SANS Reduction | Keywords: | |
Cc: | Blocking: | ||
Task: |
Description
This will need to be generated if the 2D analysis is to proceed in a meaningful way. John has done the work for this - there are routines on the VAX (ADD/ERROR) and equations in a memo for how to do this. The 2D error matrix is propogated through the reduction steps
We'll need to come up with a way to handle this, and a way to output the error (and keep it with the data set!) Possibly as a 4th column in the QxQy? ASCII output. (for the 2D ASCII?)
Change History (3)
comment:1 Changed 14 years ago by srkline
- Milestone set to SANS Reduction Wish List
comment:2 Changed 13 years ago by srkline
- Milestone changed from SANS Reduction Wish List to SANS Reduction 5.2 Release
comment:3 Changed 12 years ago by srkline
- Resolution set to wontfix
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
I don't see where this is necessary. If the data is not averaged to I(Q), then each pixel is what it is, and the error is sqrt(counts). This error doesn't need to be in the data file - it can simply be calculated after the fact.
There are probably cases where the error could be propagated through the reduction step, but I say shelve it for now.