You will require an NCI login account to use a virtual desktop. If you don’t already have one then you can register here: https://my.nci.org.au/mancini/.
User home directories. Mounted across all desktop nodes. Backed up to an archival system. Disk usage quotas apply. Good place for source code.
Don’t use this location for high demand I/O workloads as performance will be poor and will impact on all other users.
The following folders in the “Places” desktop menu are included:
Note that “/home” on “raijin” is completely separate and cannot be accessed from the desktops.
The global Lustre filesystem which is also available on “raijin”. Only a subset of volumes are accessible so please ask if you would like your project area to be made available. Primarily intended for persistent data outputs and shared software installations. More information can be found here: http://nci.org.au/services-support/getting-help/gdata-faqs/Files and Filesystems
Fast storage on the local node primarily intended for intermediate working files. Neither persistent nor backed up. Each user’s temporary directory (“$TMPDIR”) is set to this location. Does not involve any network traffic and is backed by an SSD on the node. Please take care not to fill up this volume as it will impact other users on the same node; currently we aren’t applying quotas but may do so in future.
Note that “/short” on “raijin” is completely separate to the VDI and cannot be accessed from the desktops.
We recommend using either “/g/data” or “/local” (whichever is appropriate) instead of this area as it’s currently under consideration to be removed. No new project allocations are being made here. If you have a specific need for this storage please contact us to discuss your requirements.
Not backed up and not guaranteed to be persistent. Unlike “/local”, this area is shared amongst all desktop nodes so you can exchange temporary working data with other colleagues if needed. However, each project area is limited to 100GB and files will be purged automatically after 30 days.
Don’t use this location for high demand I/O workloads as performance will be poor and will impact on all other users. For better performance you should use “/local” instead.
The “module” command is available for loading additional software packages into the command line environment. For more information see: http://nci.org.au/services-support/getting-help/environment-modules/Environment Modules
When loading modules where the version used matters (eg. scripts), it’s recommended that you explicitly state which version of each module to load. This will help avoid unexpected surprises if the default version changes when a new version of the module is deployed in future.