Skip to content

Commit 96cf439

Browse files
authored
Merge branch 'master' into report_changes.sh-fix
2 parents 6b62030 + 523c2b5 commit 96cf439

File tree

13 files changed

+222
-64
lines changed

13 files changed

+222
-64
lines changed

csc-overrides/partials/announcement.html

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,9 @@
66
#}
77
{# import ".icons/material/coffee.svg" as icon #}
88
{# import ".icons/material/chat.svg" as icon #}
9-
{# import ".icons/material/information.svg" as icon #}
10-
{% import ".icons/material/alert.svg" as icon %}
9+
{% import ".icons/material/information.svg" as icon %}
10+
{# import ".icons/material/alert.svg" as icon #}
11+
{# import ".icons/material/wrench.svg" as icon #}
1112
{# import ".icons/material/rocket-launch.svg" as icon #}
1213
{# import ".icons/material/test-tube.svg" as icon #}
1314
{# import ".icons/material/beaker.svg" as icon #}
@@ -17,7 +18,7 @@
1718
<div class="announcement-icon">{{ icon }}</div>
1819
{# Put the announcement, in HTML, right under this comment! #}
1920
<p>
20-
Significant changes to Puhti & Mahti authentication came in April! Read about the <a href="{{ base_url | url }}/support/wn/comp-new/#ssh-key">SSH key</a> and <a href="{{ base_url | url }}/support/wn/comp-new/#mfa">multi-factor authentication</a> requirements.
21+
Note: Starting from June 11, 2025, using the MyCSC portal will require multi-factor authentication (MFA). <a href="{{ base_url | url }}/accounts/mfa/">Read our MFA guide here</a>.
2122
</p>
2223
{# ...and right above _this_ comment. #}
2324
<div class="announcement-icon announcement-icon-end">{{ icon }}</div>

docs/accounts/how-to-create-new-project.md

Lines changed: 34 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ For further information on LUMI projects please visit [Users in Finland](https:/
7676

7777
A student can be the project manager of the student project. Please read the [Getting started with the Student Project](../support/tutorials/student_quick.md) carefully and then you can continue with the instructions below.
7878

79-
The student category is reserved for [free-of-charge](https://research.csc.fi/free-of-charge-use-cases){:target="_blank"} use cases. This category project is a fixed time (maximum of 6 months, non-extendable), fixed resource and is designed to support student's work with higher educational institutes' courses and thesis work.
79+
The student category is reserved for [free-of-charge](https://research.csc.fi/free-of-charge-use-cases) use cases. This category project is a fixed time (maximum of 6 months, non-extendable), fixed resource and is designed to support student's work with higher educational institutes' courses and thesis work.
8080

8181
1. Login to [MyCSC](http://my.csc.fi/) with your CSC user account or Haka/Virtu account.
8282
2. Choose **Projects** in the navigation menu on the left.
@@ -90,3 +90,36 @@ The student category is reserved for [free-of-charge](https://research.csc.fi/fr
9090
10. Click **Create project**.
9191

9292
If you wish, you can add other members to your project. The easiest way to do so is to use an [invitation link](how-to-add-members-to-project.md#using-invitation-link).
93+
94+
## Right to create CSC projects based on Haka affiliation
95+
96+
Here we describe how the Haka identity linked to your CSC account affects your right to create academic, course and student type CSC projects. During your Haka login we get information about your position in your home organisation. Below this information about your position is called "Haka affiliation information". In the table below you can see how Haka affiliation affects on the right to create and act as the Project Manager of a CSC Project.
97+
98+
| Haka Affiliation ([eduPersonScopedAffiliation](https://wiki.eduuni.fi/spaces/CSCHAKA/pages/256884450/funetEduPersonSchema2dot5#funetEduPersonSchema2dot5-eduPersonScopedAffiliation)) | Description ([from Haka documentation](https://wiki.eduuni.fi/spaces/CSCHAKA/pages/256884450/funetEduPersonSchema2dot5#funetEduPersonSchema2dot5-eduPersonAffiliation)) | Academic Project | Course Project | Student Project |
99+
| -- | -- | -- | -- | -- |
100+
| `faculty@org.fi` | research and education workers at laboratories and institutes; e.g. professors, researchers, lecturers, assistants, whether employed by the institution or some other organisation (such as Academy of Finland). Docents may be affiliated as faculty, if they are actively involved in research or education in an institute. ||||
101+
| `staff@org.fi` | administrational workers at the institution, whether employed by the institution or some other organisation ||||
102+
| `employee@org.fi` |a person actually employed by the institution ||||
103+
| `student@org.fi` (without being faculty, staff or employee) | a student who has registered as being present (läsnäoleva). ||||
104+
| `member@org.fi` (without being faculty, staff or employee) | This value covers all categories mentioned above plus students taking qualifying education courses, further education courses or open university and further education center students (pätevöitymiseen tähtäävä täydennyskoulutus, muu täydennyskoulutus, avoin yliopisto/korkeakoulu, täydennyskoulutuskeskuksen opiskelijat). ||||
105+
106+
In addition, you may have one or more of the following Haka affiliation information types, but these do not give you the right to create CSC Projects: `affiliate@org.fi`, `alum@org.fi`, `library-walk-in@org.fi`
107+
108+
More information about the policy in [Prerequisites and responsibilities for a CSC project manager](https://research.csc.fi/terms-of-use/prerequisites-for-a-project-manager/).
109+
110+
_Note_: If you are not eligible to be the Project Manager yourself, you might have a supervisor or colleague that can create a CSC Project and add you as a CSC project member.
111+
112+
### Checking your Haka affiliation information
113+
114+
You can check your Haka attributes in MyCSC portal:
115+
116+
1. Go to [https://my.csc.fi/userinfo](https://my.csc.fi/userinfo) and click on **Retrieve userinfo**
117+
2. Log in with your organization's Haka ID
118+
3. Your affiliations are in the **eduPersonScopedAffiliation** section
119+
120+
### Problems with the Haka affiliation information
121+
- If you cannot create a CSC Project, please log in to MyCSC again with Haka to update you Haka affiliation information.
122+
- If you think that your Haka affiliation information may be incorrect, please contact your home organisation.
123+
124+
125+

docs/apps/geoconda.md

Lines changed: 11 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -168,27 +168,15 @@ spyder
168168
* `os.environ["_JAVA_OPTIONS"] = "-Xmx4g"` in the beginning of your Python code.
169169

170170
### Google Earth Engine authentication set up in Puhti
171-
For using Google Earth Engine (GEE) API with `earthengine-api` package, one needs to have an account in GEE. Before first usage, also set up GEE authentication in Puhti:
172-
173-
1. Open Puhti web interface
174-
2. Start Desktop app
175-
3. In the Desktop, open:
176-
* Web Browser under Applications menu and
177-
* Terminal from shortcuts
178-
4. In the Terminal:
171+
For using Google Earth Engine (GEE) API with `earthengine-api` package, one needs to have an account and project in GEE. Before first usage, also set up GEE authentication in Puhti:
179172

180173
```
181174
module load geoconda
182-
python
183-
184-
import os
185-
os.environ['PATH'] = '/appl/opt/csc-cli-utils/google-cloud-sdk/bin:' + os.environ['PATH']
186-
187-
import ee
188-
ee.Authenticate()
175+
export PATH=/appl/opt/csc-cli-utils/google-cloud-sdk/bin:$PATH
176+
earthengine authenticate
189177
```
190178

191-
This prints out a long link and asks for a code. Copy the link to the web browser and open the Google log-in page. Log-in and copy the created code back to Python.
179+
This prints out a long link and asks for a code. Copy the link to the web browser of your local laptop. Follow the instructions on the web page and finally copy the created code back to Terminal.
192180

193181
## Using Allas or LUMI-O from Python
194182

@@ -224,20 +212,17 @@ Geoconda conda environment files and `download_wbt` and `start_wbt.py` needed fo
224212

225213
## References
226214

227-
- [CSC Python parallelisation examples]
228-
- [Python spatial] libraries
229-
- [Geoprocessing with Python using Open Source GIS]
230-
- [GeoExamples], a lot of examples of using Python for spatial analysis
231-
- [Automating GIS processes course materials], where most of the exercises are done using Python (University of Helsinki)
232-
- [Geohack Week materials]
233-
- [Multiprocessing Basics]
234-
- [Geographic Data Science with Python]
235-
- [Aalto Spatial Analytics course material]
215+
- [CSC Python parallelisation examples](https://github.com/csc-training/geocomputing/tree/master/python/puhti)
216+
- [Multiprocessing Basics](https://pymotw.com/2/multiprocessing/basics.html)
217+
- [Automating GIS processes course materials](https://automating-gis-processes.github.io) by University of Helsinki
218+
- [Aalto Spatial Analytics course material](https://spatial-analytics.readthedocs.io/en/latest/course-info/course-info.html) by Henrikki Tenkanen / Aalto University
219+
- [Introduction to GIS Programming](https://geog-312.gishub.org/index.html) by Dr. Qiusheng Wu / University of Tennessee
220+
- [Geographic Data Science with Python](https://geographicdata.science/book/intro.html) by Sergio Rey, Dani Arribas-Bel, Levi Wolf
221+
- [Python Foundation for Spatial Analysis](https://courses.spatialthoughts.com/python-foundation.html) by Ujaval Gandhi
236222

237223
------------------------------------------------------------------------
238224

239225

240-
[Conda]: https://conda.io/docs/
241226
[cartopy]: http://scitools.org.uk/cartopy/
242227
[descartes]: https://pypi.python.org/pypi/descartes
243228
[fiona]: https://pypi.python.org/pypi/Fiona
@@ -261,16 +246,4 @@ Geoconda conda environment files and `download_wbt` and `start_wbt.py` needed fo
261246
[snappy]: https://senbox.atlassian.net/wiki/spaces/SNAP/pages/19300362/How+to+use+the+SNAP+API+from+Python
262247
[SNAP]: snap.md
263248
[spyder]: https://docs.spyder-ide.org/
264-
[Conda environments]: https://conda.io/docs/user-guide/tasks/manage-environments.html#
265-
[Bioconda]: bioconda.md
266-
[Python spatial]: https://github.com/SpatialPython/spatial_python/blob/master/packages.md
267-
[Geoprocessing with Python using Open Source GIS]: http://www.gis.usu.edu/%7Echrisg/python/2009/
268-
[GeoExamples]: https://geoexamples.com/
269-
[Automating GIS processes course materials]: https://automating-gis-processes.github.io
270-
[Geohack Week materials]: https://geohackweek.github.io/schedule.html
271-
[Multiprocessing Basics]: https://pymotw.com/2/multiprocessing/basics.html
272249
[sentinelsat]: https://sentinelsat.readthedocs.io/en/stable/index.html
273-
[CSC Python parallelisation examples]: https://github.com/csc-training/geocomputing/tree/master/python/puhti
274-
[Geographic Data Science with Python]: https://geographicdata.science/book/intro.html
275-
[Aalto Spatial Analytics course material]: https://spatial-analytics.readthedocs.io/en/latest/course-info/course-info.html
276-

docs/computing/index.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,11 @@
11
# Overview
22

33
!!! Note
4-
For an overview of the LUMI supercomputer, see [the LUMI
5-
documentation](https://docs.lumi-supercomputer.eu/hardware/).
4+
For an overview of CSC's next national supercomputer Roihu coming in 2026,
5+
[see this page](systems-roihu.md).
6+
7+
For an overview of the LUMI supercomputer, see
8+
[the LUMI documentation](https://docs.lumi-supercomputer.eu/hardware/).
69

710
Puhti and Mahti are CSC's supercomputers. Puhti has been available for CSC users
811
since 2 September 2019 and Mahti has been available since 26 August 2020. LUMI is
@@ -17,6 +20,9 @@ since 2021 (Mahti AI) with Nvidia Ampere GPUs. See [specifications](available-sy
1720
for details on the systems and [this page for an outline of differences between LUMI-C and
1821
Mahti](lumi-vs-mahti.md).
1922

23+
Puhti and Mahti will be replaced in 2026 by CSC's next national supercomputer
24+
called **Roihu**. [Read more about Roihu here](systems-roihu.md).
25+
2026
CSC supercomputers use the Linux operating system and we recommend that you are familiar with
2127
basics of [Linux command line usage](../support/tutorials/env-guide/index.md) before starting.
2228

docs/computing/systems-roihu.md

Lines changed: 16 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,16 @@
44
This page contains preliminary information about CSC's next national
55
supercomputer Roihu, which is projected to be in researchers' use early
66
2026. Please note that the details may evolve over time.
7+
[See tentative schedule below](#schedule).
8+
9+
## Schedule
10+
11+
```mermaid
12+
graph LR;
13+
A{{Roihu will be installed at the **end of 2025**}}-->B;
14+
B{{Four-week pilot phase in **February 2026**}}-->C;
15+
C{{Roihu available for all users in **March 2026**}}-->D{{Puhti & Mahti end-of-life **later during 2026**}};
16+
```
717

818
## Compute
919

@@ -18,12 +28,12 @@ which supports the AVX-512 vector instruction set. 414 of the CPU nodes will
1828
have 768 GiB of memory, while the remaining 72 nodes will have an extended
1929
memory of 1 536 GiB each.
2030

21-
Each GPU node will be equipped with 4 Nvidia GH200 Grace Hopper superchips.
22-
Each GH200 superchip comprises one Hopper GPU and one Grace CPU with
23-
72 ARM CPU cores which are connected with a very fast interface. Each
24-
GH200 superchip has 120 GiB CPU memory and 96 GiB GPU memory, providing
25-
a total of 480 GiB CPU memory per node. This gives a total of 528 GPUs and
26-
38 016 CPU cores in the whole GPU partition.
31+
Each GPU node will be equipped with 4 Nvidia GH200 Grace Hopper superchips.
32+
Each GH200 superchip comprises one Hopper GPU and one Grace CPU with
33+
72 ARM CPU cores which are connected with a very fast interface. Each
34+
GH200 superchip has 120 GiB CPU memory and 96 GiB GPU memory, providing
35+
a total of 480 GiB CPU memory per node. This gives a total of 528 GPUs and
36+
38 016 CPU cores in the whole GPU partition.
2737

2838
The system will also provide four visualization nodes with two Nvidia L40 GPUs
2939
each, as well as four high-memory CPU nodes with 3 TiB memory and higher

docs/data/moving/copy_allas_ida.md

Lines changed: 76 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
# Copying data between Allas and IDA via Puhti
22

3+
34
## Copying data from Allas to IDA via Puhti
45

56
In order to be able to copy data from Allas to IDA with this procedure, you
@@ -114,15 +115,85 @@ for their username and password in IDA.
114115
If you do not need to continue working with the data on Puhti after uploading
115116
it to IDA, remove it from the scratch disk area of Puhti to free up disk space.
116117

118+
117119
## Copying data from IDA to Allas via Puhti
118120

119-
In order to copy data from IDA to Allas with this procedure, you need to be a
121+
In order to copy data from IDA to Allas, you need to be a
120122
member of a project that has Allas and Puhti services in use. On the IDA side,
121123
you either need to be a member of a project which has IDA service in use, or
122124
the data in question needs to be publicly available for downloading. Note that
123125
the projects in Allas, Puhti and IDA do not need to be the same.
124126

125-
In short, there are four steps to follow:
127+
### Automatic copying with ida2allas tool
128+
129+
If you wish to move a complete directory from IDA to Allas object storage service without
130+
any changes or rearrangements, you can use command line tool _ida2allas_. This tool is available
131+
in Puhti server at CSC.
132+
133+
#### 1. Connect to Puhti
134+
135+
We recommend that you run the data transfer process in one of the login nodes of the Puhti.
136+
(Login nodes can be used in this case as the data transfer process is not computationally heavy).
137+
The easiest way to open a login node session in Puhti is to use the WWW interface of Puhti:
138+
139+
* [Puhti Web interface](https://www.puhti.csc.fi)
140+
141+
In the web interface, choose *Login node shell* from the *Tools* menu. This opens a
142+
terminal session where you can set up connections to IDA and Allas and where you can
143+
execute the data transport process.
144+
145+
146+
#### 2. Establishing connections
147+
148+
First, open the Allas connection using the S3 protocol with the following commands:
149+
150+
```text
151+
module load allas
152+
allas-conf -m S3
153+
```
154+
155+
The _allas-conf_ command will prompt you to enter your CSC password. The Haka password is not accepted.
156+
After that you will choose the Allas project where the data will be copied.
157+
158+
159+
Next, establish the IDA connection with the commands:
160+
161+
```text
162+
module load ida
163+
ida_configure
164+
```
165+
166+
The configuration process will ask for your _IDA project number_ and _app password_ that you can get from [IDA web interface](https://ida.fairdata.fi).
167+
If you already have a working IDA connection configured, you can choose not to overwrite the `.ida-config` and `.netrc` files. In that case, you won’t need to retrieve a new IDA key from the web interface.
168+
169+
#### 3. Data transfer
170+
171+
Data transfer is launched with the command:
172+
173+
```text
174+
ida2allas
175+
```
176+
177+
The program will first ask whether to fetch data from the IDA staging area or the frozen area.
178+
179+
Then it will list the folders in the selected IDA area and prompt you to choose the folder to transfer.
180+
181+
Finally, the program will list the buckets (storage folders) in Allas and ask you to select the one where you want to transfer the data. You can also create a new bucket. Do not use uppercase letters, spaces, or special characters in the name of the bucket. Further, note that bucket names must be unique compared to any Allas project. Thus it is a good habit to add some project specific part to the bucket name.
182+
183+
In case of large (over 100 GiB) data transfers you can start the transfer with the commands:
184+
185+
```text
186+
screen
187+
ida2allas
188+
```
189+
190+
In the example above, _screen_ command launches a virtual terminal session where the _ida2allas_ command will continue running even if the connection to Puhti would be lost.
191+
192+
193+
194+
### Manual data transfer from IDA to Allas
195+
196+
If you don't want to copy a complete IDA directory to Allas or if you want to rearrange the data, then you need to do the data transfer in four steps:
126197

127198
1. Download the data from IDA to Puhti scratch disk
128199
2. Rearrange the data on the scratch disk, if necessary
@@ -190,7 +261,7 @@ cd /scratch/project_2000012/xferdir
190261
curl -fOJ "https://ida191.csc.fi:4430/download?token=18f6e5b7edae4f12a8a654ea22d57aa9.PA0p5PMqnzvgcXAU0Lw9SuVcyoQGgV8Ugnk3GEppU0b4UUhGWRLP8FRHB2MvyUTjPA0p5PMqnzvgcXAU0Lw9SuVcyoQGgV8Ugnk3GEppU0b4UUhGWRLP8FRHB2MvyUTjPA0p5PMqnzvgcXAU0Lw9SuVcyoQGgV8Ugnk3G_e3668097e34d437484e15d53624e7905=76679a7a-367c-474f-9e8c-c3869a106e2f_ehr3hd76&package=76679a7a-367c-474f-9e8c-c3869a106e2f_ehr3hd76.zip"
191262
```
192263

193-
### Step 2. Rearrange the data on scratch, if necessary
264+
#### Step 2. Rearrange the data on scratch, if necessary
194265

195266
In case you would like to rearrange the data or remove parts of it, you can do
196267
it on the scratch disk before you upload it to Allas.
@@ -204,7 +275,7 @@ cd /scratch/project_2000012/xferdir
204275
unzip testi.zip
205276
```
206277

207-
### Step 3. Upload the data to Allas
278+
#### Step 3. Upload the data to Allas
208279

209280
The easiest way to upload the data to Allas is using the `a-put` command.
210281
`a-put` uploads a directory as one archived object to Allas. It needs enough
@@ -229,7 +300,7 @@ cd /scratch/project_2000012/xferdir
229300
a-put experiment_data
230301
```
231302

232-
### Step 4. Clean the Puhti scratch
303+
#### Step 4. Clean the Puhti scratch
233304

234305
If you do not need to continue working with the data on Puhti after uploading
235306
it to Allas, remove it from the scratch disk area of Puhti to free up disk

docs/data/moving/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,3 +12,4 @@ below the one that suits your needs best.
1212
* [Sharing and transporting files using Funet FileSender](funet.md)
1313
* [Moving data between IDA and CSC computing environment](../ida/using_ida.md)
1414
* [Remote disk mounts](disk_mount.md)
15+
* [Copying data between Allas and IDA via Puhti](copy_allas_ida.md)

0 commit comments

Comments
 (0)