You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and 80% seems to be the real value. I had no explanation for this low
213
+
camera usage. My guesses are: (1) the email sent to the learners is too
214
+
long and complex, which increased uncertainty in the learners, (2) that
215
+
same email mentions the recording of learners.
216
+
217
+
Let's take a look at that email..
218
+
219
+
???- question "What is the email text?"
220
+
221
+
```text
222
+
Hello!
223
+
224
+
This email contains information for the NAISS four days online course “Introduction to Python and Using Python in an HPC environment”, which will be given Monday 20 April, Wednesday 22 April, Thursday 23 April, and Friday 24 April, 2026, 9:00-16:00 each day.
225
+
226
+
NOTE that the course starts at 9:00 not 9:15! See the schedule linked below, for each day.
227
+
228
+
We will use Zoom for this online course. See below for zoom link (#10 - last item).
229
+
230
+
NOTE please go through everything, as there is important information about pre-requirements, how to login, etc. Also be aware that you may need to set up MFA for UPPMAX and NSC, Pocket Pass for LUNARC, and SSH keys/kerberos for PDC (depending on which system you are using), which can take a day to get setup, so do this immediately.
231
+
232
+
If you have questions about this course, please fill in a support ticket at https://supr.naiss.se/support/. If you do not have a SUPR account, you can send a support mail to training@naiss.se instead, but using the form is recommended.
233
+
234
+
1) Schedule:
235
+
236
+
- Logging in and Introduction to Python (Monday): https://uppmax.github.io/naiss_intro_python/schedule/
237
+
- Packages and basic analysis (Wednesday): https://uppmax.github.io/HPC-python/schedule.html#day-2-packages-and-basic-analysis
238
+
- Advanced analysis and batch jobs (Thursday): https://uppmax.github.io/HPC-python/schedule.html#day-3-advanced-analysis-and-batch-jobs
239
+
- Parallelism, GPUs and machine learning (Friday): https://uppmax.github.io/HPC-python/schedule.html#day-4-parallelism-gpus-and-machine-learning
- Rest of the course: https://github.com/UPPMAX/HPC-python
250
+
251
+
4) Important information about the course is gathered here: https://nextcloud.naiss.se/s/pZTn9dxLZwqmfrt
252
+
253
+
5) Questions and answers page for the course: https://nextcloud.naiss.se/s/Jbfy4kj3bSJKtfG
254
+
255
+
6) Please make sure you have an account at SUPR (https://supr.naiss.se/) and at either NSC, PDC, or C3SE (or UPPMAX, if you are affiliated with UU or HPC2N if you are affiliated with UMU, SLU, IRF, LTU, or MIUN, or LUNARC if you are affiliated with LU).
256
+
257
+
The site account for NSC/PDC/UPPMAX/HPC2N/LUNARC can be applied for through SUPR after you have your SUPR account and have been added to the course project.
258
+
259
+
The account at SUPR and the accounts at NSC/PDC/HPC2N/UPPMAX/LUNARC are all SEPARATE. You should have already been contacted about getting a SUPR account if you did not have one. You should have also been added to the course project, so you can go to https://supr.naiss.se/account/ and apply for an account if you do not have one.
260
+
261
+
7) Please make sure you have installed either ThinLinc or an SSH client. ThinLinc is strongly RECOMMENDED for this course and can be installed from https://www.cendio.com/thinlinc/download If you have an account at a centre that has OpenOnDemand or GfxLauncher from inside ThinLinc, you can also use that.
262
+
263
+
264
+
Login info
265
+
266
+
- UPPMAX – Pelle
267
+
- SSH: pelle.uppmax.uu.se
268
+
- ThinLinc: pelle-gui.uppmax.uu.se
269
+
- HPC2N - Kebnekaise
270
+
- SSH: kebnekaise.hpc2n.umu.se
271
+
- ThinLinc: kebnekaise-tl.hpc2n.umu.se
272
+
- From web browser: https://kebnekaise-tl.hpc2n.umu.se:300/
- Open OnDemand portal: https://alvis.c3se.chalmers.se
289
+
290
+
Note that if you are using Open OnDemand or ThinLinc, you will connect to a graphical interface and do not need a separate X11 server to enable opening graphics and GUIs.
291
+
292
+
Note that if you are using Windows and do not already have an SSH client you use, we strongly recommend using ThinLinc.
293
+
294
+
8) Pre-requirements: This page contains some info on getting ready to login (including the above info), but also a short summary/list of links for things like Linux, editors, and coding: https://uppmax.github.io/HPC-python/prereqs.html
295
+
296
+
9) Course project and policy: As part of the hands-on, you will be given temporary access to a course project, which will be used for running the hands-on examples. There are some policies regarding this, that we ask that you follow:
297
+
298
+
- You may be given access to the project before the course; please do not use the allocation for running your own codes. Usage of the project before the course means the priority of jobs submitted to it goes down, diminishing the opportunity for you and your fellow participants to run the examples during the course.
299
+
- The course project will be open 1-2 weeks after the course, giving the participants the opportunity to test run examples and shorter codes related to the course. During this time, we ask that you only use it for running course related jobs. Use your own discretion, but it could be: (modified) examples from the hands-on, short personal codes that have been modified to test things learned at the course, etc.
300
+
- Anyone found to be misusing the course project, using up large amounts of the allocation for their own production runs, will be removed from the course project.
301
+
- When the course is no longer active, all files in the attached storage directory will be deleted. Please copy out anything you want to save before that.
- LUNARC storage directory: None – use home directory
320
+
321
+
10) Zoom info for the course:
322
+
323
+
a) There will be a zoom for the lectures. It is the same zoom link for each day.
324
+
b) When you join the Zoom meeting, use your REAL NAME.
325
+
c) Please MUTE your microphone when you are not speaking and use the “Raise hand” functionality under the “Participants” window during the lecture. Please do not clutter the Zoom chat. Behave politely!
326
+
d) If you have questions during the lectures, you can write them on this page: https://nextcloud.naiss.se/s/Jbfy4kj3bSJKtfG
327
+
e) There may be breakout rooms used in the Zoom for the hands-ons and for discussions. Most likely there will be a “silent” room for those who just wish to work on their own, a discussion room (or rooms) for cooperation, and the rest will be in the main room. If you are in the silent room and need help, go to the main room and contact a helper. There will be breakout rooms that can be used if you want individual help. There will also be parallel sessions.
328
+
f) Some of the lectures and demos will be recorded, but not the hands-ons sessions. If you ask questions during the lectures, you may thus be recorded. If you do not wish to be recorded, then please keep your microphone muted and your camera off and write your questions in the Q/A document.
329
+
330
+
ZOOM (same each day):
331
+
332
+
1. Zoom: [Link]
333
+
2. Meeting ID: [Meeting ID]
334
+
3. Passcode: [Passcode]
335
+
336
+
See you Monday!
337
+
338
+
Sahar, Richel, Pedro, Jayant, Björn, Birgitte
339
+
```
340
+
341
+
I feel it is mostly the length of the email that may make the learners
342
+
uncomfortable. The mentioning of recording is not that prominent.
343
+
I will suggest to send shorter emails to the learners, or
344
+
to encourage camera usage.
345
+
346
+
-[ ] Suggest to send shorter emails to the learners and/or encourage
347
+
camera usage in that email
348
+
203
349
- Did the parts of the introduction flow into each other naturally?
350
+
351
+
She said the parts flowed naturally into one another. She did mention
352
+
that the Priors felt rushed. And I agree with that. My intention
353
+
is to ask a question, wait three seconds and then prompt for an answer.
354
+
I feel that due to Zoom uncertainty I went too quick.
355
+
356
+
-[ ] Wait 3 seconds after asking a question in the Prior
357
+
358
+
We discussed the Prior a bit and she suggested to also show the question
359
+
visually as text. I agreed with that idea; to have two types of inputs
360
+
and I did look for captions in Zoom (and could not find it).
361
+
However, I feel I should at least try this once, to see how this feels.
362
+
363
+
-[ ] Try out two input methods for asking a question in the Prior
364
+
204
365
- Was there a part that had an unclear purpose?
205
366
206
-
...
367
+
No.
368
+
369
+
Then we discussed some other things, such as Cold Calling.
370
+
She suggested to try out a soft group activity,
371
+
e.g. list three things that all three breakout room people have in common.
372
+
In that way, people feel less more comfortable during the Cold Calling.
373
+
374
+
-[ ] Try out a soft group activity
375
+
376
+
Additionally, it was suggested to use the Zoom 'Yes'/'No' reactions
377
+
instead of a 'Raise Hand' to put people into individual Breakout rooms.
378
+
I use 'Raise Hand' to get those people to be sorted to the top of
379
+
the participant list. However, 'Yes'/'No' reactions forces everyone to
380
+
respond.
381
+
382
+
-[ ] Try out to use 'Yes'/'No' reaction (instead of 'Raise Hand')
383
+
for asking for a single breakout room
384
+
385
+
Besides that we discussed some other things:
386
+
387
+
- Always doing what is best for learning, or giving a bit
388
+
of leeway to our learners for some personal preferences that
389
+
are unhelpful to learning (e.g. forcing people to work together)
0 commit comments