Update tutorials

[tkoskela]

I've added the ReFrame tutorial and fixed the most obvious formatting issues from hackmd. I've also added separate tutorials for getting started, postprocessing and profiling, based on the materials for CIUK.

There are a few rough edges and some of the Cosma output tabs are missing, but I think I'm mostly happy with the content.

You can preview the website by clicking on the details of the publish action

[tkoskela]

I think I addressed your comments, thanks for those!

This is maybe a bit too much of a lecture notes format. I think I need to go through it and write some more prose

[ilectra]

This list appears as continuous text, probably because it's inside a comment.

[nicolin]

Installation section: Following on from creating the virtual env and cloning /installing the tests. It should be made clear that if the next step installing spack and reframe is done inside the virtual env or outside it. The reason is that when you go to the next page on a new system it says "spack env create --without-view -d /path/to/environment" . However based on the previous instruction spack is installed in the virtual env that the excalibur-tests were put in.

Reframe: Running the benchmark cases, it would be expected to have it create all IO in a defined folder, providing the -o MyBenchCasesA only puts a subset of files in there with a default/default/default folder structure. Either clarity should be given directly on this page as to the folders and structure created or point to a Reframe man page if this is a standard structure.

This is based me as a first time user of spack and Reframe: Use case that I normally do either for different systems or different configs eg GPUA GPUB on the same system is that what to have all the results in one folder so MyBenchCasesA MyBenchCasesB etc in a portable manner.

[nicolin]

more on this later. put a link to the section rather

[tkoskela]

There's a link to the documentation in the section above this one

[nicolin]

nsys can be run in nvprof mode to provide CLI output not just the GUI. Maybe useful to include this also ?

[tkoskela]

Thanks! I created #358 for this

[nicolin]

Added comments on a first glace read. Will do an actual run in the coming days.

[tkoskela]

Installation section: Following on from creating the virtual env and cloning /installing the tests. It should be made clear that if the next step installing spack and reframe is done inside the virtual env or outside it. The reason is that when you go to the next page on a new system it says "spack env create --without-view -d /path/to/environment" . However based on the previous instruction spack is installed in the virtual env that the excalibur-tests were put in.

I added more detail on this in the installation and setup sections of the documentation. Is it clear now?

Reframe: Running the benchmark cases, it would be expected to have it create all IO in a defined folder, providing the -o MyBenchCasesA only puts a subset of files in there with a default/default/default folder structure. Either clarity should be given directly on this page as to the folders and structure created or point to a Reframe man page if this is a standard structure.

This is based me as a first time user of spack and Reframe: Use case that I normally do either for different systems or different configs eg GPUA GPUB on the same system is that what to have all the results in one folder so MyBenchCasesA MyBenchCasesB etc in a portable manner.

Upon reading a bit of ReFrame documentation I found the flag that does this. It is --prefix, not --outputdir 🙃 I've updated this in the documentation.