Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

compute_energy_used vs spin2 #1167

Closed
Christian-B opened this issue Mar 13, 2024 · 1 comment
Closed

compute_energy_used vs spin2 #1167

Christian-B opened this issue Mar 13, 2024 · 1 comment
Milestone

Comments

@Christian-B
Copy link
Member

compute_energy_used has a lot of hard coded spin1 values.

Until these values are available for spin2 we should disable cfg "write_energy_report"
And leave this issue Open.

Once we have the costs we can consider updating compute_energy_used and likely the ChipPowerMonitor vertex and aplx

@Christian-B Christian-B added this to the Bluesky milestone Apr 30, 2024
@Christian-B
Copy link
Member Author

Fixed in previous pr which has changed all values to Version calls.

The version_spin2.py currently raise NotImplementedError so no need to disable the report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant