You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The simulation of pulse schedules are much slower with DynamicsBackend.run method than with Solver.solve method when the simulation is done with Jax. It was mentioned in this thread that this might be related to the location of the conversion process of the schedules towards waveforms.
It would be nice to be able to have alternative ways of reducing dramatically the simulation times with the DynamicsBackend for a batch of circuits. A comparison of runtimes is attached through a notebook. jittable_sims_runtime.ipynb.zip
The text was updated successfully, but these errors were encountered:
What is the expected behavior?
The simulation of pulse schedules are much slower with
DynamicsBackend.run
method than withSolver.solve
method when the simulation is done with Jax. It was mentioned in this thread that this might be related to the location of the conversion process of the schedules towards waveforms.It would be nice to be able to have alternative ways of reducing dramatically the simulation times with the
DynamicsBackend
for a batch of circuits. A comparison of runtimes is attached through a notebook.jittable_sims_runtime.ipynb.zip
The text was updated successfully, but these errors were encountered: