fixed bug in writing statefile for 2-d lat/lon dimensions #652
Conversation
This file contains 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
… the 2-D lats/lons were written as fill values to the state file rather than lats/lons
jhamman
approved these changes
Nov 16, 2016
|
@dgergel looks good to me. |
dgergel
added a commit
to dgergel/VIC
that referenced
this pull request
Dec 29, 2016
bartnijssen
added a commit
that referenced
this pull request
Jan 4, 2017
this PR adds a release entry note to PR #652
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.
2-D lats/lons were being written to state file as fill values rather than actual lats/lons, this PR fixes that.