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

Don't do strict validation for phirmodel, update angle and duration generation #16

Merged
merged 5 commits into from
Oct 23, 2023

Conversation

qartik
Copy link
Member

@qartik qartik commented Oct 23, 2023

To avoid breakage after merge of CQCL/phir#8.

@qartik qartik self-assigned this Oct 23, 2023

Cost: TypeAlias = float
Layer: TypeAlias = list[Shard]
Ordering: TypeAlias = list[int]
Copy link
Member Author

@qartik qartik Oct 23, 2023

Choose a reason for hiding this comment

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

Unsure if this file is the best place to place these alias definitions. I chose this as both phirgen and place_and_route already import it.

Happy to take suggestions. One option is to create a new module with all type declarations.

@@ -12,7 +12,7 @@ requires-python = ">=3.10"
license = {file = "LICENSE"}
authors = [{name = "Quantinuum"}]

dependencies = ["pytket"]
dependencies = ["phir>=0.1.5", "pytket"]
Copy link
Contributor

Choose a reason for hiding this comment

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

Only question here is should the version be pinned to exactly what's in requirements.txt? To prevent any possibility of drift.

Copy link
Member Author

Choose a reason for hiding this comment

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

I think, we should be more flexible in pyproject.toml. The pinned version is for reproducible builds, dev environments, etc.

The phir project can add more types/fields, but that may not necessarily require changes to our phir generation.

@qartik qartik merged commit 33adde6 into main Oct 23, 2023
1 check passed
@qartik qartik deleted the no-strict-validation branch October 23, 2023 21:50
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