Skip to content

Conversation

@pavoljuhas
Copy link
Collaborator

Convenience function for constructing GoogleNoiseProperties from available
specifications for known QVM devices.

Related to b/395705720

Convenience function for constructing GoogleNoiseProperties from available
specifications for known QVM device.

Related to b/395705720
@pavoljuhas pavoljuhas requested review from a team, verult, vtomole and wcourtney as code owners May 22, 2025 21:24
@github-actions github-actions bot added the size: S 10< lines changed <50 label May 22, 2025
@codecov
Copy link

codecov bot commented May 22, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.68%. Comparing base (513f309) to head (7f72c5c).
Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7369   +/-   ##
=======================================
  Coverage   98.68%   98.68%           
=======================================
  Files        1112     1112           
  Lines       97588    97601   +13     
=======================================
+ Hits        96307    96320   +13     
  Misses       1281     1281           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Collaborator

@eliottrosenberg eliottrosenberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, @pavoljuhas!

the Z phases data, if available, to construct NoiseProperties for device simulation.
Args:
processor_id: name of the processor to simulate.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we either specify valid processor names or tell where to find them?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, there seems to be no public API to get those names apart from reading the code. I will add a list_virtual_processors function in next PR.

@pavoljuhas pavoljuhas added this pull request to the merge queue May 24, 2025
Merged via the queue into quantumlib:main with commit 318887b May 24, 2025
35 checks passed
@pavoljuhas pavoljuhas deleted the qvm-noise-properties-factory branch May 24, 2025 01:02
pavoljuhas added a commit to pavoljuhas/Cirq that referenced this pull request May 27, 2025
Convenience function to get the valid `processor_id` strings for QVM factories.

Follow-up to quantumlib#7369
github-merge-queue bot pushed a commit that referenced this pull request May 27, 2025
Convenience function to get the valid `processor_id` strings for QVM
factories.

Follow-up to #7369
BichengYing pushed a commit to BichengYing/Cirq that referenced this pull request Jun 20, 2025
Convenience function for constructing GoogleNoiseProperties from
available
specifications for known QVM devices.

Related to b/395705720
BichengYing pushed a commit to BichengYing/Cirq that referenced this pull request Jun 20, 2025
…#7375)

Convenience function to get the valid `processor_id` strings for QVM
factories.

Follow-up to quantumlib#7369
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size: S 10< lines changed <50

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants