Copy values to a new vector that should solve snow model re-initaliza…#1377
Open
Copy values to a new vector that should solve snow model re-initaliza…#1377
Conversation
Pull Request Test Coverage Report for Build 23454101362Details
💛 - Coveralls |
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
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.
…tion errors
Pull Request Template
Description
Attempt at solving #1372
Hypothesis is that keeping a pointer for the snow data array and passing that to multiple tests caused the memory to be corrupted and the results to change. Copy these values into a vector so the underlying data doesn't change run to run.
Credit to Claude Sonnet for spotting the memory re-use. Blame to Claude Sonnet for some of the annoying tab/spacing changes on the close braces.
Fixes #1372
Corresponding branches and PRs:
Develop on all other branches
Unit Test Impact:
Expect tests to pass consistently across OSes
Checklist
Reminders- this section can be deleted
[Checking for PySAM Incompatible API Changes]
(https://github.com/NREL/SAM/wiki/PySAM-Incompatible-API-Changes-&-Regenerating-PySAM-Files).
[When do the PySAM files need to be regenerated?]
(https://github.com/NREL/SAM/wiki/PySAM-Incompatible-API-Changes-&-Regenerating-PySAM-Files#when-do-the-pysam-files-need-to-be-regenerated-via-export_config)