Fix: DCAr vs eta and bug fixes - #27
Open
christianreckziegel wants to merge 3 commits into
Open
Conversation
…omparePasses template
… code cell 22 was killing kernel due to attempt of access of previously used canvas, usage of new name for the canvas at the new function call corrected the wrong behavior
…nction drawProjectionSliceHisto()
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
DCAr vs eta
.ipynbtemplates were updated to correctly truncate the values.setTrendRanges()function was leading to an error when generating the reports_ComparePassestemplate, correct index handling inside ofsetTrendRanges()function was fixedFixes on period template leading to kernel kill
normalize_distribution()function was being called for values out of boundsCode cell 22 was killing kernel due to attempt of access of previously used canvas, usage of new name for the canvas at the new function call corrected the wrong behavior