[DAMD-88] Replace pfsFiberTrace with pfsFiberProfiles Created: 19/Sep/20 Updated: 05/Jan/21 Resolved: 03/Nov/20 |
|
| Status: | Done |
| Project: | Data Model |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Normal |
| Reporter: | price | Assignee: | price |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Story Points: | 2 | ||||||||
| Sprint: | 2DDRP-2021 A | ||||||||
| Reviewers: | hassan | ||||||||
| Description |
|
pfsFiberTrace contains both the profile and the position of the trace, but the position of the trace is also in the detectorMap, a confusing duplication. Furthermore, because the pfsFiberTrace contains the profile realised for a particular trace position, it's not possible to realise the profile at a different position (the profile is undersampled, so we can't just resample). In order to be able to realise the trace at a different position, we need to store the profile, and not the realised profile. I propose to replace pfsFiberTrace in the datamodel with a new object, pfsFiberProfiles. |
| Comments |
| Comment by price [ 03/Nov/20 ] |
|
This has been ready for a long time (same time as |
| Comment by price [ 03/Nov/20 ] |
|
Merged to master with hassan's blessing. |