search

cda-tum / mqt-bench

MQT Bench - A MQT Tool for Benchmarking Quantum Software Tools
https://www.cda.cit.tum.de/mqtbench/
MIT License
72 stars 16 forks source link

Update device calibration #310

Closed flowerthrower closed 3 months ago

flowerthrower commented 6 months ago

Update gate time values to SI units (seconds) and current available calibration data. This is especially relevant in the light of the new MQTPredictor reward function expected_success_probability.

codecov[bot] commented 6 months ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.9%. Comparing base (a552522) to head (7bce49f). Report is 61 commits behind head on main.

Additional details and impacted files ```diff @@ Coverage Diff @@ ## main #310 +/- ## ======================================= - Coverage 93.0% 92.9% -0.1% ======================================= Files 47 47 Lines 2422 2422 ======================================= - Hits 2253 2252 -1 - Misses 169 170 +1 ``` | [Flag](https://app.codecov.io/gh/cda-tum/mqt-bench/pull/310/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=cda-tum) | Coverage Δ | | |---|---|---| | [python](https://app.codecov.io/gh/cda-tum/mqt-bench/pull/310/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=cda-tum) | `92.9% <100.0%> (-0.1%)` | :arrow_down: | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=cda-tum#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

flowerthrower commented 5 months ago

I have updated the calibration data to the values specified online (e.g. AWS). This data comes in various units and is all transformed into SI units when imported using the respective import_backend methods.

flowerthrower commented 3 months ago

IBM, OQC (and IQM) calibration data is not supplied in seconds (hence transformation during import) IONQ, Rigetti calibration data is already specified in seconds Quantinuum - no information on timescales