{{Cluster Status
| cluster = ARC
| status = green
| title = Cluster operational
| message = Data center move is in progress. Currently, the compute nodes in cpu2019, cpu2021, cpu2022, gpu-v100, gpu-a100, and most nodes from bigmem will be unavailable

See the [[ARC Cluster Status]] page for system notices.
}}

Template:ARC Cluster Status

2024-10-04T22:27:22Z

Lleung:

{{Cluster Status
| cluster = ARC
| status = yellow
| title = Cluster partly unavailable
| message = Data center move is in progress. Currently, the compute nodes in cpu2019, cpu2021, cpu2022, gpu-v100, gpu-a100, and most nodes from bigmem will be unavailable

See the [[ARC Cluster Status]] page for system notices.
}}

Template:ARC Cluster Status

2024-10-04T22:27:11Z

Lleung:

ARC Cluster Status

2024-10-04T22:26:13Z

2024-09-25T20:40:13Z

Lleung:

{{ARC Cluster Status}}

== System Messages ==
{{Message of the day item
| title = January System Updates
| date = 2023/01/01
| message =
Beginning January 16, 2023, the ARC cluster will undergo operating system updates. We shall do our utmost to minimize disruption and allow ongoing jobs to be completed. New jobs may be temporarily held from scheduling.

The ARC login node will reboot on the morning of January 16. Please save your work and log out if possible.

The upgrade is planned to be fully complete by January 20.

If you encounter any system issues, do not hesitate to let us know.

Thank you for your cooperation.
}}

{{Message of the day item
| title = System Updates Completed
| date = 2023/01/24
| message =
The upgrade has been completed. The following has been changed:
* OS Updated to Rocky Linux 8.7
* Slurm updated to 22.05.7
* Apptainer replaces Singularity
* Each job will have its own /tmp, /dev/shm, /run/user/$uid mounted

If you encounter any system issues, do not hesitate to let us know.

Thank you for your cooperation.
}}

{{Message of the day item
| title = Filesystem Issues
| date = 2023/02/28
| message =
We are currently investigating a filesystem issue that is causing filesystem slowdowns across ARC.

We will update you with more information as it becomes available.

Thank you for your patience.
}}

{{Message of the day item
| title = Filesystem Issues
| date = 2023/03/1
| message =
We are still currently investigating a filesystem issue that is causing filesystem slowdowns across ARC. Some jobs on ARC have been paused to help us find the root cause of the slowdowns.

We will update you with more information as it becomes available.

Thank you for your patience.
}}

{{Message of the day item
| title = ARC Login node reboot
| date = 2023/03/2
| message =
The ARC login node will be rebooted this afternoon for an emergency maintenance. This downtime is needed to help mitigate the filesystem slowdowns experienced on the login node. Jobs will continue running and scheduling during this time.

All logins to the ARC login node will be terminated at 3:00PM and will remain unavailable until 4:00PM.

We apologize for the inconvenience and thank you for your patience.
}}

{{Message of the day item
| title = ⚠️ Filesystem Issues
| date = 2023/03/2
| message =
We are still currently investigating a filesystem issue that is causing filesystem slowdowns on specific nodes in our MSRDC location.

We will update you with more information as it becomes available.

We apologize for the inconvenience and thank you for your patience.
}}

{{Message of the day item
| title = Filesystem Issues Resolved
| date = 2023/03/10
| message =
We have upgraded the filesystem routers in our MSRDC location to address the performance issues.

Please let us know if you experience any issues with the filesystem performance.

Thank-you for your patience.
}}

{{Message of the day item
| title = Open OnDemand reboot
| date = 2023/05/01
| message =
On May 1, 2023, the ARC Open OnDemand node will be rebooted between 5PM and 6PM. Expected downtime will be approximately 15 minutes.

If you encounter any system issues, do not hesitate to let us know.

Thank you for your cooperation.
}}

{{Message of the day item
| title = Apptainer (Singularity) on ARC Login Node
| date = 2023/06/22
| message =
Apptainer (Singularity) containers may experience an error when
running on the Arc login node. If apptainer complains that a system
administrator needs to enable user namespaces, simply run your
containers inside a job.

This is a temporary measure due to security vulnerability that will be
patched soon.

}}

