Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: pipe_tasks
-
Labels:
-
Story Points:12
-
Epic Link:
-
Sprint:Measurement-S14-2
-
Team:Data Release Production
Description
The switch to meas_base will involve changing the names of most measurement algorithms, as we're using a new naming convention that provides more traceability. This will break downstream code that:
- uses field names instead of slots to access measurements
- reads or modifies the list of configured-to-run algorithms.
Whenever possible, we should fix the former by converting them to use slots, as this will automatically provide backwards compatibility. I'm not yet sure how to handle the latter; the easiest solution would be to give up on full backwards-compatibility with meas_algorithms, but we might be able to find some way to make the old names aliases to the new ones during the deprecation period.
Attachments
Issue Links
- is duplicated by
-
DM-738 Fix any AFW Table version 0 dependencies
- Done
More meas_algorithms
I think I'd actually be okay with just switching SecondMomentStarSelector over to the new framework entirely, and removing support for the old one, at least if it still passes its own unit tests when using the new framework. Is there any reason you can think of why we'd still need the old one here? The main reason to keep the old one around is that we haven't quite reimplemented all the algorithms or fixed up the error-handling, but I don't think either of those are concerns here.