Skip to content
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: use cp vl when circuit is CRT based #619

Merged
merged 3 commits into from
Apr 17, 2024
Merged

Conversation

jfrery
Copy link
Collaborator

@jfrery jfrery commented Apr 17, 2024

@cla-bot cla-bot bot added the cla-signed label Apr 17, 2024
@jfrery jfrery force-pushed the chore/use_cp_vl_when_crt branch from f6c845e to 5688e3b Compare April 17, 2024 09:52
Copy link
Collaborator

@andrei-stoian-zama andrei-stoian-zama left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just a minor doubt on whether the compiled model will always be compilable and CRT with n_bits=4. But otherwise great!


# If the old simulation method should be used
if USE_OLD_VL:
# Whether the old simulation method should be used based on USE_OLD_VL
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would rephrase this with :

# If the virtual library method should be used 
# For now, use the virtual library when simulating circuits that uses CRT 
# decomposition because the official simulation is too slow 
# FIXME: https://github.com/zama-ai/concrete-ml-internal/issues/4391

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't like this # If the virtual library method should be used . Feels like something else is coming to complete the sentence.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as you wish, not sure what would come next though. it's just that we use this formulation in most of our docstrings . We do also use whether but it usually needs to be followed by or not afterwards, which I always find a bit redundant

Copy link
Collaborator Author

@jfrery jfrery Apr 17, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But it's a bit weird to have:

# If the virtual library method should be used 
if USE_OLD_VL:

no? I would expect:

# If USE_OLD_VL is True, use the virtual library
if USE_OLD_VL:

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Anyway back to the original comment with some of your suggestion.

Copy link
Collaborator

@RomanBredehoft RomanBredehoft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for this update, I would just make some things a bit more clear !

@andrei-stoian-zama
Copy link
Collaborator

This also closes https://github.com/zama-ai/concrete-ml-internal/issues/4391 right ?

Copy link
Collaborator

@RomanBredehoft RomanBredehoft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

great thanks !

Copy link

Coverage passed ✅

Coverage details

---------- coverage: platform linux, python 3.8.18-final-0 -----------
Name    Stmts   Miss  Cover   Missing
-------------------------------------
TOTAL    7548      0   100%

59 files skipped due to complete coverage.

@jfrery jfrery marked this pull request as ready for review April 17, 2024 15:49
@jfrery jfrery requested a review from a team as a code owner April 17, 2024 15:49
@jfrery jfrery merged commit cf6f224 into main Apr 17, 2024
11 checks passed
@jfrery jfrery deleted the chore/use_cp_vl_when_crt branch April 17, 2024 15:50
@RomanBredehoft
Copy link
Collaborator

RomanBredehoft commented Apr 18, 2024

no @andrei-stoian-zama because the issue you link is used as a fixme, until this is somehow fixed by concrete

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants