Conversation
|
One or more of the following people are relevant to this code:
|
There was a problem hiding this comment.
The first h2 starts with "Addons for" and the rest of the h2s don't follow that pattern. Style guide has us avoid gerunds in headers, so I would recommend a structure like this:
- Addons to map domain problems
- Addons to optimize circuits for hardware execution
- Addons to manage noise for expectation value estimation
- Addons to manage noise for sampling results
- Supplemental addons
Alternative: just remove the "Addons to" altogether, if it feels too repetitive... and go with:
- Map domain problems
- Optimize circuits for hardware execution
- Manage noise for expectation value estimation
etc.
There was a problem hiding this comment.
I like the alternative option (removing addons from those headers)
|
|
||
|
|
||
| ## Addons for mapping domain problems | ||
| These addons are particularly useful for preparing efficient quantum circuits based on the application you are building for. |
There was a problem hiding this comment.
| These addons are particularly useful for preparing efficient quantum circuits based on the application you are building for. | |
| These addons are particularly useful for preparing efficient quantum circuits based on the application you are building. |
"based on the application" - Maybe this can be clearer - are the circuits based on the application, or are the addons based on the application?
|
|
||
|
|
||
| ## Optimizing circuits for hardware execution | ||
| The following addons are useful for reducing circuit depth, both generally (for the circuit cutting addon) and when your workload estimates the expectation value of an observable using operator backpropagation. |
There was a problem hiding this comment.
The phrase "addons are useful for" is repeated in each section. It's more concise to use language like
"Use the following addons to reduce circuit depth, both generally..." (and I think it will feel less obviously repetitive, even if you use it in every section).
Or - mix it up with language like "These addons excel at...." "The purpose of these addons is..." "These addons specialize in..." etc.
There was a problem hiding this comment.
Good suggestion (I would perhaps replace addons with capabilities). I like both "Use these capabilities to ..." and "These capabilities specialize in..."
| </CardGroup> | ||
|
|
||
| ## Noise management for expectation value estimation | ||
| These addons are useful for managing noise when building quantum workloads which estimate expectation values of one or more observables. |
There was a problem hiding this comment.
| These addons are useful for managing noise when building quantum workloads which estimate expectation values of one or more observables. | |
| These addons are useful for managing noise when building quantum workloads that estimate expectation values of one or more observables. |
There was a problem hiding this comment.
I think we could be more concise and just say "expectation values of observables"
There was a problem hiding this comment.
I like the alternative option (removing addons from those headers)
| @@ -9,6 +9,9 @@ description: Understand the Qiskit addon tools, which help you build utility-gra | |||
|
|
|||
| Qiskit addons are a collection of research capabilities for enabling algorithm discovery at the utility scale. These modular software components can plug into a [workflow](/docs/guides/intro-to-patterns) to scale or design new quantum algorithms. Many of these addons are powered by the `qiskit-addon-utils` package. See the [Qiskit addon utilities documentation](https://qiskit.github.io/qiskit-addon-utils/) for more information. | |||
There was a problem hiding this comment.
Let's remove the last two sentences on the utils package since we now have a dedicated section for it.
There was a problem hiding this comment.
Let's move the optimization mapper to the top of the list. And add the qiskit-fermions package next to it. Suggested description for the latter: "Map fermionic problems to qubit operators and circuits."
| </CardGroup> | ||
|
|
||
| ## Noise management for expectation value estimation | ||
| These addons are useful for managing noise when building quantum workloads which estimate expectation values of one or more observables. |
There was a problem hiding this comment.
I think we could be more concise and just say "expectation values of observables"
| /> | ||
| </CardGroup> | ||
|
|
||
| ## Supplemental addons |
There was a problem hiding this comment.
I like where you're going with this. What about
| ## Supplemental addons | |
| ## Supplemental capabilities |
or
| ## Supplemental addons | |
| ## Supporting capabilities |
There was a problem hiding this comment.
I think I prefer "supporting capabilities" the most here
|
|
||
|
|
||
| ## Optimizing circuits for hardware execution | ||
| The following addons are useful for reducing circuit depth, both generally (for the circuit cutting addon) and when your workload estimates the expectation value of an observable using operator backpropagation. |
There was a problem hiding this comment.
Good suggestion (I would perhaps replace addons with capabilities). I like both "Use these capabilities to ..." and "These capabilities specialize in..."
jenglick
left a comment
There was a problem hiding this comment.
A few more quick comments!
| </CardGroup> | ||
|
|
||
| ## Noise management for sampling results | ||
| These addons are useful for managing noise when building sample-based quantum workloads. |
There was a problem hiding this comment.
I want to add a card here for the postselection capabilities in addon-utils. Even though we call out the addon-utils package later on, I think it's worth highlighting the postselection tools for mitigation
| </CardGroup> | ||
|
|
||
| ## Noise management for sampling results | ||
| These addons are useful for managing noise when building sample-based quantum workloads. |
There was a problem hiding this comment.
Let's remove the dice-eigensolver card and organize the tiles in this section in this order:
first row: sqd, sqd-hpc
second row: postselection, mthree
Co-authored-by: abbycross <across@us.ibm.com> Co-authored-by: Jen Glick <41485571+jenglick@users.noreply.github.com>
|
Thanks for the edits @jenglick! Just finished going through them and implementing the changes. Let me know if there's anything else we should change. |
| These capabilities specialize in mapping domain problems into quantum operators and circuits for execution on a quantum computer. | ||
| <CardGroup> | ||
| <Card | ||
| title="Optimization Mapper" |
There was a problem hiding this comment.
| title="Optimization Mapper" | |
| title="Optimization mapper" |
Whoops, I thought this one's official name was capital-M Mapper, but I just now checked and it's not. (AQC-Tensor is officially capital-T Tensor... I mixed them up)
jenglick
left a comment
There was a problem hiding this comment.
A few more quick comments
| </CardGroup> | ||
|
|
||
| ## Manage noise for sampling results | ||
| Manage noise when sampling results with the following addons. |
There was a problem hiding this comment.
| Manage noise when sampling results with the following addons. | |
| These techniques are useful for managing noise on sampling results. |
| </CardGroup> | ||
|
|
||
| ## Supplemental addons | ||
| This set of functions can be used to support and compose your workflows that leverage other addons. |
There was a problem hiding this comment.
| This set of functions can be used to support and compose your workflows that leverage other addons. | |
| Use these capabilities to support and compose your workflows that leverage other addons. |
| # Advanced techniques - Qiskit addons | ||
|
|
||
| Qiskit addons are a collection of research capabilities for enabling algorithm discovery at the utility scale. These modular software components can plug into a [workflow](/docs/guides/intro-to-patterns) to scale or design new quantum algorithms. Many of these addons are powered by the `qiskit-addon-utils` package. See the [Qiskit addon utilities documentation](https://qiskit.github.io/qiskit-addon-utils/) for more information. | ||
| Qiskit addons are a collection of research capabilities for enabling algorithm discovery at the utility scale. These modular software components build upon Qiskit’s performant foundation and can plug into a [workflow](/docs/guides/intro-to-patterns) to scale or design new quantum algorithms. |
There was a problem hiding this comment.
I think it would be helpful to add a final sentence here that says what this page does. Something like this
| Qiskit addons are a collection of research capabilities for enabling algorithm discovery at the utility scale. These modular software components build upon Qiskit’s performant foundation and can plug into a [workflow](/docs/guides/intro-to-patterns) to scale or design new quantum algorithms. | |
| Qiskit addons are a collection of research capabilities for enabling algorithm discovery at the utility scale. These modular software components build upon Qiskit’s performant foundation and can plug into a [workflow](/docs/guides/intro-to-patterns) to scale or design new quantum algorithms. This page highlights the available tools across key functional categories to help you choose relevant capabilities when building your workflows. |
Closes #4919