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

fix: avoid executing pytket-cutensornet notebooks #8

Merged
merged 3 commits into from
Oct 25, 2024
Merged

Conversation

CalMacCQ
Copy link
Collaborator

@CalMacCQ CalMacCQ commented Oct 24, 2024

Add a bit of a file path hack to avoid executing the pytket-cutensornet example notebooks -> CQCL/pytket-cutensornet#172

We don't have GPUs set up in the repo that builds the website (not sure its worth adding)

However we still want to continue execute all the other code examples

@CalMacCQ CalMacCQ changed the title fix: slight file path hack to avoid executing pytket-cutensornet notebooks fix: avoid executing pytket-cutensornet notebooks Oct 24, 2024
@CalMacCQ CalMacCQ merged commit 45cc4e4 into main Oct 25, 2024
@CalMacCQ CalMacCQ deleted the CalMacCQ-patch-1 branch October 25, 2024 10:05
CalMacCQ added a commit to CQCL/pytket-cutensornet that referenced this pull request Oct 25, 2024
# Description

Adding the notebook examples into the docs html pages. The coversion to
html is done by the MyST-NB library. I'm avoiding execution for now. To
show the cell outputs would require setting up GPUs in C.I. in the
repository that builds the website or somehow executing them in this
repository and just deploying the html from the website repository.

<img width="1053" alt="Screenshot 2024-10-25 at 13 07 07"
src="https://github.com/user-attachments/assets/8e6a9e64-5581-4fba-be85-026b5fec58e0">


remaining TODOs

- [x] validate file path hack to avoid executing notebooks (working
locally) -> CQCL/pytket-docs-theming#8
- [ ] fix C.I. failures (fixed check-examples, just need the nix c.i.
fixed.)

# Related issues

closes #154 

# Checklist

- [ ] I have performed a self-review of my code.
- [ ] I have commented hard-to-understand parts of my code.
- [ ] I have made corresponding changes to the public API documentation.
- [ ] I have added tests that prove my fix is effective or that my
feature works.
- [ ] I have updated the changelog with any user-facing changes.

---------

Co-authored-by: PabloAndresCQ <[email protected]>
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.

1 participant