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

feat: add sevennet support to mlp recipes #2553

Merged

Conversation

mamunm
Copy link
Contributor

@mamunm mamunm commented Nov 30, 2024

Summary of Changes

Added sevennet to the MLP recipes based on issue #2429.

Key changes include:

  1. Added sevennet implementation to mlp recipes
  2. Created unit tests to validate sevennet functionality
  3. Ensured compatibility with existing MLP workflows

Requirements

-[X] My PR is focused on a single feature addition [#2429 ].
-[X] My PR has relevant, comprehensive unit tests.
-[X] My PR is on a custom branch (feature/sevennetMLP).

@buildbot-princeton
Copy link
Collaborator

Can one of the admins verify this patch?

Copy link

codecov bot commented Nov 30, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.32%. Comparing base (4696bd8) to head (d633621).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2553   +/-   ##
=======================================
  Coverage   97.32%   97.32%           
=======================================
  Files          85       85           
  Lines        3550     3554    +4     
=======================================
+ Hits         3455     3459    +4     
  Misses         95       95           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@Andrew-S-Rosen Andrew-S-Rosen left a comment

Choose a reason for hiding this comment

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

@mamunm: Thank you very much for your PR! I have just two questions before I can merge this.

Comment on lines 72 to 73
if "model" not in kwargs:
kwargs["model"] = "7net-0"
Copy link
Member

Choose a reason for hiding this comment

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

7net-0 is the default model, so it seems like we should probably not specify this.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I added both the default settings so the user knows what model and devices are being used if they want to dig deeper. But it's redundant, and I'll remove them in the next push.

Copy link
Member

@Andrew-S-Rosen Andrew-S-Rosen Dec 1, 2024

Choose a reason for hiding this comment

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

The default setting is "auto" for device I believe, but in any case let's remove them so we are always consistent with the underlying calculator. If there are changes to the model, it should (ideally) break the tests here.

Comment on lines 74 to 75
if "device" not in kwargs:
kwargs["device"] = "cpu"
Copy link
Member

Choose a reason for hiding this comment

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

The default device is "auto". Is there a reason to override this default by forcing CPU?

@Andrew-S-Rosen
Copy link
Member

Thanks, merging!

@Andrew-S-Rosen Andrew-S-Rosen merged commit e61f75d into Quantum-Accelerators:main Dec 1, 2024
20 checks passed
@mamunm
Copy link
Contributor Author

mamunm commented Dec 1, 2024

Thanks, merging!

Thanks for the review!

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

Successfully merging this pull request may close these issues.

3 participants