Open Modification DDA using Magnum
This page describes how to run a workflow that uses Magnum and Percolator for open modification DDA proteomics searching and uploading those results to Limelight for visualization, analysis, and sharing.
Prerequisites
Note
These are optional, one-time setup steps.
If you plan to upload results to Limelight, please set up your Limelight credentials.
If you will be downloading data from Panorama, please set up your Panorama credentials.
Workflow Steps
Connect to the GSIT (Nexus) system Follow the instructions to connect via SSH.
Create a directory for the analysis Create and move into a new directory for your analysis. For example:
mkdir magnum-run cd magnum-run
Copy configuration files Copy the template files for the workflow into your new directory:
cp /net/maccoss/vol1/maccoss_shared/nextflow/templates/openmod-dda/Magnum.conf . cp /net/maccoss/vol1/maccoss_shared/nextflow/templates/openmod-dda/pipeline.config .
Update
Magnum.confEdit theMagnum.conffile for your specific analysis. You can find detailed information about Magnum parameters at the Magnum documentation.Update
pipeline.configEdit thepipeline.configfile to set the parameters for the Nextflow workflow itself. More information about the Nextflow parameters can be found in the workflow documentation.Run the workflow Execute the following script to start the workflow:
/net/maccoss/vol1/maccoss_shared/nextflow/scripts/run-nextflow-dda-openmod-maccosslab.sh
Editing Files with Nano
A simple way to edit files on the command line is with the nano text editor. To edit a file, run:
nano <filename>
For example, to edit Magnum.conf:
nano Magnum.conf
To save your changes and exit, press Ctrl + X, then Y to confirm, and finally Enter.
Running with tmux
Note
When you connect to nexus.gs.washington.edu, you are randomly logged into one of nexus1, nexus2, or nexus3. To reattach to a tmux session, you must be logged into the same server where the session is running.
It is recommended to explicitly connect to a specific server (e.g., ssh your_username@nexus1.gs.washington.edu) to make it easier to find and reattach to your sessions later.
It is highly recommended to run long processes like this workflow inside a tmux session. tmux is a terminal multiplexer that allows you to create persistent terminal sessions. This means your workflow will continue to run even if you get disconnected from the server.
Start a new `tmux` session and run the workflow: This command creates a new session named nextflow_run and executes the workflow script inside it.
tmux new -s nextflow_run "bash -c '/net/maccoss/vol1/maccoss_shared/nextflow/scripts/run-nextflow-dda-openmod-maccosslab.sh;exec bash'"
Detach from the session: You can safely detach from the session, and your workflow will continue to run. To detach, press
Ctrl + bfollowed byd.Reattach to the session: To check on your workflow’s progress, you can reattach to the session at any time:
tmux attach -t nextflow_run
Exit the session: Once the workflow is finished, it is important that you exit the tmux session by typing
exitand pressingEnter.Note
If you need to re-execute a workflow, be sure to exit the tmux session before starting another one.
Specifying a Cluster Queue
By default, the workflow runs on the sage cluster queue, which is the general queue for Genome Sciences users. You can specify a different queue using the -q flag.
Available queues:
maccoss: The MacCoss lab cluster queue, available to all users in the MacCoss lab.sage: The general GS cluster queue, available to all users in Genome Sciences.pr: The UW Proteomics Resource queue; may not be available to all users.
For example, to run the workflow on the pr queue:
/net/maccoss/vol1/maccoss_shared/nextflow/scripts/run-nextflow-dda-openmod-maccosslab.sh -q pr