Conversation
|
should we keep modifying the model under the hood for the use of algorithms to make sense or should we raise an explanatory exception educating the user on the propor use of the algorithm ? @murilobalves , @fernandohds564 , @vellosok75 , @Gabrielrezende-asc another concern: potential inconsistencies because of temporary modifications of the model when threads that use the same model are running. |
|
I think we should drop this behavior and raise exceptions when the model state doesn't match what is expected. |
agreed |
|
@murilobalves , @vellosok75 , do you want to take a position on this ? @Gabrielrezende-asc , if others do not object, I think we can proceed with what fernando and I agreed. |
I agree. I prefer raising exceptions. |
| @@ -262,6 +261,8 @@ def set_delta_kicks(self, dkicks): | |||
| def set_kicks(self, kicks): | |||
There was a problem hiding this comment.
Also, shouldn't we be working with the set_delta_kicks method in correct_orbit? I believe the set_kicks is incorrect since the pseudo-inversion is giving us deltas, right?
There was a problem hiding this comment.
This function applies the kicks. The delta kick values are computed and processed before this function is called.
I agree with raising exceptions. |
|
Ok guys, as soon as I finish tasks related to the VPU commissioning I will continue this PR |
Co-authored-by: fernandohds564 <fernandohds564@gmail.com>
A possible problem in the orbit correction class: