[PIPE2D-888] DisplayDetectorMap should allow user to specify fibres to overlay Created: 24/Aug/21 Updated: 13/Jan/22 |
|
| Status: | Open |
| Project: | DRP 2-D Pipeline |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | hassan | Assignee: | hassan |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Story Points: | 1 | ||||||||||||
| Sprint: | 2DDRP-2021 A 8 | ||||||||||||
| Description |
|
When running DisplayDetectorMapTask, the resultant display can be sluggish to manipulate when many fibers are overlaid, as is the case when examining SuNSS data or complete PFI data. Please provide a means to allow the user to specify the fibers that should be overplotted. |
| Comments |
| Comment by rhl [ 24/Aug/21 ] |
|
I'm not sure that this is the correct solution, it maybe the backend display code. My impression is that the matplotlib-only showDetectorMap doesn't suffer from this problem. |
| Comment by price [ 24/Aug/21 ] |
|
DetectorMap.display should be changed to only plot every Nth point in the traces like showDetectorMap does, and it will go faster. |
| Comment by hassan [ 24/Aug/21 ] |
|
Paul's suggestion is also fine. I'll do that if everyone agrees. |
| Comment by rhl [ 24/Aug/21 ] |
|
This may be good as a quick fix, but in general I'd rather merge the two utilities. |