-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workflow for lidar-prod threshold optimization preparation #117
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
leavauchier
force-pushed
the
workflow-lidarprod-optim
branch
from
April 18, 2024 14:56
b35bddb
to
76f5094
Compare
leavauchier
force-pushed
the
workflow-lidarprod-optim
branch
from
April 18, 2024 15:06
76f5094
to
fceb59c
Compare
leavauchier
force-pushed
the
workflow-lidarprod-optim
branch
20 times, most recently
from
April 25, 2024 07:53
e4d1ae1
to
5d1bc84
Compare
leavauchier
force-pushed
the
workflow-lidarprod-optim
branch
3 times, most recently
from
April 25, 2024 11:33
194e7e1
to
0314c70
Compare
CharlesGaydon
requested changes
Apr 25, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Quelques corrections et typos mais globalement c'est top :)
leavauchier
changed the title
Workflow lidarprod optim
Workflow for lidar-prod threshold optimization preparation
Apr 25, 2024
leavauchier
force-pushed
the
workflow-lidarprod-optim
branch
3 times, most recently
from
May 2, 2024 07:43
2e63e8c
to
08e52cf
Compare
leavauchier
force-pushed
the
workflow-lidarprod-optim
branch
6 times, most recently
from
May 2, 2024 09:44
3f6c9c8
to
b48590b
Compare
leavauchier
force-pushed
the
workflow-lidarprod-optim
branch
from
May 2, 2024 11:38
b48590b
to
88deda5
Compare
CharlesGaydon
approved these changes
May 6, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍🏻 !
LGTM :)
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.
Ajout d'un workflow pour faire tourner une inférence sur le jeu de données permettant d'optimiser les seuils du module de validation de bâtiments de lidar-prod.
Le lancement se fait depuis github (il faut avoir un compte autorisé)
Dans l'onglet "Actions"
choisir "Prediction on lidar-prod optimization dataset" dans la toolbar de gauche :
puis "run workflow" à droite
et entrer les valeurs des paramètres demandés :