Add a field for a list of GPU models, and update versions to v10 - #27
Merged
Conversation
5 tasks
slr71
approved these changes
Feb 18, 2026
| - This module is versioned as v9 in the module path. If releasing a new major version, update module path and coordinate with downstream consumers. | ||
|
|
||
| ## Where to look next / follow-ups | ||
| - If you need runtime examples of how these models are consumed, search in the `cyverse-de` organization for imports of `github.com/cyverse-de/model/v9`. |
Member
Author
|
Cool, thanks for the review. I'll get it merged in so it's easier for me to start using it! |
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.
(v10 won't exist until merging, but made sense to update it now, I thought)
Basically just plumbing. Jobs that want to limit the acceptable models provide a list, ones that don't care provide an empty list or null.