fix(scripts): correct variable names and comments in split_grid_transient.py#21
Open
Hydrogenplus3 wants to merge 1 commit intouvahotspot:masterfrom
Open
Conversation
…ient.py - Rename 'grid_steady_file' to 'grid_transient_file' throughout - Update usage description to reflect transient file processing - Fix example filename reference from '.grid.steady' to '.grid.ttrace' - Update output filename pattern to use actual prefix These changes eliminate confusion between steady-state and transient processing workflows.
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
This PR addresses inconsistencies in split_grid_transient.py where comments and variable names appear to have been carried over from split_grid_steady.py without appropriate updates.
Changes Made:
The core functionality of original split_grid_transient.py file remains unaffected - the script executes correctly without behavioral changes. These modifications simply address documentation and naming issues that could confuse developers working with both steady-state and transient processing workflows.