Closed nathanshammah closed 2 weeks ago
Should we include information about the QED-C integration here in this README? It seems a bit out-of-place I think. While, sure, the client is used as part of the QED-C pipeline, the pipeline itself (I would think) should be completely obscured from any content here to make it agnostic toward any specific applications. Thoughts @WrathfulSpatula @nathanshammah ?
You can assign this to me!
@QuantumAli Thank you! Vincent has been working on a pipeline to take the QED-C benchmark notebooks linked in the comment above, add a command-line interface for running the benchmarks on cloud provider quantum hardware automatically, and immediately piping the results into the Metriq REST API back end.
Vincent's new results are here: https://metriq.info/Submission/554
Please take a look at the diff and fork of the QED-C repository above, modified by Vincent for Metriq, as well as his new benchmark results at the Metriq submission above, and please write a summary of the new functionality as pertains to the Metriq client, (i.e.: people can automatically run and upload quantum cloud hardware benchmarks via the QED-C repository and the `metriq-client).
@QuantumAli if I can help in providing any additional context on usage or specifics on this diff, please let me know!
Just a follow-up on this to see if @QuantumAli is still working on this one. If not, you can assign me. Don't want to infringe if there is progress being made though!
Apologies, I have been purely focused on the Quantum Wednesday - you are more than welcome to take it on. Thank you for working with me on this
Update readme also to include information about the QED-c integration with metriq-api.