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
Is your feature request related to a problem? Please describe.
It would be nice if it was possible to do a possible checkpointing of an IBMQExperiment.
Describe the solution you'd like
The use case I'm imagining is that a notebook has generated an IBMQExperiment and submitted at least some of the jobs, but then the kernel dies. It should be able to save the state of the IBMQExperiment on each submit/poll for results. Even on notebook restart, it should be possible to interact with the existing jobs since we save the job ids.
The text was updated successfully, but these errors were encountered:
File ~\pyGSTi\pygsti\extras\ibmq\ibmqcore.py:384, in IBMQExperiment.write(self, dirname)
382 for atr in _attribute_to_pickle:
383 with open(dirname + '/ibmqexperiment/{}.pkl'.format(atr), 'wb') as f:
--> 384 _pickle.dump(self[atr], f)
Is your feature request related to a problem? Please describe.
It would be nice if it was possible to do a possible checkpointing of an IBMQExperiment.
Describe the solution you'd like
The use case I'm imagining is that a notebook has generated an IBMQExperiment and submitted at least some of the jobs, but then the kernel dies. It should be able to save the state of the IBMQExperiment on each submit/poll for results. Even on notebook restart, it should be possible to interact with the existing jobs since we save the job ids.
The text was updated successfully, but these errors were encountered: