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
It would be nice to document how users who don't have access to the cloud database can load old experiments.
I think this can be done roughly as:
fromqiskit_experiments.frameworkimportExperimentData# Somehow the user must retain and run the same code that created the experiment originallyexperiment=Experiment(**opts)
# Somehow the user must retain and provide the list of job IDsdata=ExperimentData(job_ids=job_ids)
experiment.analysis.run(data)
data.block_for_results()
I think that should retrieve the raw data from the IBM Quantum service and run the same analysis on it again. I am not sure if there are some caveats that need to be added on cases where some information could be missing here.
Perhaps documentation for this could fill in the "somehow"s above -- maybe BaseExperiment.config() and BaseExperiment.from_config() could be used to save and restore the experiment from a file instead of re-running the original experiment code. Also, the qiskit-ibm-experiment package provides a local option for IBMExperimentService (see here). This local option is provided primarily for testing (it is not very scalable), but perhaps it would (or could) provide a better option for a user to save and reload a handful of experiments rather than storing job IDs by hand.
I think we should 'promote' the option to save experiments locally to be easy to use, and handle all the required nitty-gritty, such as job-ids handling as Will mentioned. Currently the option is hidden and requires code tweaking to use. Enabling some like this:
It would be nice to document how users who don't have access to the cloud database can load old experiments.
I think this can be done roughly as:
I think that should retrieve the raw data from the IBM Quantum service and run the same analysis on it again. I am not sure if there are some caveats that need to be added on cases where some information could be missing here.
Perhaps documentation for this could fill in the "somehow"s above -- maybe
BaseExperiment.config()
andBaseExperiment.from_config()
could be used to save and restore the experiment from a file instead of re-running the original experiment code. Also, theqiskit-ibm-experiment
package provides a local option forIBMExperimentService
(see here). This local option is provided primarily for testing (it is not very scalable), but perhaps it would (or could) provide a better option for a user to save and reload a handful of experiments rather than storing job IDs by hand.This topic came up in this Slack discussion.
The text was updated successfully, but these errors were encountered: