Closing remarks - PDF file

1. Getting access to computational resources

There are two main ways of using IMAS environment in preinstalled environment

2. Connecting to remote machines

In both cases (Gateway/ITER) you can use one of two methods to get into machine: SSH or NoMachine - you can download NoMachine client here: https://www.nomachine.com

3. Setting up environment

Before you can compile, link and run IMAS based code you have to make sure to setup IMAS environment inside your current session - be it NoMachine or SHH.

module load imasenv

module load IMAS

dd_doc

dd_doc

4. Working with source code

ACH/TSVV collaboration requires means of sharing source code. ACH will provide EUROfusion based source control system based on Gitlab. In case you need to host your software using ITER Computing Cluster it is also possible (however we encourage to store/mirror repositories inside Gateway GitLab installation).

There are two servers that provide access to IMAS and ACH related repositories.

5. Submitting bugs and issues

In case you need to submit a bug/issue we suggest following general good practices of bug reporting. It means, your bug should allow to easily reproduce and check the issue. Typically, bug reports that say: "SMTH doesn't work" do not lead to quick resolution of the problem. This is why we have prepared few points that make life of both sides (reporter and assignee) a little bit easier:

Reporting a bug in "proper" way can greatly reduce response time. It also helps to understand the issue better and locate it faster.
To make it easier (to locate the bug) consider providing following information:
  - IMAS version
  - Data Dictionary version
  - Location of application, source code, means of building and running the code
  - Source codes and Makefile
  - Link to any documentation that allows to get familiar with the code
  - Your environment settings (preferably, script that sets up the environment exactly the same way you have it set)
  - Your environment variable ([shell]> env > ~/my_environment_while_spotting_the_bug)
  - Your current module list  ([shell]> module list > ~/my_module_list_while_sporring_the_bug)

Once you have everything in place, there are two trackers where you can submit bugs/issues