Features How Workflow Commander tames Grid Engines for you
Save your code for something special.
In order to get massive amounts of work done on compute clusters, you analyze code and run programs constantly. Having to do the same through the Grid Engine scheduler just to keep data flowing is a distraction. Leave the tedious task of monitoring workflows to Workflow Commander, and use that precious programmer time towards interesting analysis work.
A picture == 1000 words.
A flowchart is useful when understanding large systems in a simple way. So for complex computational work, why not use flow diagrams? Once you monitor the entire workflow status with just a glance, the old way will seem like the hard way.
No installation, no problem.
Does your sysadmin object to installing messy programs, or any programs? Workflow Commander keeps your data organized, has no installation process, and it can be run without superuser privileges on the server. Keep things moving along without fighting with software or sysadmin rules.
Reclaim time and get more done.
Workflow Commander has many more features to save you time, make you more efficient, and keep you organized. You can see what we mean by giving the Lite Edition a whirl -- no limits or strings attached. Use your extra time to do more of what you do, and get rewarded for it.
Make reproducible science work for you
When a collaborator shares a workflow with you, getting it to run is straightforward. And when you publish your own work, half of the methods writeup is done before you begin, including an analysis flowchart image. Running workflows more easily leads to better science -- that can't be disputed.
Catch bugs before they catch you.
An important first requirement for quick agile iterating of your work is responsive error-reporting. Don't let a workflow with an error run longer than it has to. Use Workflow Commander to diagnose errors correctly, quickly, and easily.
GUI doesn't mean lock-in.
Workflow Commander was designed with advanced programmers in mind, too. The workflow format is a very concise XML -- easy to write and manipulate. Having a simple, open format means that the effort you put into your workflows is never a one-way deal.
Build off expert work quickly.
Get started analyzing by loading pre-defined workflows directly into the editor. Don't waste time re-inventing the wheel. If you create workflows of your own algorithms for others to use, upload them to the central repository with attribution information to make them accessible to the entire Workflow Commander userbase.
Adapt to your servers' needs.
The server portion of Workflow Commander can be run on an unlimited number of servers, so position it wherever you see fit. If many users are running the server process on the same server, they can share one process run by a superuser. Settings and permissions will be respected in a shared server instance as they would be in many, separate individual instances. Workflow Commander uses SSH to communicate between client and server, and SSH comes standard on nearly every server.
Resume seamlessly after dropped connections.
Whether your network connection drops or a program process quits, Workflow Commander will pick up where it left off as soon as everything is up and running again. Workflow Commander never alters the scheduling of jobs on the compute cluster at any time.
Handle the compute cluster details in stride.
Do you specify where the output and error streams will be saved to? Workflow Commander will save this for you automatically, even if you don't. It allows you to specify array jobs, simplifies your workflow, and eases the burden on the server.
Stay lean and clean.
All of the files organized by Workflow Commander are in one place. Clearing up disk space or resetting program configurations is just a matter of cleaning up a single folder.