Add additional CLM3.5 option --CLM3.5 in build-script
#111
Conversation
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
s-poll
approved these changes
Nov 25, 2025
Member
s-poll
left a comment
s-poll
left a comment
There was a problem hiding this comment.
PR is fine with me. I did one small suggestion.
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.
Multiple times the difference between
--CLM35and the model directory being calledCLM3.5has caused disruption / errors.Therefore, I suggest adding the option
--CLM3.5for invoking CLM3.5.Latest appearance of this issue, while checking out #109 (script is not renaming the build directory appropriately).
I tested it on JUWELS, where it works as expected. Only possible problem I see is that the
.in--CLM3.5can cause problems / is highly unusual.