--- **ALICE at HackyHour (April 18th 2020)** The texts in quotes are copied from the ALICE wiki --- **General ALICE Wiki:** https://wiki.alice.universiteitleiden.nl/index.php?title=ALICE_User_Documentation_Wiki **How to get an account:** "provide your ULCN or LUMC account name" in an email to the helpdesk https://wiki.alice.universiteitleiden.nl/index.php?title=Getting_an_account **What is ALICE?** > “High-Performance Computing” (HPC) is computing on a “Supercomputer ”, a computer with at the frontline of contemporary processing capacity – particularly speed of calculation and available memory." > "The HPC currently consists of: A set of different computer clusters" > Computer Cluster = Several Computer connected by a local network ALICE is a super computer that is available to be used by any researcher at LU and LUMC. Which is great, you dont need to pay for it, nor do you need to go through a lengthy process to get an account. Mention you used ALICE in your papers though, that makes everyone happy and ensures finances. ALICE is the brain child of people at the Astrophysics department. You might want to keep that in mind when trying to understand documentation. In general, Python and matlab are much more common on there than R. **Workflow** > A typical workflow looks like: > 1. Connect to the login nodes with SSH > 2. Transfer your files to the cluster > 3. Create a job script and submit your job - SLURM it > 4. Get some coffee and be patient: > 1. Your job gets into the queue > 1. Your job gets executed > 1. Your job finishes > 5. Study the results generated by your jobs, either on the cluster or after downloading them locally. **Debugging and getting started** > "Use the debug queue. It has a higher priority which is useful for running tests that can complete in less than 10 minutes." sinfo doesnt give me a "debugging partition". Nor a partition that has a timelimit of 10 min. It does however have a "testing" partition with a timelimit of 60min. So I am assuming that is where the debug queue is. Which basically means, to test slurm scripts, use "testing" instead of "cpu-long" or "gpu-short" (or others). **Integrating git and/or RStudio** --> hot tips? --> how should I organize my repo? --> SLURM can do a lot, let's hear Ed talk about that!