Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: Gap translations in Blueprint Helper (#3027)
Introducing small changes into the way translations are handled in the `BlueprintHelper` gap filling. Previously, because the rotation of a gap volume was applied before the translation, the gaps were positioned in the wrong points of the global coordinates. This was due to the fact that `negC` and `posC` are already defined in the rotated frame. The change solidifies the global way of defining the transformations in the user code, which seems to be consistent with the way it is handled across the `Blueprint`. To give an example: if the user code tries to fill the gaps in the detector rotated by `pi/2`, the `negC`, `posC` would've been calculated along the already rotated axis. Then, the gap transformation would've been constructed and the filling volume would've been sent along the `pi` with respect to the initial global coordinates, as the rotation would've been effectively applied twice. Now, the fact that the rotation is already present in the translation vector is taken into account.
- Loading branch information