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

Code cleanup + Bugfix #63

Merged
merged 5 commits into from
Dec 13, 2024
Merged

Code cleanup + Bugfix #63

merged 5 commits into from
Dec 13, 2024

Conversation

JonhasSC
Copy link
Collaborator

@JonhasSC JonhasSC commented Dec 4, 2024

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.

Copy link
Collaborator

@gsgrattan gsgrattan left a 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/utils.py Show resolved Hide resolved
algo_name='GSEE',
fname=circuit_name,
is_extrapolated=is_extrapolated,
numsteps=nsteps,
Copy link
Collaborator

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.

Copy link
Collaborator Author

@JonhasSC JonhasSC Dec 12, 2024

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

Copy link
Collaborator

@zain2864 zain2864 left a 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.

src/qca/utils/utils.py Show resolved Hide resolved
src/qca/utils/utils.py Show resolved Hide resolved
src/qca/utils/utils.py Outdated Show resolved Hide resolved
Copy link
Collaborator

@zain2864 zain2864 left a 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!

@JonhasSC JonhasSC merged commit 73d254e into dev Dec 13, 2024
2 of 4 checks passed
@JonhasSC JonhasSC deleted the enhancements/code_cleanup branch December 18, 2024 05:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants