mgym upload: Quantum Fourier Transform on ibm/ibm_marrakesh#355
Conversation
vprusso
added
the
source:metriq-gym
There was a problem hiding this comment.
Pull request overview
Adds a new Metriq Gym results artifact for the “Quantum Fourier Transform” benchmark run on IBM ibm_marrakesh.
Changes:
- Introduces a new JSON results file capturing benchmark metrics, platform metadata, and run parameters.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "value": 0.0030000000000000005, | ||
| "uncertainty": 0.001 | ||
| }, | ||
| "score": { | ||
| "value": 0.0030000000000000005, |
There was a problem hiding this comment.
The value fields contain excessive floating-point precision (0.0030000000000000005), which makes the dataset harder to read and can introduce noisy diffs. Consider normalizing/rounding numeric serialization (e.g., 0.003) at write-time so stored artifacts use stable, human-friendly precision.
| "value": 0.0030000000000000005, | |
| "uncertainty": 0.001 | |
| }, | |
| "score": { | |
| "value": 0.0030000000000000005, | |
| "value": 0.003, | |
| "uncertainty": 0.001 | |
| }, | |
| "score": { | |
| "value": 0.003, |
| "value": 0.0030000000000000005, | ||
| "uncertainty": 0.001 | ||
| }, | ||
| "score": { | ||
| "value": 0.0030000000000000005, |
There was a problem hiding this comment.
The value fields contain excessive floating-point precision (0.0030000000000000005), which makes the dataset harder to read and can introduce noisy diffs. Consider normalizing/rounding numeric serialization (e.g., 0.003) at write-time so stored artifacts use stable, human-friendly precision.
| "value": 0.0030000000000000005, | |
| "uncertainty": 0.001 | |
| }, | |
| "score": { | |
| "value": 0.0030000000000000005, | |
| "value": 0.003, | |
| "uncertainty": 0.001 | |
| }, | |
| "score": { | |
| "value": 0.003, |
No description provided.