Skip to content

Commit e250da4

Browse files
TheKharleeciJooNivrkronbergJMuff22
authored
update job submit instructions (#2623)
* update job submit instructions * update technical details * update overview * update broken references * Add note on q50 topology * update topology image * update sample job scripts * add separate tables for backends * table tabs for qiskit and cirq examples * Fix errors in transpile / decompose section * update sample scripts * table tabs for batch script * table tabs for batch and python scripts * wording * typo * table tabs for metadata * Add q50 reference to fom, fix link * typo * update running jobs interactively * add redirects * Update mkdocs.yml Co-authored-by: Rasmus Kronberg <[email protected]> * Update docs/accounts/index.md Co-authored-by: Jake Muff <[email protected]> * update images * update broken links * fix nav structure * update accounts links * update running-jobs * formatting, fix images * formatting * add kvasi redirect * update helmi topology diagram * update interactive job instruction --------- Co-authored-by: Joonas Nivala <[email protected]> Co-authored-by: Rasmus Kronberg <[email protected]> Co-authored-by: Jake Muff <[email protected]>
1 parent 5c61d6a commit e250da4

26 files changed

+1073
-742
lines changed

docs/accounts/billing.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,6 @@ at research.csc.fi.
1818
data stored in Allas is billed.
1919
* [Pouta billing](../cloud/pouta/accounting.md)
2020
* [Rahti billing](../cloud/rahti/billing.md)
21-
* [Kvasi billing](../computing/quantum-computing/kvasi/kvasi-billing.md)
2221
* [SD Connect and SD Desktop billing](../data/sensitive-data/sd-use-case-new-user-project-manager.md#sd-connect-bu-consumption)
2322

2423

docs/accounts/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ The Project Manager is typically a leader of a research team or other senior res
1414
* **Billing Units** (BUs) are used to allocate resources to users' projects. You can apply for Billing Units in [MyCSC](https://my.csc.fi) portal and CSC grants BUs to projects. [Usage consumes billing units](billing.md) but **no actual payment** is required.
1515
However, the amount of billing units must always remain positive.
1616

17-
* **LUMI projects** used to manage access to LUMI and the resources provided by it. LUMI projects are restricted to LUMI environment only (LUMI-C, LUMI-G etc.). Finnish LUMI projects are fixed in time and resources, and the total resources must be defined already in the project application. Lumi projects are also used for [Helmi quantum computer](../computing/quantum-computing/helmi/helmi-from-lumi.md). For further information please see [these instructions](https://www.lumi-supercomputer.eu/get-started-2021/users-in-finland/){:target="_blank"}.
17+
* **LUMI projects** used to manage access to LUMI and the resources provided by it. LUMI projects are restricted to LUMI environment only (LUMI-C, LUMI-G etc.). Finnish LUMI projects are fixed in time and resources, and the total resources must be defined already in the project application. Lumi projects are also used for [FiQCI quantum computers](../computing/quantum-computing/access.md). For further information please see [these instructions](https://www.lumi-supercomputer.eu/get-started-2021/users-in-finland/){:target="_blank"}.
1818

1919
* **My.csc.fi portal** MyCSC is the self-service CSC customer portal for research and education customers and end-users. MyCSC is also available for any other CSC customer or end-user, if they have CSC user accounts according to the CSCID policies.
2020
MyCSC portal offers users the functionality for registering CSC user accounts, creating computing or data projects, adding members to projects, and applying resources for projects. Users can also manage their projects and project lifecycles through MyCSC, and they can see the resources consumption and amount of stored data there.

docs/apps/cirq-on-iqm.md

Lines changed: 11 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -14,16 +14,16 @@ catalog:
1414
# Cirq-on-iqm
1515

1616
Cirq on IQM is an open-source cirq adapter for IQM quantum computers. It is
17-
installed as `fiqci-vtt-cirq` on LUMI. It is used for running quantum circuits on
18-
[Helmi](../computing/quantum-computing/helmi/running-on-helmi.md).
17+
installed as `fiqci-vtt-cirq` on LUMI. It is used for running quantum circuits on the
18+
[quantum computers](../computing/quantum-computing/running-quantum-jobs.md).
1919

2020
## Available
2121

2222
Currently supported [cirq-on-iqm](https://iqm-finland.github.io/cirq-on-iqm/) versions:
2323

2424
| Version | Module | LUMI | Notes |
2525
|:--------|:-------------------------------------|:-----:|-----------------|
26-
| 15.2 | `fiqci-vtt-cirq/15.2` | X | |
26+
| 16.2 | `fiqci-vtt-cirq/16.2` | X | |
2727

2828

2929
All modules are based on Tykky using LUMI-container-wrapper.
@@ -61,14 +61,14 @@ module avail fiqci-vtt-cirq
6161

6262
### Example batch script
6363

64-
Example batch script for running a quantum job on Helmi:
64+
Example batch script for running a quantum job:
6565

6666
```bash title="LUMI"
6767
#!/bin/bash -l
6868

69-
#SBATCH --job-name=helmijob # Job name
70-
#SBATCH --output=helmijob.o%j # Name of stdout output file
71-
#SBATCH --error=helmijob.e%j # Name of stderr error file
69+
#SBATCH --job-name=quantumjob # Job name
70+
#SBATCH --output=quantumjob.o%j # Name of stdout output file
71+
#SBATCH --error=quantumjob.e%j # Name of stderr error file
7272
#SBATCH --partition=q_fiqci # Partition (queue) name
7373
#SBATCH --ntasks=1 # One task (process)
7474
#SBATCH --cpus-per-task=1 # Number of cores (threads)
@@ -79,6 +79,9 @@ Example batch script for running a quantum job on Helmi:
7979
module use /appl/local/quantum/modulefiles
8080
module load fiqci-vtt-cirq
8181

82+
export DEVICES=("Q5") #export DEVICES=("Q5" "Q50") to use Helmi and Q50
83+
source $RUN_SETUP
84+
8285
python -u quantum_job.py
8386
```
8487

@@ -87,4 +90,4 @@ Submit the script with `sbatch <script_name>.sh`.
8790
## More information
8891

8992
- [Cirq-IQM documentation](https://iqm-finland.github.io/cirq-on-iqm/user_guide.html)
90-
- [Quantum-Computing](../computing/quantum-computing/helmi/running-on-helmi.md)
93+
- [Quantum-Computing](../computing/quantum-computing/running-quantum-jobs.md)

docs/apps/qiskit-on-iqm.md

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,8 @@ catalog:
1414
# Qiskit-on-iqm
1515

1616
Qiskit on IQM is an open-source qiskit adapter for IQM quantum computers. It is
17-
installed as `fiqci-vtt-qiskit` on LUMI. It is used for running quantum circuits on
18-
[Helmi](../computing/quantum-computing/helmi/running-on-helmi.md).
17+
installed as `fiqci-vtt-qiskit` on LUMI. It is used for running quantum circuits on the
18+
[quantum computers](../computing/quantum-computing/running-quantum-jobs.md).
1919

2020

2121
## Available
@@ -25,7 +25,7 @@ versions:
2525

2626
| Version | Module | LUMI | Notes |
2727
|:--------|:-------------------------------------|:-----:|-----------------|
28-
| 15.5 | `fiqci-vtt-qiskit/15.5` | X | |
28+
| 17.8 | `fiqci-vtt-qiskit/17.8` | X | |
2929

3030
All modules are based on Tykky using LUMI-container-wrapper.
3131
Wrapper scripts have been provided so that common commands such as `python`,
@@ -62,14 +62,14 @@ module avail fiqci-vtt-qiskit
6262

6363
### Example batch script
6464

65-
Example batch script for running a quantum job on Helmi:
65+
Example batch script for running a quantum job:
6666

6767
```bash title="LUMI"
6868
#!/bin/bash -l
6969

70-
#SBATCH --job-name=helmijob # Job name
71-
#SBATCH --output=helmijob.o%j # Name of stdout output file
72-
#SBATCH --error=helmijob.e%j # Name of stderr error file
70+
#SBATCH --job-name=quantumjob # Job name
71+
#SBATCH --output=quantumjob.o%j # Name of stdout output file
72+
#SBATCH --error=quantumjob.e%j # Name of stderr error file
7373
#SBATCH --partition=q_fiqci # Partition (queue) name
7474
#SBATCH --ntasks=1 # One task (process)
7575
#SBATCH --cpus-per-task=1 # Number of cores (threads)
@@ -79,7 +79,8 @@ Example batch script for running a quantum job on Helmi:
7979

8080
module use /appl/local/quantum/modulefiles
8181
module load fiqci-vtt-qiskit
82-
82+
export DEVICES=("Q5") #export DEVICES=("Q5" "Q50") to use Helmi and Q50
83+
source $RUN_SETUP
8384
python -u quantum_job.py
8485
```
8586

@@ -88,4 +89,4 @@ Submit the script with `sbatch <script_name>.sh`.
8889
## More information
8990

9091
- [Qiskit-IQM documentation](https://iqm-finland.github.io/qiskit-on-iqm/)
91-
- [Quantum-Computing](../computing/quantum-computing/helmi/running-on-helmi.md)
92+
- [Quantum-Computing](../computing/quantum-computing/running-quantum-jobs.md)

docs/apps/qiskit.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,8 +17,8 @@ catalog:
1717

1818
Qiskit is an open-source software for working with quantum computers at the level of circuits, pulses, and algorithms.
1919
This page contains information in regard to running Quantum simulations using qiskit inside of a singularity container.
20-
For information pertaining to running jobs on Helmi using qiskit please refer to this documentation:
21-
[Running on Helmi](../computing/quantum-computing/helmi/running-on-helmi.md).
20+
For information pertaining to running jobs on the physical quantum computers using qiskit please refer to this documentation:
21+
[Running quantum jobs](../computing/quantum-computing/running-quantum-jobs.md).
2222

2323
!!! info "News"
2424
**19.02.2025** Installed `qiskit/1.3.2` in a singularity container on LUMI with all major Qiskit packages and

docs/computing/available-systems.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# Systems
22

33
CSC's computing environment consists of supercomputers Puhti and
4-
Mahti, and the quantum learning machine Kvasi. Puhti and Mahti have a
4+
Mahti. Puhti and Mahti have a
55
fairly similar compute environment, and there is a wide range of
66
workloads that can utilize both efficiently. At the same time their
77
hardware is different, and this makes some worklods uniquely suitable
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
# Setting up a LUMI project and accounts for accessing the Quantum computers
2+
3+
This page outlines the steps to set up a LUMI account and project for accessing the **Helmi(VTT Q5)** and **VTT Q50** quantum computers. It is assumed that you have some knowledge of supercomputing systems. If you're new, start with the [overview of CSC supercomputers](../../computing/index.md).
4+
5+
To access Helmi or Q50, you must first create a LUMI project with quantum computing resources: [Quantum Projects on LUMI](projects.md).
6+
7+
Once the project is created, the **Principal Investigator (PI)** can invite other users: [How to add members to project](../../accounts/how-to-add-members-to-project.md)
8+
9+
The project PI is responsible for ensuring that the [Helmi Terms of Use](https://a3s.fi/FiQCI/Helmi-Terms-of-Use-2022.pdf) or [Q50 Terms of Use](https://a3s.fi/FiQCI/VTT_Quantum_Academic_Use_EULA.pdf) are followed.
10+
11+
## Connect to LUMI
12+
13+
Follow the official instructions to connect to the LUMI system: [Connecting to LUMI – Official Documentation](https://docs.lumi-supercomputer.eu/firststeps/).
14+
15+
Details for running jobs on the quantum computers through LUMI can found in the [Running quantum jobs](running-quantum-jobs.md) page.
16+
17+
## Support channels
18+
19+
For support with access via LUMI, contact the [CSC Service Desk](../../support/contact.md), reachable at [email protected].
20+
Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
# Specific instructions for the FiQCI partition on LUMI
2+
3+
The FiQCI partition within LUMI provides access to quantum processing units (QPUs) for users belonging to projects with allocated QPU resources. In addition to executing quantum workloads via LUMI, users can leverage the full LUMI infrastructure, including its software stack and quantum simulators, for development, testing, and hybrid quantum-classical workflows.
4+
5+
!!! info "View status of the quantum computers"
6+
You can check the status of the connection here: [https://fiqci.fi/status](https://fiqci.fi/status)
7+
8+
9+
## LUMI Quantum Computing projects vs. regular LUMI projects
10+
11+
Quantum computing projects are slightly different from standard LUMI projects. The main difference is, that you will
12+
need to apply for quantum resources in addition to CPU, GPU, and storage.
13+
14+
15+
## The FiQCI partition `q_fiqci`
16+
17+
Access to the quantum computers is only available through the FiQCI partition on LUMI, which provides a direct connection between a [LUMI-C
18+
node](https://docs.lumi-supercomputer.eu/hardware/lumic/) and the Fiqci quantum computers.
19+
20+
* [Further details on LUMI nodes](https://docs.lumi-supercomputer.eu/hardware/)
21+
22+
There is one queue in the LUMI partition corresponding to FiQCI projects: `q_fiqci`.
23+
Currently, the maximum run time of a quantum job is 2 hours.
24+
25+
| Name | Max walltime | Max jobs |
26+
| --------- | ------------ | -------- |
27+
| _q_fiqci_ | _2 hours_ | _64_ |
28+
29+
30+
## Storage areas
31+
32+
The `q_fiqci` partition uses the same storage policies as LUMI. You can find [further details on LUMI Storage here](https://docs.lumi-supercomputer.eu/storage/).
33+
34+
## Usage and Billing
35+
36+
Quantum computing projects work similarly to the regular LUMI system. The main differences are:
37+
38+
1. FiQCI projects use the `--partition=q_fiqci` partition instead of the regular LUMI-C `--partition=standard` and `--partition=small`.
39+
2. The maximum job walltime is **2 hours**.
40+
3. Usage is billed as QPU seconds **QPUs** in `q_fiqci`.
41+
4. The LUMI-Fiqci computing environment has to be loaded separately. See [Running on quantum jobs](./running-quantum-jobs.md) for details.
42+
43+
Presently, running through the `q_fiqci` queue will consume QPU seconds for the amount of wall-time spent running in the `q_fiqci` queue.
44+
45+
!!! success "Querying your used QPUs"
46+
You can check your used QPUs using the `lumi-allocations` tool.
47+
48+
49+
Support can be reached via the [CSC Service Desk](../../support/contact.md). Note that presently, user support is limited to technical issues.

0 commit comments

Comments
 (0)