{{Message of the day item
| title = Lattice, Single, cpu2013 partition changes
| date = 2023/07/13
| message =
The Lattice and Single, and cpu2013 have all been decomissioned. The Single
partition will be replaced by the nodes formerly in the cpu2013 partition but
will be called single.

}}

{{Message of the day item
| title = Open OnDemand reboot
| date = 2023/10/17
| message =
Open OnDemand will be rebooted on October 17, 2023 for an update. It will be down for up to 30 minutes.

}}

{{Message of the day item
| title = Storage Upgrade MARC/ARC cluster
| date = 2023/10/23
| message =
We will be performing storage upgrades on the MARC/ARC cluster on
November 16 and 17, 2023. To facilitate this, we will be throttling
down the number of jobs on both clusters while the upgrades are
performed
}}

{{Message of the day item
| title = Systems Operating Normally
| date = 2024/05/3
| message =
}}

{{Message of the day item
| title = Power Interruption
| date = 2024/05/07
| message = Arc Experienced an brief power outage around 11AM May 7, 2024.
Most compute nodes have or are rebooting. Most jobs running at this time
were lost. Arc administrators are actively working on restarting compute
nodes. Sorry for the inconvenience.
}}

{{Message of the day item
| title = GPU a100 Node Reservation
| date = 2024/06/03
| message = Job submissions targeted to the GPU a100 partition will be
affected by a temporary reservation on the nodes to accommodate the RCS
summer school class taking place on 2024/Jun/10. Reservation will end
shortly after. Please submit your jobs normally and the scheduler will
start them as soon as the nodes are available. Sorry for the inconvenience.
}}

{{Message of the day item
| title = GPU a100 Node Reservation Removed
| date = 2024/06/11
| message = GPU a100 Nodes in ARC have been returned to normal scheduling.
}}

{{Message of the day item
| title = Notice of Upcoming Partial Outage
| date = 2024/08/23
| message = Several compute nodes from the ARC cluster will be unavailable
between Sept 23 to Sept 27 inclusive (subject to change). All compute nodes
in cpu2019, cpu2021/2, gpu-v100 most nodes from bigmem and gpu-a100 will be
affected. These nodes will return to service as soon as the work is complete.
}}

{{Message of the day item
| title = Partial Outage Update I
| date = 2024/08/25
| message = Due to hardware issues that is blocking our original maintenance window, most compute nodes that were taken offline on Monday has been brought back online today. An additional partial outage will occur again starting next Tuesday for the same nodes.

On Tuesday, October 1, 2024, the compute nodes in cpu2019, cpu2021, cpu2022, gpu-v100, gpu-a100, and most nodes from bigmem will be unavailable until Friday October 4, 2024.

We apologise for the inconvenience.
}}

{{Navbox ARC}}
[[Category:ARC]]

Think Login Node Status

2024-09-25T20:26:02Z

Lleung:

Altis Login Node Status

2024-09-25T20:25:48Z

Lleung:

TALC Cluster

2024-09-23T22:28:04Z

Lleung: Lleung moved page TALC Cluster to TALC Cluster Guide over redirect

#REDIRECT [[TALC Cluster Guide]]

TALC Cluster Guide

2024-09-23T22:28:04Z

Lleung: Lleung moved page TALC Cluster to TALC Cluster Guide over redirect

