Skip to content

Commit

Permalink
Get rid of separate Intro to sessions
Browse files Browse the repository at this point in the history
  • Loading branch information
beckykd committed Jan 17, 2025
1 parent 9bed2f6 commit f9cfaa0
Show file tree
Hide file tree
Showing 4 changed files with 6 additions and 93 deletions.
7 changes: 4 additions & 3 deletions docs/guides/execution-modes.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ description: An overview of the available execution modes in Qiskit Runtime; ses
---
# Introduction to Qiskit Runtime execution modes

There are several ways to run workloads, depending on your needs. Execution modes determine how your jobs are scheduled, and choosing the right execution mode allows your jobs to run efficiently within your time budget.
There are several ways to run workloads, depending on your needs. Execution modes determine how your jobs are scheduled, and choosing the right execution mode allows your jobs to run efficiently within your budget.


**Job mode**: A single primitive request of the estimator or the sampler made without a context manager. Circuits and inputs are packaged as primitive unified blocs (PUBs) and submitted as an execution task on the quantum computer. To run in job mode, specify `mode=backend` when instantiating a primitive. See [Primitives examples](/guides/primitives-examples) for examples.
Expand Down Expand Up @@ -60,8 +60,9 @@ The the benefits of each are summarazed below:
- There is usually minimal delay between jobs, which can help avoid drift.
- If you partition your workload into multiple jobs and run them in batch mode, you can get results from individual jobs, which makes them more flexible to work with.
- **Session**
- Dedicated and exclusive access to the QPU during the session active window, and no other users’ or QPU jobs can run.
- Useful for workloads that don’t have all inputs ready at the outset.
- Dedicated and exclusive access to the QPU during the session active window.
- Can run multiple experiments simultaneously.
- Useful for workloads that don’t have all inputs ready at the outset or for iterative workloads that require dedicated access.
- **Job**
- Easiest to use when running a small experiment.
- Might run sooner than batch mode.
Expand Down
4 changes: 2 additions & 2 deletions docs/guides/primitives-examples.ipynb
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@
"isa_circuit = pm.run(circuit)\n",
"isa_observable = observable.apply_layout(isa_circuit.layout)\n",
"\n",
"estimator = Estimator(backend)\n",
"estimator = Estimator(mode=backend)\n",
"job = estimator.run([(isa_circuit, isa_observable)])\n",
"result = job.result()\n",
"\n",
Expand Down Expand Up @@ -440,7 +440,7 @@
"pm = generate_preset_pass_manager(backend=backend, optimization_level=1)\n",
"isa_circuits = pm.run(circuits)\n",
"\n",
"sampler = Sampler(backend)\n",
"sampler = Sampler(mode=backend)\n",
"job = sampler.run(isa_circuits)\n",
"result = job.result()\n",
"\n",
Expand Down
75 changes: 0 additions & 75 deletions docs/guides/sessions.mdx

This file was deleted.

13 changes: 0 additions & 13 deletions scripts/config/internal-links.json
Original file line number Diff line number Diff line change
Expand Up @@ -1684,19 +1684,6 @@
"#when-should-i-use-qiskit-serverless"
]
},
{
"path": "docs/guides/sessions.mdx",
"anchors": [
"#advantages-of-using-sessions",
"#end-a-session",
"#ends",
"#how-sessions-work",
"#introduction-to-qiskit-runtime-sessions",
"#next-steps",
"#usage-patterns",
"#what-is-a-session"
]
},
{
"path": "docs/guides/set-optimization.ipynb",
"anchors": [
Expand Down

0 comments on commit f9cfaa0

Please sign in to comment.