Fix paco classifying and update paco code repo tag to v2.0.4 #1218
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
Paco tag v2.0.4 has two newer commits to main, which fixed the training algorithm, and the same requirement.txt as the previous v2.0.3.
dchiller
approved these changes
Oct 11, 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.
Paco tag v2.0.4 has two newer commits to main, which fixed the training algorithm, and the same requirement.txt as the previous v2.0.3.
Resolves: (#1209)
Our Rodan now should point to the latest Paco codes. All changes are captured in the tag v2.0.4 with the currently used, fixed dependencies, and the fix for the inference step in the classifying job. (Please refer to the issue for more details.)
Kyrie and I have tested the new docker images on our local machine and grid lines are no longer there with the same model.