Opened 18 years ago
Last modified 18 years ago
#1128 assigned enhancement
detrend creation validates detrend even if all are input are excluded
| Reported by: | eugene | Owned by: | Paul Price |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | ippScripts | Version: | unspecified |
| Severity: | minor | Keywords: | |
| Cc: |
Description
Not sure where this is happening, but probably in detrend_reject_exp.pl. I have an example of a DARK run in which a bug in ppMerge result in nonsense fits, and the residuals all rejected. But, the detrend master was accepted anyway.
Note:
See TracTickets
for help on using tickets.
The REJECTIONS recipe contains a boolean that forces the "master" attribute for a detrend stack, even if anything or everything was rejected. For SIMTEST, this is turned on:
ITERATION BOOL FALSE # Are iterations permitted?
MASTER BOOL TRUE # Force stacks to be accepted as a master?