Fix sparse CT scenario indexing#905
Open
acsevillam wants to merge 1 commit into
Open
Conversation
Contributor
|
Can you check if this ist sill relevant on the dev branch? As said in #904 , the dev_varRBErobOpt has been merged into dev a while ago (and was also part of the last releases), and I remember fixing something similar on dev. |
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
2 participants
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.
Bug description
Sparse CT scenario models can fail when the active CT scenario id is not equal to its row position in ctScenProb.
Approach
This PR disambiguates CT scenario position from real CT scenario id in sub2scenIx and fixes extractSingleScenario to select ctScenProb rows by CT scenario id.
Open Questions and/or Concerns
References
None.