-
Notifications
You must be signed in to change notification settings - Fork 159
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
chore: add run use case example to GH workflow #310
Conversation
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.
looks good I think, you'll be able to test it after merging it in main anyway since it's a new workflow
I already tested it in the link above. You can trigger a workflow by setting the on: push in a workflow file such that it runs even if not merged in main. |
2faa97f
to
8c0b84b
Compare
Looks fishy to me:
|
1339a20
to
d946b95
Compare
why was this closed @jfrery ? |
Not sure if this is useful. We never needed it. |
3f74619
to
5b77be9
Compare
d35ff40
to
b8433a9
Compare
38cd25e
to
33e1cc8
Compare
0dee236
to
5621f00
Compare
use_case_examples/cifar/cifar_brevitas_finetuning/cifar_utils.py
Outdated
Show resolved
Hide resolved
@@ -2,11 +2,14 @@ | |||
export LC_ALL=en_US.UTF-8 | |||
export LANG=en_US.UTF-8 | |||
|
|||
EXAMPLE_NAME=cifar_brevitas_finetuning | |||
EXAMPLE_NAME=cifar_brevitas_training |
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.
here and in the following makefiles, I believe the EXAMPLE_NAME
and JUPYTER_RUN
are useless as only TIME_NB
is used to run the notebooks/files
so I would remove them as it's a bit confusing why we have two jupyter nbconvert --to notebook --inplace --execute
occurences (here and in time_notebook_execution.sh
)
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.
Yes bad copy paste here thanks!
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.
I see that you kept EXAMPLE_NAME
here (and below), are these necessary ? I don't see how they are used !
also I can see some jupyter nbconvert --to notebook --inplace --execute
in some makefiles below, so I guess you're not finished !
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.
Nice catch. I am not using the folder name as example name to print logs. This can be remove. Let me clean the Makefile.
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.
thanks for cleaning up things ! I still see one remaining EXAMPLE_NAME
in this exact makefile, but the other ones look fine
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.
Indeed bad rebase. It's fixed
868efd9
to
7051a21
Compare
7051a21
to
d97152f
Compare
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.
looks great, thanks a lot !
Coverage passed ✅Coverage details
|
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.
Might be a dumb question but don't we also want to open a PR with the new run of the use-case or is this just for testing purposes? (cc @jfrery )
What is a PR with the new run? If you mean the updated notebooks, we add a discussion on this. |
Thanks for the link to the discussion, makes sense! |
echo "*** Processing example ${EXAMPLE_NAME}" | ||
else | ||
continue | ||
CURRENT_DIR=$(pwd) |
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.
Should we check somehow that the CURRENT_DIR is the root of the repo? or shouldn't we force CURRENT_DIR to the root of the repo?
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.
I am expecting the GH action to put me in the root of the repo. Not sure what path we should force it to. Depends on the GH action I suppose.
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.
$PATH_OF_SCRIPT / .. / ..
or something like that? Don't know how easy it is to get from bash. I'm fine with the current solution.
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.
Yes indeed we could use path from script. A bit annoying but maybe safer. I can add this quickly in another PR why not.
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.
Done -> #627 will merge this one first
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.
Looks good to me, nice to have a make file per use-case, is this something that should also be used by our users? 🤔
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.
Great work! thanks
closes https://github.com/zama-ai/concrete-ml-internal/issues/3458
closes https://github.com/zama-ai/concrete-ml-internal/issues/4315