[PIPE2D-103] Running constructFiberTrace doesn't report failure Created: 15/Oct/16 Updated: 27/Mar/21 Resolved: 27/Mar/21 |
|
| Status: | Done |
| Project: | DRP 2-D Pipeline |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Major |
| Reporter: | rhl | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
I just ran FindAndTraceAperturesTask on an arc image and it silently found no traces. The behaviour is fine, but please add diagnostics. Probably the simplest is to include the expected number of traces as a config parameter; in the future we may want better diagnostics (e.g. by comparing with a previous FiberTraceSet) – but for now a check that the expected number of fibres is found is OK. |
| Comments |
| Comment by price [ 27/Mar/21 ] |
|
BuildFiberProfilesTask with doBlindFind=True will warn if it fails to identify GOOD fibers from the pfsConfig. |