![]() The FireWorkers request workflows from the LaunchPad, execute them, and send back information. One or more workers (“FireWorkers”) that run your jobs. The workflows can be a straightforward series of scripts or dynamically adapt depending on the results obtained. You can add workflows (a DAG of “FireWorks”) to the LaunchPad, query for the state of your workflows, or rerun workflows. There are essentially just two components of a FireWorks installation:Ī server (“LaunchPad”) that manages workflows. Support for several queueing systems such as PBS/Torque, Sun Grid Engine, SLURM, and IBM LoadLeveler. Package many small jobs into a single large job (e.g., automatically run 100 serial workflows in parallel over 100 cores) Remotely track the status of output files during execution. ![]() Support for dynamic workflows - workflows that modify themselves or create new ones based on what happens during execution.Īutomatic duplicate handling at the sub-workflow level - skip duplicated portions between two workflows while still running unique sectionsīuilt-in tasks for creating templated inputs, running scripts, and copying files to remote machines Multiple execution modes - directly on a multicore machines or through a queue, on a single machine or multiple machines. Some (but not all) of its features include:Ī clean and flexible Python API, a powerful command-line interface, and a built-in web service for monitoring workflows.Ī database backend (MongoDB) lets you add, remove, and search the status of workflows.ĭetect failed jobs (both soft and hard failures), and rerun them as needed. ![]() FireWorks is intended to be a friendly workflow software that is easy to get started with, but flexible enough to handle complicated use cases.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |