-
Notifications
You must be signed in to change notification settings - Fork 2
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
Code cleanup + Bugfix #63
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.
A few minor questions but otherwise looks good!
src/qca/utils/algo_utils.py
Outdated
algo_name='GSEE', | ||
fname=circuit_name, | ||
is_extrapolated=is_extrapolated, | ||
numsteps=nsteps, |
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 choose a default naming scheme for all functions and standardize that? as far as I'm aware, we have numsteps, total_steps, and nsteps and potentially others.
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.
nsteps is used the most so ill proceed with that one
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.
Other than the comments George and I have, it looks good. I think we just need to add many test cases to make sure handling new functions and some old that were not tested before. Maybe we should start log warnings for when inputs are invalid or unexpected behaviors occurs.
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.
Test cases for scale_resource looks good to me, thanks!
This PR is focused on cleaning up some of the code, specifically, the interfaces for generating resource estimates. Additionally, this PR is focused on fixing up some bugs w/ respect to GSEE that was uncovered after PR #61 was merged in. The bugs just broke the handshake between circuit generation + resource estimation so that was handled as well.