-
Type: Task
-
Status: Done (View Workflow)
-
Priority: Normal
-
Resolution: Done
-
Component/s: None
According to the discussion in the software meeting, cobra_target current contains two kinds cobra information, before and after the move, respectively. We should separate them into two different tables. So that cobra_target keeps the information from the prediction and cobra_move contains the actual move measured from MCS/FPS.
- relates to
-
INSTRM-1655 Write Cobra Movement Data to cobra_target
- Done
-
INSTRM-2015 Change the foreign key constraint of `cobra_move` and `cobra_match`
- Done