-
Notifications
You must be signed in to change notification settings - Fork 56
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
ZNE in Catalyst blog post #604
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
LGTM!
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.
really nice blog post! Do you plan for this to go out on Oct 31st?
@@ -0,0 +1,44 @@ | |||
--- | |||
title: "Just in time for just-in-time error mitigation" |
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.
Minor comment, but as the title is quite important for SEO, could be good to give it a 'subtitle'. E.g.,
Just in time for just-in-time error mitigation: compiling error mitigation with LLVM, X, and Y.
Could sprinkle in important keywords as well like Mitiq, Catalyst, etc.
Did I tell you how much we learned? For the Unitary Fund team, this project was our first venture into the JIT world and the architectural stack that comes with implementing it. | ||
We had to ramp up on things like JAX and the MLIR framework (Multi-Level Intermediate Representation). Understanding MLIR gave us deeper insights into compiler design for quantum programs in general as well. I am not going to lie; it was all a bit daunting in the beginning, but it was incredibly rewarding! |
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.
Maybe something I am wondering while reading this paragraph, why MLIR/JAX? E.g., if I am not familiar with these technologies, does it bring anything to the table (or is it just another way of doing the same thing as other technologies as QASM?)
That's a provisional date. I plan for this to go out as soon as PennyLaneAI/qml#1207 is merged. |
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.
This reads very well and is both informative and engaging. Congratulations @cosenal on finding the right register and conveying the complexities involved as best as possible.
Some minor comments besides those in the text:
- Include a high quality version of the image, if available
- Next to subtitles as suggested by @josh146, also consider the use of chapter/section titles. I like how this blog post renders in terms of subtitle and section titles
- The second part of the blog post switches from to recount what's been done in the collaboration, starting from the paragraph "Even though Mitiq can be used with PennyLane programs, it doesn’t seamless integrate into the Catalyst...". I suggest limiting the past tense and emphasizing a bit more the result obtained as an outcome of the work in the collaboration. The section titles could help convey this better (first intro section / collab section / results section).
I totally agree, the blurry version is ugly. However, for doing this, I need the original version of the Catalyst diagram, which I couldn't find in the catalyst repo, e.g., https://github.com/PennyLaneAI/catalyst/tree/main/doc/_static/arch. @josh146 @dime10 may know where I can find it (I don't remember where I copied the blurry version from). |
Hi @cosenal, here is a higher quality version: |
Blog post presenting our contribution to the Catalyst project.