-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Deprecate pulse module and related functionality for removal in 2.0 #13063
Comments
mtreinish
added a commit
to mtreinish/qiskit-core
that referenced
this issue
Aug 30, 2024
This commit removes benchmarks for the deprecated assemble module and the soon to be (see Qiskit#13063) deprecated pulse module. While these features are still supported it's not worth the spending the limited CPU time we hacve on the benchmarking system to track the performance of these components anymore.
I'd be happy to work on this. |
github-merge-queue bot
pushed a commit
that referenced
this issue
Sep 3, 2024
This commit removes benchmarks for the deprecated assemble module and the soon to be (see #13063) deprecated pulse module. While these features are still supported it's not worth the spending the limited CPU time we hacve on the benchmarking system to track the performance of these components anymore.
Will pulse related module become another independent package? |
sbrandhsn
pushed a commit
to sbrandhsn/qiskit
that referenced
this issue
Sep 5, 2024
This commit removes benchmarks for the deprecated assemble module and the soon to be (see Qiskit#13063) deprecated pulse module. While these features are still supported it's not worth the spending the limited CPU time we hacve on the benchmarking system to track the performance of these components anymore.
Hi @Zonaldo7, the Pulse module will be part of Qiskit Dynamics once removed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What should we add?
It's been decided that moving into Qiskit 2.0 we'll be removing the pulse module and all the related functionality (such as the schedule function along with it's backing module and calibrations in the target) as it's not in scope for the direction of the project anymore. We should ensure that we mark all these features as deprecated in 1.3.0 so there is sufficient warning prior to the release of Qiskit 2.0. These features will continue to be supported in Qiskit through the EoL with the 1.x.y release series into the 2H of 2025.
The text was updated successfully, but these errors were encountered: