8000 add latest releases of Qiskit, Runtime, Serverless, and Functions to Latest updates page by abbycross · Pull Request #3121 · Qiskit/documentation · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

add latest releases of Qiskit, Runtime, Serverless, and Functions to Latest updates page #3121

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

Merged
merged 20 commits into from
May 16, 2025

Conversation

abbycross
Copy link
Collaborator

No description provided.

@qiskit-bot
Copy link
Contributor

One or more of the following people are relevant to this code:

@pandasa123
Copy link
Collaborator

Qiskit Serverless

Developers can set detailed statuses and track what's happening across a workflow

Serverless workloads have several stages across a workflow. By default, the following statuses are viewable with job.status():

  • QUEUED: the workload is queued for classical resources
  • INITIALIZING: the workload is set up
  • RUNNING: the workload is currently running on classical resources
  • DONE: the workload has successfully completed

Now, you can also set custom statuses that further describe the specific workflow stage, as follows:

from qiskit_serverless import update_status, Job
 
## If your function has a mapping stage, particularly application functions, you can set the status to "RUNNING: MAPPING" as follows:
update_status(Job.MAPPING)
 
## While handling transpilation, error suppression, and so forth, you can set the status to "RUNNING: OPTIMIZING_FOR_HARDWARE":
update_status(Job.OPTIMIZING_HARDWARE)
 
## After you submit jobs to Qiskit Runtime, the underlying quantum job will be queued. You can set status to "RUNNING: WAITING_FOR_QPU":
update_status(Job.WAITING_QPU)
 
## When the Qiskit Runtime job starts running on the QPU, set the following status "RUNNING: EXECUTING_QPU":
update_status(Job.EXECUTING_QPU)
 
## Once QPU is completed and post-processing has begun, set the status "RUNNING: POST_PROCESSING":
update_status(Job.POST_PROCESSING)

Qiskit Functions

Over the coming weeks, every function will give detailed information to help you run, debug, and analyse your workflows. This includes:

  • When jobs fail, you can use job.error_message() to find out specific error codes and messages to help you debug your workflows
  • job.status() will give more information on what's happening while a Function is RUNNING, including:
    • RUNNING: MAPPING
    • RUNNING: OPTIMIZING_FOR_HARDWARE
    • RUNNING: WAITING_FOR_QPU
    • RUNNING: EXECUTING_QPU
    • RUNNING: POST_PROCESSING
  • Finally, after a Qiskit Function is complete, you can inspect how much time is spent across each stage with job.result()['metadata']['resource_usage']:
{
       ...,
	"metadata": {
		"resource_usage": {
			{
				"RUNNING: MAPPING": {
					"CPU_TIME": seconds,
					"GPU_TIME": seconds,
					"QPU_TIME": seconds,
				}, 
				"RUNNING: OPTIMIZING_FOR_HARDWARE": {
					"CPU_TIME": seconds,
					"GPU_TIME": seconds,
					"QPU_TIME": seconds,
				}, 
				"RUNNING: WAITING_FOR_QPU": {
					"CPU_TIME": seconds,
					"GPU_TIME": seconds,
					"QPU_TIME": seconds,
				}, 
				"RUNNING: EXECUTING_QPU": {
					"CPU_TIME": seconds,
					"GPU_TIME": seconds,
					"QPU_TIME": seconds,
				}, 
				"RUNNING: POST_PROCESSING": {
					"CPU_TIME": seconds,
					"GPU_TIME": seconds,
					"QPU_TIME": seconds,
				}, 
			}, 
		}
	}
}

We're hoping these changes make it easier to use Qiskit Functions, and you can get started with free trials in the catalog today

@abbycross abbycross changed the title add latest releases of Qiskit and Runtime to Latest updates page add latest releases of Qiskit, Runtime, Serverless, and Functions to Latest updates page May 16, 2025
Copy link
Collaborator
@JulesMurphy JulesMurphy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good for me, besides checking with Jessie on if we can start to hide some of the Qiskit Runtime Service items

Co-authored-by: Rebecca Dimock <66339736+beckykd@users.noreply.github.com>
@abbycross abbycross added this pull request to the merge queue May 16, 2025
Merged via the queue into main with commit d337b9e May 16, 2025
4 checks passed
@abbycross abbycross deleted the ajc/qiskit-2.0-in-latest-updates branch May 16, 2025 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

5 participants
0