scnc
/
qiskit-documentation
mirror of https://github.com/Qiskit/documentation.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[1 APRIL] Remove obsolete reservations information (#1079) 

System reservations are no longer possible for clients starting 1 April
2024.
This commit is contained in:
abbycross 2024-04-01 10:02:35 -04:00 committed by GitHub
parent 87b0799e93
commit 95307d056f
5 changed files with 2 additions and 50 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/run-new/_toc.json
View File

@ -125,10 +125,6 @@
{
"title": "Manage cost",
"url": "/run/manage-cost"
},
{
"title": "Reserve system time",
"url": "/run/reserve-system-time"
}
]
}

4
docs/run/_toc.json
View File

@ -125,10 +125,6 @@
{
"title": "Manage cost",
"url": "/run/manage-cost"
},
{
"title": "Reserve system time",
"url": "/run/reserve-system-time"
}
]
}

2
docs/run/index.mdx
View File

@ -10,7 +10,7 @@ IBM Quantum™ maintains the world’s most advanced fleet of quantum system
## The run phase
In the run phase, you send your quantum program to be executed on a quantum system. This section provides information about IBM Quantum hardware and how to connect to the instances that provide access to quantum systems. You can find details about estimating job run time and cost, running within a session, reserving time on a system, and more.
In the run phase, you send your quantum program to be executed on a quantum system. This section provides information about IBM Quantum hardware and how to connect to the instances that provide access to quantum systems. You can find details about estimating job run time and cost, running within a session, and more.
The steps during the run phase are:

40
docs/run/reserve-system-time.mdx
View File

@ -1,40 +0,0 @@
---
title: Reserve system time
description: Reserve time on a system as an IBM Quantum Network member
---
# Reserve system time
<Admonition type="caution" title="Important">
This feature is available only to organizations that belong to the [IBM Quantum&trade; Network](https://www.ibm.com/quantum/network). Educators and researchers can also make reservations and access other benefits by signing up for one of the special programs we offer. Go to the [Educators program sign-up form](https://quantum.ibm.com/programs/educators) or the [Researchers program sign-up form](https://quantum.ibm.com/programs/researchers) for more information.
</Admonition>
Under standard operating conditions, IBM Quantum systems accept jobs according to the dynamic priority assigned by the [fair-share scheduler](fair-share-queue).
![A job enters the queue and joins other jobs from various instances. The job that entered the queue first exits the queue and is sent to a backend.](/images/run/normal_queue_with_providers1.jpg "Normal device-queuing operation")
While this system attempts to balance workloads for the benefit of all users, there are often use cases where you may require limited-time access at a higher priority level. IBM Quantum provides an option to gain elevated access to specific systems over a specified period of time: **Dedicated mode**. Depending on your hub configuration, if you are a hub admin or group admin, you can reserve time in advance on a particular system with the **Systems Reservations** tool.
Example use cases for dedicated mode include the following:
- In-class demonstrations
- Iterative and near-time compute algorithms
- Jobs involving detailed noise analysis
- Time-critical projects
<Admonition type="info" title="System reservations and fair-share allocation">
System time accumulated while using system reservations counts toward an instance’s fair-share allocation amount.
</Admonition>
If you need sole access to a specific quantum system for a given instance, select dedicated mode when making a reservation (only available to members of the [IBM Quantum Network](https://www.ibm.com/quantum/network)).
![A job enters the queue and joins other jobs from various instances. The jobs that are sent from Instance 2 are all processed in their own dedicated queue while jobs from other instances wait in the normal queue.](/images/migration/dedicated_queue1.jpg "Instance #2 in dedicated mode")
The standard fair-share queue is always blocked when the device is in dedicated mode.
![A job enters the queue and joins other jobs from various instances. There are no jobs from Instance 2. Because the backend is in dedicated mode for instance 2, no jobs are processed. All jobs wait in the normal queue.](/images/migration/dedicated_queue_no_jobs1.jpg "Dedicated mode with no dedicated jobs")
Dedicated mode with no dedicated jobs from instance #2 leaves the device idle.
This allows users to implement algorithms where input circuits are conditioned on previous results, such as iterative and near-time compute methods, without having to wait for other users’ results to process. If the dedicated instance has multiple users, then a single user’s jobs may be queued behind those of other users in the instance, as the execution is first-in first-out.

2
docs/run/system-information.mdx
View File

@ -54,7 +54,7 @@ These values are shown on both the Systems and Simulators tabs of the [Compute r
* **Status** - The system status.
* **Total pending jobs** - The total number of jobs that you have submitted to this system.
* **Processor type** - Reflects the system topology and indicates the approximate qubit count.
* **Features** - Additional information about the system, such as whether it can be reserved and whether it supports pulse inputs.
* **Features** - Additional information about the system, such as whether it supports pulse inputs.
**Additional information available on the details page for each system**