Decide upon prerequisites

[richelbilderbeek]

Currently, there are no course prerequisites, as voted earlier in #5.

However, looking at a draft schedule at #13, I find it ironic that at least a third of the time is spent on logging in, where this course is on file transfer.

Could we re-vote on prerequisites?

Here I suggest 4 options, feel free to add more:

• No prerequisites:
• Be able to login using a local ThinLinc client:
• Be able to login using a local ThinLinc client and an SSH client: Richel
• Be able to login using a local ThinLinc client and an SSH client and be able to navigate the filesystem under Linux: Richel

[bclaremar]

In other words:
They should have an account and a project already

Voting for bullet 4

• but showing specifically how to use path when transferring in shell

[richelbilderbeek]

So 'Be able to login using a local ThinLinc client and an SSH client and be able to navigate the filesystem under Linux' it is...

... would I understand the addition of 'but showing specifically how to use path when transferring in shell': I feel this is related to the course content, not to the prerequisite.

Is the prerequisite

Be able to login using a local ThinLinc client and an SSH client and be able to navigate the filesystem under Linux

or is there another text to use?

[richelbilderbeek]

I've added these preliminary prereqs to the README, we'll modify it based on your reply to the post above 👍

[bclaremar]

shit

Log in is part of course (sorry I missed your interpretation in the beginning of this issue)
But sure, they are supposed to connect when getting password so this step is done.

• I could add that in the prereqs that it is a natural step of the getting account.

Still I believe it should be a small part of the workshop. Repeating this so they feel comfortable. See #13

[bclaremar]

Suggestion:

Prereqs:

• User account on a Swedish academic HPC cluster
  • (you will get one if you lack one)
• Be able to log in in one way (instructions when you get an account)
• Be able to navigate the filesystem under Linux

[bclaremar]

example linux material: https://uppmax.github.io/uppmax_intro_day_1/sessions/use_terminal/ and exercise 1-3

[richelbilderbeek]

Log in is part of course (sorry I missed your interpretation in the beginning of this issue)

AFAICS, this is incorrect. We decided that learners should be able to login (see below a copy-paste of the prereqs).

• Be able to login to your cluster's remote desktop environment, using either a website or a local ThinLinc client
• Be able to login using an SSH client
• Be able to navigate the filesystem under Linux

Or is this a demand of the NAISS training coordinator?

If this is a demand, I mostly agree with the prereqs you posted (copy-pasted below):

• User account on a Swedish academic HPC cluster (you will get one if you lack one)
• Be able to log in in one way (instructions when you get an account)
• Be able to navigate the filesystem under Linux

I suggest to slight change it to:

• User account on a Swedish academic HPC cluster [RJCB: no, they need to have done this]
• Be able to log in (in at least one way), as instructed by you HPC center
• Be able to navigate the filesystem under Linux

If the training coordinator demands we spend an hour on login, sure, we'll do less transfer methods :-)

[bclaremar]

I am leaning more towards your opinion also after talking to Diana, but I try to get the opinion from J.
So far:
J: "I thought that connect and transfer goes together, since for most things I do (scp, cyberduck) I need a working ssh connection."
B: "But connection can equally well be in prereqs is our argument (included would also be "Be able to navigate the filesystem under Linux" (there is good online material))"

[bclaremar]

Also from J and how we have done it so far:

" anyone who has control of a student of staff email at a Swedish higher education institution is clearly welcome to attend."

Therefore, those with no compute project yet should get an account to a course project on Tetralith or Dardel