job.result() needs a refresh option

[ajavadia]

it seems like the Job class is caching its result. But it is easy to change the result during post-processing, for example marginalizing over some qubits or doing error mitigation on the result. I think this should not affect the original job result. At least, the job.result() call should have an option to fetch the original result from the API again.

[jyu00]

If a user wants to change the result object but keep the original, can't they just do a copy.deepcopy()?

[ajavadia]

Sure but it will take some time to figure out this is happening (based on my debugging experience). I don’t think it is expected that “job.result()” is *not* returning the result of the executed job every time you call it.

…

On Nov 25, 2019, at 11:55 AM, Jessie Yu ***@***.***> wrote: If a user wants to change the result object but keep the original, can't they just do a copy.deepcopy()? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[jyu00]

Closed via #469