subset_data: Fix conversion of Longitude to string#3286
Merged
samsrabin merged 9 commits intoESCOMP:b4b-devfrom Jun 27, 2025
Merged
subset_data: Fix conversion of Longitude to string#3286samsrabin merged 9 commits intoESCOMP:b4b-devfrom
samsrabin merged 9 commits intoESCOMP:b4b-devfrom
Conversation
Disallow implicit conversion because we want the user to specify which type they want.
Makes it so that NO tests in that file will work outside CESM-supported machines.
4817233 to
4b50783
Compare
6 tasks
samsrabin
commented
Jun 27, 2025
slevis-lmwg
approved these changes
Jun 27, 2025
Contributor
slevis-lmwg
left a comment
There was a problem hiding this comment.
@samsrabin and I went over this PR in detail today.
@samsrabin already documented a concern that I expressed, by opening issue #3293.
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.
Description of changes
Resolves an issue in
subset_datawhere Longitude types were being implicitly converted to string to look like<ctsm.longitude.Longitude object at 0x7f34cb836a90>. Now, implicit string conversion is disallowed—the user must specify the type of longitude they want.Also adds testing:
subset_dataoutput filescreate_newcaseworks withsubset_dataoutputsNew CIME SystemTest SUBSETDATAPOINT.No; moving to a different PR.Specific notes
Contributors other than yourself, if any: None
CTSM Issues Fixed:
Are answers expected to change (and if so in what way)? No
Any User Interface Changes (namelist or namelist defaults changes)? No
Does this create a need to change or add documentation? Did you do so? No
Testing performed, if any: As of 319ea5a (worked at aca0a5d):
Also:
clm_pymodssuite:/glade/derecho/scratch/samrabin/tests_0627-161354de/As of 71f9995: New SystemTest:Moving to a different PR to keep this one focused.SUBSETDATAPOINT_Ld5_D_Mmpi-serial.CLM_USRDAT.I2000Clm60BgcCrujra.derecho_intel.clm-default. Completes successfully!