Fixed a bug of using non-inverse error for weights #70
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When I was looking into the issue #69, I found that when averaging the telescope-wise reconstructed directions the pipeline uses the errors which are not inverse. This makes the reconstruction performance worse because it weights to the reco parameter whose error is large. I checked that fixing this issue and using the inverse errors improve the angular resolutions, please see the attached two plots for the comparison of the resolutions before and after fixing the bug.
@jsitarek, since it would affect your analysis, please give me an approval when you acknowledge this fix. Thanks!