Details
-
Type:
Story
-
Status: In Progress
-
Resolution: Unresolved
-
Fix Version/s: None
-
Labels:None
-
Story Points:6
-
Epic Link:
-
Team:Data Release Production
-
Urgent?:No
Description
Prototype an approach to the "versioned cameras" concept that allows camera definitions and datasets to be unversioned (representing a "nominal camera"), with all versioned quantities stored in IsrCalib objects in data repositories; that versioned content will be added to the Camera object on read via new factory classes/methods.
This ticket is prep work for an RFC on the topic, which will include much more detail on the plan and philosophy; I just want to work through some open questions by trying to code pieces of them first.
Attachments
Issue Links
- is triggered by
-
- Adopted
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | To Do [ 10001 ] | In Progress [ 3 ] |
| Story Points | 2 | 6 |
| Summary | Prototype versioned camera assembly | Finish versioned camera assembly |
| Summary | Finish versioned camera assembly | Implement versioned camera assembly |
I'm repurposing this ticket as an implementation ticket for RFC-842, since the prototype was never going to be merged on its own anyway.
I believe much of the code on the prototype is still valid, but there's a lot more work to do to implement the final RFC proposal (which I won't bother repeating here).
Note to self: current story-point estimate reflects work already done, back in the prototyping phase.