Fixed clone bug in ctm_setup #53
Merged
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
mmanyin
added
the
0 diff
|
Tagging this "zero diff" since the model itself has not changed, only the post-processing for cloned experiments |
mathomp4
approved these changes
Dec 22, 2024
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.
The standard cloning process was not properly editing ctm_post.j
and therefore the old EXPDIR string was not being changed to the new EXPDIR string.
This was due to the non-standard form of that file.
Two fixes are now included: ctm_post.j has a new format which will now work with the standard cloning process,
and that process (in ctm_setup) has been modified to account for ctm_post.j in the old format.