PennyLaneAI
Differentiable classical shadows
Brief demo highlighting
- classical shadow theory
- new PennyLane implementations, i.e. differentiability
- compare quantum resources with standard methods
Right now the build has trouble importing classical_shadow from pennylane even though this is branched against dev - any idea what is going wrong here?
Update: This version is now somewhat complete in terms of its contents and the points I am trying to make. However, it is not really polished yet. Especially, the code for the two examples of measuring one single and all q-local observables is quite lengthy.
Generally I am not sure if it is worth making that case for all and one single observables explicitly, since the results are rather "obvious" (but it still feels right to demonstrate it). Something to consider moving forward.
It renders locally but there are some CI problems that need to be taken care of. Maybe @rashidnhm can help? It seems it is not pulling the latest master from pennylane which includes the new functionalities I am showcasing.
Update: This version is now somewhat complete in terms of its contents and the points I am trying to make. However, it is not really polished yet. Especially, the code for the two examples of measuring one single and all q-local observables is quite lengthy.
Generally I am not sure if it is worth making that case for all and one single observables explicitly, since the results are rather "obvious" (but it still feels right to demonstrate it). Something to consider moving forward.
It renders locally but there are some CI problems that need to be taken care of. Maybe @rashidnhm can help? It seems it is not pulling the latest master from pennylane which includes the new functionalities I am showcasing.
@Qottmann this pull-request might be another scenario where we may want to ignore the qml cache while building the demo. Since the update to pennylane is external it could be that the cached version of pennylane here does not have the updated function (this would depend on when that function was added and when this PR was opened). So I think first thing to try would be to ignore the cache and see if the error persists.
@Qottmann I've added the ignore-cache label, please push another commit to your branch to trigger the builds again.
Thank you for opening this pull request.
You can find the built site at this link.
Deployment Info:
- Pull Request ID:
557 - Deployment SHA:
e4aec0b461f18c8c530f4b38428cc651066fedec(TheDeployment SHArefers to the latest commit hash the docs were built from)
Note: It may take several minutes for updates to this pull request to be reflected on the deployed site.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
PR was closed automatically as the dev branch was recreated. Re-opened the PR and now it targets master.
If the demo does use any post-v0.26.0 features from PennyLane, the target branch should be changed again to dev.
Hey @Qottmann , you removed the changes in the .rst file. Your demo does not appear in any category now
Good catch, it was still in my browser's cache and it got lost with the big merge with the master branch 👍 Btw, @KetpuntoG do you have an idea for a better thumbnail?
On Monday I will continue with the review 😄 I've updated the thumbnail, let me know if you think it's okey FYI, the idea is to publish this demo 11 Oct 💪
In the end, as you said @Qottmann , it was found that updating the pyscf to 2.1.1 fixed the warning problem. There was only a demo in which it was being used and the update did not break anything. Thank you for the work carried out in these demos!!