▶ How to get started quickly
Getting started on LSU systems requires several steps that may vary depending on how experienced you are with HPC systems. The items listed here are not meant to be exhaustive - treat as robust starting points.
Every LONI and HPC system user requires a user account. Some systems also require an allocation account to charge production runs against.
- Visit the applications index to see what software is currently installed. Listings by name and by field (i.e. Computational Biology) are provided. Assistance with installing other software is available.
- Request a LSU and/or LONI user account. Individuals on the LSU campus have access to both sets of resources.
- Be aware that assistance in many forms is always available.
Production efforts on LONI and some LSU resources (i.e. SuperMike-II) require an allocation of system time in units of core-hours (i.e. SU) against which work is charged. This is a no-cost service, but a proposal of one form or another is required. The holder of an allocation then adds users who may charge against it. Note that only faculty and research staff may request allocations (see allocation policy pages for details).
To request or join an allocation, you must have the appropriate system user account and then visit:
- LSU allocation applications (e.g. SuperMike-II).
- LONI allocation applications (e.g. QueenBee, Eric, etc.).
- Learn how to connect to an HPC system (SSH, PuTTY, WinSCP).
- Learn basic Linux commands.
- Learn how to edit files (vi/vim editor).
- Learn about the user shell environment (bash shell).
- Learn how to submit jobs (PBS)
- Learn how to manage data files.
- Learn how to control your applications of choice.
- Learn how to write shell scripts (i.e. job scripts).
- Learn how to install custom software.
- Learn to program in one or more languages.
- Learn how to debug software (ddt, totalview).
- Learn how to use parallel programming techniques.
- Learn how to profile and optimize code (tau).
- Learn how to manage source code (svn).
- Learn how to automate the build process (make).
Users may direct questions to email@example.com.