Containerized Joint Optimization#41
Draft
T-Burton-ND wants to merge 14 commits into
Draft
Conversation
Collaborator
Author
|
New design thrust: limiting new container to just the model usage so that a new container doesnt have to be rebuilt everytime there is an unrelated code change. Additionally, batching model usage to limit the number of times a container is needed. |
Collaborator
Author
|
Well that wasnt my worst idea ever, but it was up there. Adding xtb and pysis back into the container becuase...we need them... |
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
1 participant
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.
Attempt to move Joint Optimization workflow fully into containers to wrap numpy and sk-learn versioning independent of main yarp code.