-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A proper way to combine the result object #1470
Comments
can this exist in aqua until we have a mega job that combines them? |
I do not mind Aqua users will keep seeing the deprecated message but just wonder how to surpass the deprecated message properly. I can copy the codes for combining jobs used in Terra to Aqua, just a few lines. But if the mega job is not supported yet, why the combination of result objects are deprecated? |
We can’t do that. Let’s think about an option. |
Can we make a temp code in aqua that allows you to combine results. For terra, we want to only have one result for a job. We will work on how we send larger jobs to the api as a separate thread. I am closing this for now |
So what is the proper way to combine two |
Was this issue ever solved? I want to combine two result objects too. |
I am also looking for a solution to this problem. Is there any progress? |
What is the expected behavior?
In the newest branch, there is a deprecated warning about discouraging use
+
to combine multiple result objects; however, I can not find a proper way to combine the result object if I have multiple results.The situation is that since there is a limitation to submit circuits to the remote quantum device, we need to get the results over multiple jobs. For the easy usage, we would like to combine the result objects into one and then users are able to retrieve the result easier.
Or the limitation of number of circuits can be submitted in one job is removed? If so, I do not need to split the circuits into multiple jobs and then there is no need to combine result objects.
The text was updated successfully, but these errors were encountered: