Accelerate your research with
PROOF Workbench
Submit, track, and troubleshoot WDL workflows on the Fred Hutch cluster
Organize and speed up your cluster computing with WDL
Use WDL workflows to make your work more composabile and portable.
Take an advantage of WDL modules that have already been optimized for the Fred Hutch cluster.
Share WDL workflows with your colleagues so they can verify, adapt, and improve on your results.
Validate, submit, track, and troubleshoot your workflows with ease
Monitor your running workflows in real time, and browse previous iterations of executed workflows.
Inspect the detilas of failed jobs, error messages, and past versions to troubleshoot failed workflows.
Get live help debugging workflows via Teams, Slack, or Data House Calls.
Make the best of all the computing resources Fred Hutch has to offer
All of the workflows you submit with PROOF run on the Fred Hutch cluster, so there is no additional cost.
Develop, test, and harden your workflows as a 'proof of concept' before moving compute to the cloud, saving money in the process.
Working with data that is subject to an NIH Data Use Certification, perhaps from dbGaP? No problem, PROOF Workbench is fully compliant.
New to the cluster? Get started with this self-paced course.
Our tutorial is a great was to get acquainted with PROOF.
Browse the WILDS WDL Library for ready-to-launch workflows.
Modularize your compute with the WILDS Docker Library.
Get started with our Developing WDL Workflows self-paced course.
OCDO is eager to collaborate with you directly to write WDLs.
PROOF runs on the Fred Hutch cluster. If you need cluster access and you are a Fred Hutch employee, complete our introductory tutorial. If you already have access, log in with your Fred Hutch credentials. Make sure are you are on campus or connected to the VPN to access PROOF.
Start a PROOF server that will track the WDL workflows you submit to the Fred Hutch cluster. Your PROOF server is like a puppet-master, coordinating the tasks articulated in your WDL, ensuring that workflow results are cached for faster execution, and paralleling your computing with no extra effort on your part.
Once your PROOF server is up and running, first validate your WDL to ensure it is free from syntax errors. After validating your WDL, submit it, along with input and options JSON files to be run on the Fred Hutch cluster.
After submitting a WDL, you can track its progress, including the status of each job that it launches, in real time. If a job fails, do not get discouraged, WDL development is often an iterative process. OCDO offers several avenues for support in WDL development and using PROOF.
Running WDLs on PROOF allows you to develop workflows that you can share with your research group, your collaborators, or even the broader field. With PROOF you can iterate on your workflows in a low-stakes environment before moving vetted workflows to the cloud.
We are here to help you develop and troubleshoot WDL workflows. Schedule a 20 minute Research Computing Data House Call to get started.
If you need any help using PROOF Workbench, we are here for you. Schedule a 20 minute Code & Software Data House Call for live help.
Fred Hutch staff can join our dedicated channel all about PROOF Workbench and WDL development on Teams.
Researchers from across the Cancer Consortium are welcome to join the PROOF community on Slack in the #workflow-managers channel.