codecov[bot]
commented
1 month ago Codecov Report
Attention: Patch coverage is 85.71429% with 2 lines in your changes missing coverage. Please review.
Project coverage is 97.90%. Comparing base (
eb25b44) to head (045db46).
| Files | Patch % | Lines |
|---|---|---|
| frontend/catalyst/jax_tracer.py | 0.00% | 0 Missing and 2 partials :warning: |
Additional details and impacted files
```diff @@ Coverage Diff @@ ## main #945 +/- ## ========================================== - Coverage 97.93% 97.90% -0.04% ========================================== Files 72 72 Lines 10333 10341 +8 Branches 1177 1180 +3 ========================================== + Hits 10120 10124 +4 - Misses 169 171 +2 - Partials 44 46 +2 ```:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Context: Verification so far checks that the observables are supported, but not that the measurement type is.
Description of the Change:
We add a check to
validate_observables, and change its name tovalidate_measurements, as it now more generally validates that both theMeasurementProcessand the observables on a measurement are valid.Adding this verification caused many tests fail with a
CompilationError, claiming the measurement is unsupported. This happened in two cases:StateMPmeasurements: There was a bug whereProgramFeaturesrecords any device from the new device API as being in finite-shot mode, even when no shots are passed. This caused theqjit_capabilities.measurement_processes(which the transform relies on) to be incorrect for the new device API andshots=None. This PR updates howProgramFeaturesare initialized to fix the bug.shots, using sample based measurements withoutshots, or mixing state and sample based measurements in a singleqnode). These tests have been updated.Related Shortcut Stories: [sc-69062]
Note: I haven't updated any TOML files. The OQC device and all the Lightning TOML files already include measurement processes. The CUDA TOML doesn't, but I'm not sure which MPs it supports, and it's not affected by these changes yet because it still uses the old device API.