Body
Quest and Kellogg Linux Cluster Downtime, December 14 - 18.Quest, including the Quest Analytics Nodes, the Genomics Compute Cluster (GCC), the Kellogg Linux Cluster (KLC), and Quest OnDemand, will be unavailable for scheduled maintenance starting at 8 A.M. on Saturday, December 14, and ending approximately at 5 P.M. on Wednesday, December 18. During the maintenance window, you will not be able to login to Quest, Quest Analytics Nodes, the GCC, KLC, or Quest OnDemand submit new jobs, run jobs, or access files stored on Quest in any way including Globus. For details on this maintenance, please see the Status of University IT Services page.
Quest RHEL8 Pilot Environment - November 18.Starting November 18, all Quest users are invited to test and run their workflows in a RHEL8 pilot environment to prepare for Quest moving completely to RHEL8 in March 2025. We invite researchers to provide us with feedback during the pilot by contacting the Research Computing and Data Services team at quest-help@northwestern.edu. The pilot environment will consist of 24 H100 GPU nodes and seventy-two CPU nodes, and it will expand with additional nodes through March 2025. Details on how to access this pilot environment will be published in a KB article on November 18.
This page provides help getting started with connecting to, accessing software on, and submitting jobs to the Quest computing cluster.
See our Introduction To Quest video for a 90-minute interactive tutorial that takes you step-by-step through logging into Quest, editing a job submission script, launching and monitoring a job, as well as a deep dive into how Quest works.
Navigating Quest
If you'd prefer a video demonstration you can get started with basic commands and a demonstration of navigating home and project directories on Quest by watching our video tutorial Navigating Quest via Shell.
Once you've logged into Quest, you will begin in your Home directory: /home/<NetID>. The home directory has 80GB of storage and is backed up nightly. Backups are kept for two weeks.
Note that throughout this guide, items in angle brackets (<>) in example commands are parameters you need to change relative to your account and work. Do not include <> around the values you substitute into the commands.
You can navigate to the projects directory of your allocation by typing
cd /projects/<project_id>
Project directories are not backed up. You can check how much storage you have by typing
checkproject <project_id>
If you are unfamiliar with using the command line, this tutorial, Learning the Shell, will help you learn the basics.
Moving Files onto Quest
Please visit the Transferring Files on Quest web page for information about transferring files from your local machine, the Northwestern OneDrive/Sharepoint Endpoint, Research Data Storage Service, or elsewhere, to Quest.
Software available on Quest
Many applications are available on Quest. You can access them through modules, which modify your environment to enable you to run the software. Quest uses modules so that multiple versions of the same software can be available for different users.
See Modules Software Environment Manager for examples of loading software with modules and a list of common commands.
If you would like additional software packages installed on Quest, please fill out the Software Installation Request Form. Additionally, you can also install software in your own home or project directories. For details, review our Installing Software on Quest page.
Running Jobs on Quest
When you first log in to Quest, you will be on one of the four login nodes: quser21, quser22, quser23, or quser24. From the login nodes, you can submit jobs to the compute nodes, edit files, and perform small test jobs. Login node use is limited to 4 cores and 4 GB of RAM per user.
To take advantage of Quest's computing power, jobs can be submitted to the compute nodes in two ways: Interactive jobs, which are particularly useful for GUI applications, or Batch jobs, which are the most common jobs on Quest. Interactive jobs are appropriate for GUI applications like Stata, Visit, Paraview, etc., testing and prototyping of programs, running jobs with small core counts (< 6), and for short duration jobs. Batch jobs are appropriate for jobs with no GUI interface, large core counts, or long duration.
See Submitting a Job on Quest for more details, example job submission commands, and an example of a submission script.
Managing Your Jobs on Quest
| Command |
Description |
squeue -u <NetID> |
Shows your jobs on the queue |
squeue -A <AllocationID> |
Shows your jobs belonging to specified allocation |
checkjob <JobID> |
Shows detailed information about specified job |
scancel <JobID> |
Cancels your job from the command line |
scancel -u <NetID> |
Cancels all of your jobs from the command line |
For more information about managing your jobs visit Managing Jobs on Quest.
Getting Help
Learn more about using Quest from our documentation or attend one of our Introduction to Quest trainings. If you need more personalized assistance, send an email stating your issue to quest-help@northwestern.edu and the Northwestern IT Research Computing Services team will assist you with your issue.