General
Best Practices
Event Procedure
Helpdesk Request Form
Lab Closure Procedure
Links
Resource Drive Conventions
Resource Map
Shipping (FedEx)
Shipping (International)
Suggestion Box
Support Article Guidelines
Welcome
Information Technology
Email & Calendar
Add Calendars to iPhone
Confidential emails
Create a Shared Calendar
Create an Email Group
Email Filters & Rules
Email Groups
Email Headers
Email Signatures
Google 2-Step Verification
Google Calendar Overview
Phishing
Schedule emails
Staff Minus One Emails
Using Outlook with Gmail
Using Yubico Security Keys with your Google account
Print & Fax
Software
1Password
Adobe Acrobat DC
Adobe Creative Cloud
ArcGIS
Colby VPN
Combine PDFs in Adobe Acrobat
Excel Trust Settings
Install Falcon Antivirus
Microsoft Office
Microsoft Office Runtime Error Fix
Mosyle Mac Enrollment
Raiser's Edge
Slack
Software Resources
Uninstall OpenVPN
Windows 10 - Restore from backup
Updates
2020 December - email name spoofing
2020 October - COVID resources
2021 December - WiFi
2021 January - Zoom recording + private chat
2021 March - NetSuite Google authentication
2021 March - VPN Upgrade
2023 - Zoom Updates
2024 May - VPN SSO
DNS
DNS Change
Data Storage and Computer Backups
Google Drive
HPCC and Storage Proposal Information
Laptop Recommendations
Loaner Hardware
Migrating data from Storage to Google Drive
Passwords
Phones
Restoring Files
Storage
VPN
VPN Migration
Vendor Access
Website Request
WiFi
Zeiss Digital Classroom
HR & Payroll
Paid Time Off
Payroll Overview & FAQ
Personnel Offboarding
Personnel Onboarding
Timesheet Approval (supervisors)
Timesheets
Facilities
BMS Access
Bigelow R/V Billing Form
E&I Wing Construction Update
R/V Bowditch Reservation Center
R/V Clarice Reservation Center
Finance
Admin
Budget & Reports
Invoicing
Policies & Procedures
Advancement Entry of Donations and Pledges
Corporate Traveler / Melon
Gas and Cryo-Supply Ordering Process and Form Link
Purchasing Flowchart - for staff reference
Purchasing Policy
Vendors Exempt from Purchase Orders
Proposals
Purchase & Expense
Bill/Invoice Approval
Creating a Bill to be Paid
Equipment Capitalization Help
Expense Report
Expense Report (example)
Non-Employee Reimbursement
Purchase Order
Purchase Order (example)
Purchase Order (supplemental)
Recurring Purchase Order (SRS)
Amazon.com
Approval Reminders
Business Office Orientation
Capital One - Corporate Credit Card
Customize Dashboard
Dashboard (SRS)
NetSuite FAQ
NetSuite Login
NetSuite shortcuts
Revenue Flow Chart
Workshop, Training Projects, and Participant Support Help
Computing
Software
AAI Calculation
ANI Calculation
AlphaFold
Anvi'o
Conda environments
Jupyter notebook
Prokka
RStudio
dada2
sag-mg-recruit
Job management
Charlie Overview
Connect to Charlie
Edit with VS Code
Getting Started
Monitor jobs
Software modules
Transfer files
Zoom
- Home
- Computing
- Job management
- Interactive jobs
Interactive jobs
Updated
Interactive jobs allow the user to log on to c1 via a scheduled session for the purpose of debugging or new feature development. An interactive job can be created by typing qsub -I submission.sh
on the command line. This submission.sh script will be different than the ones used above in that it will only contain PBS directives, leaving out any code that refers to jobs that you would like to test. A PBS directive starts with a # symbol followed by commands that tell PBS how much time and resources to allow you to use on Charlie. An example submission script for an interactive session is shown below:
#!/bin/sh
#PBS -l walltime=1:00:00
#PBS -l select=1:ncpus=1
#PBS -q devel
The above script requests a session on c1 lasting 1 hour and using 1 cpu. For most jobs a single cpu will be sufficient, unless working with parallel programs. In this way, after 1 hour, our session will close automatically. The final line in our submission script #PBS -q devel
tells PBS which queue we would like to use. When using an interactive session the devel queue is the best queue to use because this queue makes sure that the job will be run right away so we can get our test results as fast as possible.
Additionally we do not need to use a submission script for starting an interactive session. We may type the information necessary to start a session directly into the command line as follows: qsub -I -l walltime=1:00:00 -l select=1:ncpus=1 -q level
. This command will produce the same results as described above.
Some example interactive job command line scripts specific to charlie:
For a 8 hour job that uses 5 cpus and 32G of memory:
qsub -I -q route -l walltime=8:00:00,ncpus=5,mem=32G -N my-interactive-job
You may want to specify which server you want your job to run on. To do so, use the model
designator under the -l option. So for the same job as above, specifically run on c1 the command would be:
qsub -I -q route -l walltime=8:00:00,ncpus=5,mem=32G,model=c1 -N my-interactive-job
For a full list of submission options, and job parameters see the Submit a Job page.
Once an interactive job has been submitted, PBS will print:
qsub: waiting for job <Job ID> to start
qsub: job <Job ID> ready
Once PBS prints that the job is ready, its status is R, and thus it will not be possible to adjust the amount of time of the session. To end an interactive session, simply type exit
on the command line.