Bug in CalculateCoverageDGS #15182
Labels
Bug
Issues and pull requests that are regressions or would be considered a bug by users (e.g. crashing)
Direct Inelastic
Issues and pull requests related to direct inelastic
High Priority
An issue or pull request that if not addressed is severe enough to postponse a release.
Milestone
There is a problem when using the planning tool for direct geometry inelastic. In particular, the trajectories do not correspond to results from ConvertToMD if one uses projections
Here is the results from ConvertToMD
The script to generate it is:
When using the planning tool, one can use the projection u to be (1,1,0), projection v (1,-1,0)
One can also reverse the order of projections, but still plot (HH0) along x, and (H,-H,0) along y. I would expect the same result. But what I get is
I tracked down the issue, and is the way we store matrices. In CalculateCoverageDGS.cpp I set the rows of W matrix as the projection vectors, instead of the columns (lines 295-297)
The text was updated successfully, but these errors were encountered: