Helena Zhang

I see your point, though former Ignis users are probably looking for a replacement, so it would be helpful to direct people to experiments, whether in the links or a...

@nitin-pandita Thanks for opening the PR—can you sign the CLA?

As discussed in the meeting, it would be good to have the same type of abstract class for interfacing with the provider so we don't directly edit `ExperimentData` when provider...

Thanks for the interface patterns @ItamarGoldman. I agree it's good to have the option to load either the experiment or experiment data or both, since these operations could be slow...

@wshanks discussed in the meeting today that we should support the use case of not running the analysis when running an experiment and then saving experiment config in a dummy...

The user wants to save a long experiment without waiting for it to complete and then load it and run the analysis later, so the `block_for_results()` fix won't work for...

@nayan2167 Great! If you're on the [Qiskit Slack](https://qisk.it/join-slack), I can add you to the experiments-dev channel where we discuss development on Qiskit Experiments.

This is a good start, thanks @nayan2167. A few comments: - It looks like you've defined `circuits_per_job` as the total number of circuits in the experiment, so this variable isn't...

The current behavior is that jobs will only be loaded if a provider is given, like `load_expdata = ExperimentData.load(expdata.experiment_id, service, provider)`, but this is confusing. We already recommend in the...