First steps: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 15: | Line 15: | ||
* If you are going to travel, but want to continue working on Tycho while you are travelling, you need to set up a Dynamic Firewall '''before''' travelling. You can do so by following the detailed instructions [https://hpc.ku.dk/documentation/otp.html: here] | * If you are going to travel, but want to continue working on Tycho while you are travelling, you need to set up a Dynamic Firewall '''before''' travelling. You can do so by following the detailed instructions [https://hpc.ku.dk/documentation/otp.html: here] | ||
* Consider setting up Visual Studio Code for remote development for transparent editing of files on the cluster. See [[Visual Studio Remote Development]] | |||
Revision as of 13:58, 15 November 2023
To start using Tycho, please follow these steps
- Get a user account by contacting a sponsor and signing up at
https://hpc.ku.dk/account.html
You have to select "Astro" as your group. Remember to sign the rules-of-conduct-form
- BE AWARE THAT THE WELCOME E-MAIL IS NOT CORRECT. You should never login to fend0X.hpc.ku.dk, but instead use the Tycho-specific frontends called astro0X.hpc.ku.dk (see Hardware for an up to date list of available frontends / Analysis hardware).
- Set up an SSH key pair for secure passwordless login (see Accessing Tycho)
- Add
module load astroto you$HOME/.bashrcfile to have access to all the custom installed software. - Consider changing
umask 077toumask 027in$HOME/.bashrcto allow collaborators and/or your supervisor read access to your files when logged in to the cluster.
- If you are going to travel, but want to continue working on Tycho while you are travelling, you need to set up a Dynamic Firewall before travelling. You can do so by following the detailed instructions here
- Consider setting up Visual Studio Code for remote development for transparent editing of files on the cluster. See Visual Studio Remote Development