{{TALC Cluster Status}}{{Message Box
|icon=Security Icon.png
|title=Cybersecurity awareness at the U of C
|message=Please note that there are typically about 950 phishing attempts targeting University of Calgary accounts each month. This is just a reminder to be careful about computer security issues, both at home and at the University. Please visit https://it.ucalgary.ca/it-security for more information, tips on secure computing, and how to report suspected security problems.}}

This guide gives an overview of the Teaching and Learning Cluster (TALC) at the University of Calgary and is intended to be read by new account holders getting started on TALC. This guide covers topics as the hardware and performance characteristics, available software, usage policies and how to log in and run jobs.

==Introduction==
TALC is a cluster of computers created by Research Computing Services (RCS) in response to requests for a central computing resource to support academic courses and workshops offered at the University of Calgary. It is a complement to the Advanced Research Computing (ARC) cluster that is used for research, rather than educational purposes. The software environment in the TALC and ARC clusters is very similar and workflows between the two clusters are identical. What students learn about using TALC will have direct applicability to using ARC should they go on to use ARC for research work.

If you are the instructor for a course that could benefit from using TALC, please review this guide and the [[TALC Terms of Use]] and then contact us at support@hpc.ucalgary.ca to discuss your requirements.

Please note that in order to ensure that the appropriate software is available, student accounts are in place, and appropriate training has been provided for your teaching assistants, it is best to start this discussion several months prior to the start of the course.

If you are a student in a course using TALC, please review this guide for basic instructions in using the cluster. Questions should first be directed to the teaching assistants or instructor for your course.

===Obtaining an account===
TALC account requests are expected to be submitted by the course instructor rather than from individual students. You must have a University of Calgary IT account in order to use TALC. If you do not have a University of IT account or email address, please register for one at https://itregport.ucalgary.ca/. In order to ensure TALC is provisioned in time for a course start date, the instructor should submit the initial list of @ucalgary.ca accounts needed for the course 2 weeks before the start date.

User accounts for classes will exist for the duration of the semester they are being taught, and are deleted along with the data in the home directories when the semester ends. You must ensure you save anything you want to access later saved elsewhere before these dates. We do not keep backups of data on TALC.

For the upcoming academic calendar, accounts will be deleted on the following dates:

Spring: 23 June 2023

Summer: 25 Aug 2023

Fall: 22 Dec 2023

Winter: 30 Apr 2024

=== Getting Support ===
{{Message Box
|title=Need Help or have other TALC Related Questions?
|message='''Students''', please send TALC-related questions to your course instructor or teaching assistants.<br />
'''Course instructors and TAs''', please report system issues to support@hpc.ucalgary.ca.
|icon=Support Icon.png}}

==Hardware==
The TALC cluster is comprised of repurposed research clusters that are a few generations old. As a result, individual processor performance will not be comparable to the latest processors but should be sufficient for educational purposes and course work.
{| class="wikitable"
!Partition
!Description
!Nodes
!CPU Cores, Model, and Year
!Installed Memory
!GPU
!Network
|-
|gpu
|GPU Compute
|3
|12 cores, 2x Intel Xeon Bronze 3204 CPU @ 1.90GHz (2019)
|192 GB
|5x NVIDIA Corporation TU104GL [Tesla T4]
|40 Gbit/s InfiniBand
|-
|cpu16
|General Purpose Compute
|36
|16 cores, 2x Eight-Core Intel Xeon CPU E5-2650 @ 2.00GHz (2012)
|64 GB
|N/A
|40 Gbit/s InfiniBand
|-
|bigmem
|General Purpose Compute
|2
|32 cores, 4x Intel(R) Xeon(R) CPU E7- 4830 @ 2.13GHz (2015)
|1024 GB
|N/A
|40 Gbit/s InfiniBand
|}

===Storage===
{{Message Box
| title=No Backup Policy!
| message=You are responsible for your own backups. Since accounts on TALC and related data are removed shortly after the associated course has finished, you should download anything you need to save to your own computer before the end of the course.
}}

TALC is connected to a network disk storage system. This storage is split across the <code>/home</code> and <code>/scratch</code> file systems.
====<code>/home</code>: Home file system====
Each user has a directory under /home and is the default working directory when logging in to TALC. Each home directory has a per-user quota of 500 GB. This limit is fixed and cannot be increased.

Note on file sharing: Due to security concerns, permissions set using <code>chmod</code> on your home directory to allow other users to read/write to your home directory will be automatically reverted by an automated system process unless an explicit exception is made. If you need to share files with others on the TALC cluster, please write to support@hpc.ucalgary.ca to ask for such an exception.

====<code>/scratch</code>: Scratch file system for large job-oriented storage====
Associated with each job, under the <code>/scratch</code> directory, a subdirectory is created that can be referenced in job scripts as <code>/scratch/${SLURM_JOB_ID}</code>. You can use that directory for temporary files needed during the course of a job. Up to 30 TB of storage may be used, per user (total for all your jobs) in the <code>/scratch</code> file system.

Data in <code>/scratch</code> associated with a given job will be deleted automatically, without exception, five days after the job finishes.

== Software ==
{{Message Box
| title=Software Package Requests
| message=Course instructors or teaching assistants should write to support@hpc.ucalgary.ca if additional software is required for their course.
}}

All TALC nodes run a version of Rocky Linux. For your convenience, we have packaged commonly used software packages and dependencies as modules available under <code>/global/software</code>. If your software package is not available as a module, you may also try Anaconda which allows users to manage and install custom packages in an isolated environment.

For a list of available packages that have been made available, please see [[ARC Software pages]].

=== Modules ===
The setup of the environment for using some of the installed software is through the <code>module</code> command.

Software packages bundled as a module will be available under <code>/global/software</code> and can be listed with the <code>module avail</code> command.
<syntaxhighlight lang="bash">
$ module avail
</syntaxhighlight>

To enable Python, load the Python module by running:
<syntaxhighlight lang="bash">
$ module load python/anaconda-3.6-5.1.0
</syntaxhighlight>

To unload the Python module, run:
<syntaxhighlight lang="bash">
$ module remove python/anaconda-3.6-5.1.0
</syntaxhighlight>

To see currently loaded modules, run:
<syntaxhighlight lang="bash">
$ module list
</syntaxhighlight>

==Using TALC==
{{Message Box
|title=Usage subject to [[TALC Terms of Use]]
|message=Please review the [[TALC Terms of Use]] prior to using TALC.
|icon=Support Icon.png}}

===Logging in===
To log in to TALC, connect using SSH to talc.ucalgary.ca. Connections to TALC are accepted only from the University of Calgary network (on campus) or through the University of Calgary General VPN (off campus).

When logging into a new TALC account for '''the first time''' the new user has to agree to the '''conditions of use''' for TALC.
Until the conditions are accepted the account is not active.

See [[Connecting to RCS HPC Systems]] for more information.

===Working interactively===

TALC uses the Linux operating system. The program that responds to your typed commands and allows you to run other programs is called the Linux shell. There are several different shells available, but, by default you will use one called bash. It is useful to have some knowledge of the shell and a variety of other command-line programs that you can use to manipulate files. If you are new to Linux systems, we recommend that you work through one of the many online tutorials that are available, such as the [http://www.ee.surrey.ac.uk/Teaching/Unix/index.html UNIX Tutorial for Beginners (external link)] provided by the University of Surrey. The tutorial covers such fundamental topics, among others, as creating, renaming and deleting files and directories, how to produce a listing of your files and how to tell how much disk space you are using. For a more comprehensive introduction to Linux, see [http://linuxcommand.sourceforge.net/tlcl.php The Linux Command Line (external link)].

The TALC login node may be used for such tasks as editing files, compiling programs and running short tests while developing programs. CPU intensive workloads on the login node should be restricted to under 15 minutes as per [[General Cluster Guidelines and Policies|our cluster guidelines]]. For interactive workloads exceeding 15 minutes, use the '''[[Running_jobs#Interactive_jobs|salloc command]]''' to allocate an interactive session on a compute node.

The default <code>salloc</code> allocation is 1 CPU and 1 GB of memory. Adjust this by specifying <code>-n CPU#</code> and <code>--mem Megabytes</code>. You may request up to 5 hours of CPU time for interactive jobs.
salloc --time 5:00:00 --partition cpu16

===Running non-interactive jobs (batch processing)===
Production runs and longer test runs should be submitted as (non-interactive) batch jobs, in which commands to be executed are listed in a script (text file). Batch jobs scripts are submitted using the <code>sbatch</code> command, part of the Slurm job management and scheduling software. #SBATCH directive lines at the beginning of the script are used to specify the resources needed for the job (cores, memory, run time limit and any specialized hardware needed).

Most of the information on the Running Jobs page on the Compute Canada web site is also relevant for submitting and managing batch jobs and reserving processors for interactive work on TALC. One major difference between running jobs on the TALC and Compute Canada clusters is in selecting the type of hardware that should be used for a job. On TALC, you choose the hardware to use primarily by specifying a partition, as described below.

===Using JupyterHub on Talc===
TALC has a Jupyterhub server which runs a Jupyter server on one of the TALC compute nodes and provides all the necessary encryption and plumbing to deliver the notebook to your computer. To access this service you must have a TALC account. Point your browser at http://talc.ucalgary.ca and login with your usual UC account. As of this writing, the job that runs the jupyter notebook is 1 cpu and 10GiB of memory on a cpu16 node.

'''Please note''' that before using the Jupyterhub on TALC a new user has to login into his/her TALC account using SSH at least once to '''accept the conditions of TALC use'''.
Until the conditions are accepted the account is not activated and the Jupyterhub login will not work either.

===Selecting a partition===
TALC currently has the following partitions available for use. The <code>gpu</code> and <code>cpu12</code> partitions are refer to the same nodes. The <code>cpu12</code> partition was created to only expose the CPUs on the GPU hardware for general purpose use. Each GPU node has 5 Tesla T4 GPUs installed, but you may only request one per job within the TALC environment.
{| class="wikitable"
!Partition
!Description
!Nodes
!Cores
!Memory
!Memory Request Limit
!Time Limit
!GPU Request per Job
!Network
|-
|gpu
|GPU Compute
|3
|12 cores
|192 GB
|190 GB
|24 hours
|1x NVIDIA Corporation TU104GL [Tesla T4]
|40 Gbit/s InfiniBand
|-
|cpu12
|General Purpose Compute
|3
|12 cores
|192 GB
|190 GB
|24 hours
|None
|40 Gbit/s InfiniBand
|-
|cpu16
|General Purpose Compute
|36
|16 cores
|64 GB
|62 GB
|24 hours
|None
|40 Gbit/s InfiniBand
|-
|bigmem
|General Purpose Compute
|2
|32 cores
|1024 GB
|1022 GB
|24 hours
|None
|40 Gbit/s InfiniBand
|}
There are some aspects to consider when selecting a partition including:
* Resource requirements in terms of memory and CPU cores
* Hardware specific requirements, such as GPU or CPU Instruction Set Extensions
* Partition resource limits and potential wait time
* Software support for parallel processing using Message Passing Interface (MPI), OpenMP, etc. For example, MPI for parallel processing can distribute memory across multiple nodes, so that per-node memory requirements could be lower. Whereas OpenMP or single process serial code that is restricted to one node would require a higher memory node.

Since resources that are requested are reserved for your job, please request only as much CPU and memory as your job requires to avoid reducing the cluster efficiency. If you are unsure which partition to use or the specific resource requests that are appropriate for your jobs, '''Course instructors and TAs''' may contact us at [mailto:support@hpc.ucalgary.ca support@hpc.ucalgary.ca] and we would be happy to work with you.

=== Using a partition ===

==== CPU only jobs ====
To select the <code>cpu16</code> partition, include the following line in your batch job script:<syntaxhighlight lang="text">
#SBATCH --partition=cpu16
</syntaxhighlight>You may also start an interactive session with <code>salloc</code>:<syntaxhighlight lang="text">
$ salloc --time 1:00:00 -p cpu16
</syntaxhighlight>

==== GPU jobs ====
In TALC, you are limited to exactly 1 GPU per job. Jobs that request for 0 GPUs or 2 or more GPUs will not be scheduled.

To submit a job using the <code>gpu</code> partition with one GPU request, include the following to your batch job script:<syntaxhighlight lang="text">
#SBATCH --partition=gpu
#SBATCH --gpus-per-node=1
</syntaxhighlight>

Like the previous example, you may also request interactive sessions with GPU nodes using <code>salloc</code>. Just specify the <code>gpu</code> partition and the number of GPUs required. <syntaxhighlight lang="text">
$ salloc --time 1:00:00 -p gpu -n 1 --gpus-per-node 1
</syntaxhighlight>You may verify that a GPU was assigned to your job or interactive session by running <code>nvidia-smi</code>. This command will show you the status of the GPU that was assigned to you.<syntaxhighlight lang="text">
$ nvidia-smi
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 450.80.02 Driver Version: 450.80.02 CUDA Version: 11.0 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|===============================+======================+======================|
| 0 Tesla T4 Off | 00000000:3B:00.0 Off | 0 |
| N/A 36C P0 14W / 70W | 0MiB / 15109MiB | 5% Default |
| | | N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=============================================================================|
| No running processes found |
+-----------------------------------------------------------------------------+
</syntaxhighlight>

==== Partition limitations ====
In addition to the hardware limitations of the nodes within the partition, please be aware that there may also be policy limits imposed on your account for each partition. These limits restrict the number of cores, nodes, or GPUs that can be used at any given time. Since the limits are applied on a partition-by-partition basis, using resources in one partition should not affect the available resources you can use in another partition.

These limits can be listed by running:
<syntaxhighlight lang="bash">
$ sacctmgr show qos format=Name,MaxWall,MaxTRESPU%20,MaxSubmitJobs
Name MaxWall MaxTRESPU MaxSubmit
---------- ----------- -------------------- ---------
normal 1-00:00:00
cpulimit cpu=48
gpucpulim+ cpu=18
gpulimit cpu=2,gres/gpu=1
</syntaxhighlight>

=== Time limits ===
Use the <code>--time</code> directive to tell the job scheduler the maximum time that your job might run. For example:
#SBATCH --time=hh:mm:ss

You can use <code>scontrol show partitions</code> or <code>sinfo</code> to see the current maximum time that a job can run.
<syntaxhighlight lang="bash" highlight="6">
$ scontrol show partitions
PartitionName=cpu16
AllowGroups=ALL AllowAccounts=ALL AllowQos=ALL
AllocNodes=ALL Default=YES QoS=cpulimit
DefaultTime=NONE DisableRootJobs=NO ExclusiveUser=NO GraceTime=0 Hidden=NO
MaxNodes=UNLIMITED MaxTime=1-00:00:00 MinNodes=0 LLN=NO MaxCPUsPerNode=UNLIMITED
Nodes=n[1-36]
PriorityJobFactor=1 PriorityTier=1 RootOnly=NO ReqResv=NO OverSubscribe=NO
OverTimeLimit=NONE PreemptMode=OFF
State=UP TotalCPUs=576 TotalNodes=36 SelectTypeParameters=NONE
JobDefaults=(null)
DefMemPerNode=UNLIMITED MaxMemPerNode=UNLIMITED

</syntaxhighlight>

Alternatively, with <code>sinfo</code> under the <code>TIMELIMIT</code> column:
<syntaxhighlight lang="bash">
$ sinfo
PARTITION AVAIL TIMELIMIT NODES STATE NODELIST
cpu12 up 1-00:00:00 3 idle t[1-3]
cpu16 up 1-00:00:00 36 idle n[1-36]
bigmem up 1-00:00:00 2 idle bigmem[1-2]
gpu up 1-00:00:00 3 idle t[1-3]

...
</syntaxhighlight>
[[Category:TALC]]
[[Category:Guides]]
{{Navbox TALC}}

Altis Login Node Status

2024-09-03T21:26:15Z

Lleung: Created page with "{{ARC Cluster Status}} == System Messages == {{Message of the day item | title = Systems Operating Normally | date = 2024/09/03 | message = The ARC Cluster and the Altis login node is operational. No upcoming upgrades are planned. }} Category:ARC {{Navbox ARC}}"

Template:ARC Cluster Status

2024-09-03T21:19:06Z

Lleung:

{{Cluster Status
| cluster = ARC
| status = green
| title = Cluster operational
| message = System is operational. No updates are planned.

See the [[ARC Cluster Status]] page for system notices.
}}

2024-08-13T16:43:38Z

Lleung: Lleung moved page MARC accounts to How to get a MARC account

This page describes the process of obtaining an account and how to login to the Marc Cluster. If you are looking for information about the MARC cluster hardware, please see the [[Marc_Cluster_Guide]].

= Obtaining an Account =
== Prerequisites ==
* Access will only be granted to MARC for those with project shares on SCDS as this is the only to get data into MARC.
* Users must have a UC domain IT account, and an HR relationship type of Staff, Faculty, Student, General Associate or General Associate - Research collaborator.
* If you wish to add a new person to MARC or SCDS, and they do not appear in the ServiceNow person picker, this may be because the new account has not completed provisioning in ServiceNow, or their HR relationship type might not be in the categories above. Please contact HR for assistance with adjusting your collaborator's HR relationship type. Changes in HR-> Peoplesoft can take some time to complete and propagate to ServiceNow. Please contact it@ucalgary.ca for assistance with ServiceNow.

== Procedure ==
# Navigate to the IT Homepage: www.ucalgary.ca/it
# Click Login in the upper right corner
# Click "Order Something"
# Click "Research Computing"
# Click "Medical Advanced Research Computing (MARC)"
# Select "Add Access" from the "What would you like to do?" box
# Choose your SCDS share from the next box
# Type a synopsis of the work you plan to do into the "Business Reason" box.
# You may leave the Additional Information box empty
# Someone should reply to you when your account is ready.

= Logging in to MARC =
== Prerequisites ==
# You will need a Microsoft Authenticator second factor to access Marc. This is the same Microsoft Authenticator that is used with an Office 365 account.
# VPN is NOT required but is acceptable when accessing Marc.

== Procedure ==
=== Login to myappmf ===
# Point your browser to https://myappmf.ucalgary.ca [[File:RdhLoginScreen.png|thumb|center|Image of the myappmf.ucalgary.ca login screen.]]
# This will bring up the familiar login portal that is used in many other UofC apps. Enter your User Name. Use your UC domain credentials without the UC\ in front. (eg. jsmith)
# Enter your usual UC password.
# Click the Sign In button.
# A Microsoft authenticator request will be sent to your chosen second factor device. This is the same as an Office 365 login. Accept the authentication.

=== Add Applications ===
# Once you have logged into myappmf click Apps at the top
# Click the Putty icon to start Putty [[File:RdhAddPutty.png|thumb|center]]

=== Login to Marc with Putty ===
# Once Putty starts you will see the PuTTY Configuration screen: [[File:RdhPuttyConfiguration.png|thumb|center]]
# Enter "marc.ucalgary.ca" in the "Host Name" box
# If you want this to be default, click "Default Settings" then click the Save button beside it.
# Click Open. You will be presented with a black terminal screen prompting for your UC username and password.[[File:RdhPuttyLogin.PNG|thumb|center]]
# The contents of the screen will look something like this:
<PRE>
login as: myusername
myusername@marc.ucalgary.ca's password:
Last login: Thu Apr 9 13:12:21 2020
===========================================================================
___________________________________
_ _ __ ____ __
/ /| / | / ) / )
---/| /-|---/__|---/___ /---/------
/ |/ | / | / | /
_/__/___|_/____|_/_____|__(____/___
marc.ucalgary.ca
Problems or deficiencies? Send email to:
support@hpc.ucalgary.ca

===========================================================================

SYSTEM NOTICES:
[myusername@marc ~]$

</PRE>
Now you may return to the [[Marc Cluster Guide]] page

[[Category:MARC]]
[[Category:Guides]]

How to get an account

2024-08-13T16:42:24Z

Lleung:

All eligible University of Calgary Researchers may request for a HPC account. Visiting or external collaborators must first obtain a General Associate account before they are eligible for a HPC account. Undergraduates must be confirmed by their research supervisor. In all cases, the applicant must must have an '''active UCalgary IT account''' to be able to get access to our HPC systems.

This process is only for production Level 1/2 HPC systems.

* For teaching/learning applications and for undergraduates who need an account on TALC, please visit [[TALC Cluster|Teaching And Learning Cluster (TALC)]] for more information.
* For Level 3/4 (high-security) HPC applications, please apply for a [[MARC accounts|MARC]] account instead.

Please refer to the following table for next steps:
{| class="wikitable"
|-
! style="text-align: left;" |I am a University of Calgary researcher or graduate student
|All University of Calgary researchers, including graduate students, can directly request an account on the ARC cluster.
'''Next steps''': Please email the completed application form to support@hpc.ucalgary.ca.
|-
! style="text-align: left;" | I am not a University of Calgary researcher
|If you are not University of Calgary researcher and have collaboration work that required access to the ARC cluster, you must first obtain the status of the [[External collaborators |'''General Associate''']] with the University in order to obtain a UCalgary email account. You may apply for an ARC account only after obtaining your University of Calgary IT and Email account.
'''Next steps''': Obtain a [[External collaborators |'''General Associate''']], then email the completed application form to support@hpc.ucalgary.ca.
|-
! style="text-align: left;" |I am an undergraduate student
|If an undergraduate student is working for a research group and needs access to HPC infrastructure, their account must be confirmed by their research supervisor. Additionally, the supervisor must confirm the nature of the research work the student is conducting is related to the supervisor's area of research and that the HPC infrastructure is necessary to faciliate this research.
Every undergraduate student who needs an account on ARC is still expected to submit their own application, and answer all the questions '''on their own'''. If the student has difficulties with answering the application questions, it may be too early to create and account or the ARC environment is not appropriate for their research. ARC is a production research system and untrained users can potentially disrupt other researchers work.

'''Next steps''': Please have undergraduate student email the completed application form to support@hpc.ucalgary.ca and cc'd to the research supervisor. The research supervisor must then reply to support@hpc.ucalgary.ca with their approval.
|}

To apply, please '''copy and paste''' the [[How to get an account#Application form|Application form]] below into an email message to [mailto:support@hpc.ucalgary.ca support@hpc.ucalgary.ca] and then respond to the questions in the text.

Please also include the subsequent '''[[How to get an account#Clauses of understanding|clauses of understanding]]''' into your application as your agreement to these terms are mandatory.

== ARC application form ==
'''About myself:'''

*What is your status with the University of Calgary? (Eg. undergraduate student, PhD student, MS student, postdoc, visiting researcher)

*What research group do you work for?
*Who is your supervisor?
:(If you are a Principal Investigator yourself, please respond accordingly).

*How did you learn about the ARC cluster?

*Do you have any experience with '''Linux'''?

*Have you used '''compute clusters''' before?

*Does anybody else in your group use ARC for their work?

*What '''shortcoming of your work computer''' are you trying to address by using a compute cluster? '''What is lacking''' on your computer that is required for you work?

'''About the project(s) I am going to work on''':

*Please tell us a briefly about the '''research topic''' you are going to be working on on ARC.

*What are the '''data''' you are planning to work on? What '''form''' is it in?

*What '''kind of analysis''' is it?

*What '''software''' are you going to be using?

*Do you have an estimate for the '''amount''' of work (please provide it, if known)?

=== Clauses of understanding ===
By applying for an ARC account I certify '''I understand that''':

* The storage provided by the ARC cluster is only suitable for '''Level 1 and Level 2 data''', as classified according to the University of Calgary Information '''Security Classification Standard''' (https://www.ucalgary.ca/legal-services/sites/default/files/teams/1/Standards-Legal-Information-Security-Classification-Standard.pdf)
* ARC's availability may be changed with little to no warning. While RCS take precautions to avoid interrupting running jobs, there may be instances where interruptions are occur including power or network interruptions. RCS may also take nodes offline for regular maintenance and node availability is subject to change.
* ARC's storage should not be used as your main storage facility for research data. Access to your data may be interrupted or temporarily unavailable when ARC is under maintenance. Data on ARC is not backed up. Your research group should ensure that the master copy of research data should be stored elsewhere. We highly recommend that only data used for computational analysis on ARC should reside on ARC.
* User's accounts on ARC are subject to '''automatic deletion after 12 months of inactivity'''. Please log in periodically to prevent your account from being deleted. You will be notified before the account is deleted. Please note that when an account is delete '''all the data''' stored in the home directory of the account are '''deleted''' as well.

== Book online training sessions ==
After obtaining your ARC account, you may [[book online training sessions]] with one of our analysts to get started with ARC.

[[Category:Guides]]
[[Category:How-Tos]]
{{Navbox Guides}}