To run a Rose/Cylc suite at NCI, you need to be a member of the following project hr22.

The hr22 project maintains the cylc module that provides executables such as rose, cylc and fcm, as well as Rose and Cylc global configurations tested at NCI. 

To run workflows prepared for the access and related projects, you need to be a member of the following projects

  • access
  • <compute project>

The  access project maintains modules such as ecccodes, that required by the suite.

The <compute project> supports the ARE VDI session with compute and storage allocation. To query its compute grant and storage quota details, follow the example below. 

$ nci_account -P om02  

Usage Report: Project=om02 Period=2023.q1
=============================================================
    Grant:    50.00 KSU
     Used:     3.17 KSU
 Reserved:    20.00 SU 
    Avail:    46.81 KSU
    

Storage Usage Report: Project=om02
=============================================================
Filesystem        Used     iUsed    Allocation    iAllocation    
gdata5       76.19 GiB   52.11 K      5.00 TiB       599.00 K        
scratch1     15.39 GiB   30.32 K     10.00 TiB         1.02 M        
=============================================================

In the example we have used om02 as the project, replace it with your own project code to see how much compute and storage allocation you get access to through the project. 

If any of the  projects mentioned above is missing from your list, join the project through my.nci.org.au and wait for 30 minutes after the approval to allow the new membership to be updated across all servers.

To look up your project memberships, try either of the following two methods

  1. Login to my.nci.org.au and click Home on the left panel, a summary of project and membership shows in the main panel. An example for user jpf777 is shown below.
  2. In a login shell either on a Gadi login node or within an ARE VDI session, run the groups command to print the list of your memberships. The example below highlights hr22 and ki32 in the membership list.

           $ groups | grep "hr22\|ki32"

           access bx82 dk92 dx2 fp0 hh5 hr22 ki32 ki32_mosrs ki32_nemo om02 pp66 up99 wb00

  • No labels