Skip to content

Update README to reflect new rocoto repo ownership #131

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
christopherwharrop-noaa merged 1 commit into from
Apr 28, 2026
Merged

Update README to reflect new rocoto repo ownership #131

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Rocoto Workflow Management System

[![TestSuite](https://github.com/christopherwharrop/rocoto/actions/workflows/test-suite.yaml/badge.svg)](https://github.com/christopherwharrop/rocoto/actions/workflows/test-suite.yaml)
[![TestSuite](https://github.com/NOAA-GSL/rocoto/actions/workflows/test-suite.yaml/badge.svg)](https://github.com/NOAA-GSL/rocoto/actions/workflows/test-suite.yaml)

## Introduction
Workflow Management is a concept that originated in the 1970's to handle business process management. Workflow management systems were developed to manage complex collections of business processes that need to be carried out in a certain way with complex interdependencies and requirements. Scientific Workflow Management is much newer, and is very much like its business counterpart, except that it is usually data oriented instead of process oriented. That is, scientific workflows are driven by the scientific data that "flows" through them. Scientific workflow tasks are usually triggered by the availability of some kind of input data, and a task's result is usually some kind of data that is fed as input to another task in the workflow. The individual tasks themselves are scientific codes that perform some kind of computation or retrieve or store some type of data for a computation. So, whereas a business workflow is comprised of a diverse set of processes that have to be completed in a certain way, sometimes carried out by a machine, sometimes carried out by a human being, a scientific workflow is usually comprised of a set of computations that are driven by the availability of input data.
Expand Down Expand Up @@ -132,7 +132,7 @@ Depending on how the components of a modeling system are designed and how existi
Each workflow task must correctly check for its successful completion, and must return a non-zero exit status upon failure. An exit status of 0 means success, regardless of what actually happened. No workflow task should contain automation features. Automation is the workflow management system's responsibility. A workflow management system cannot manage tasks or jobs that it is not aware of. Enable reuse of workflow tasks by using principles of modular design to build autonomous model components with well-defined interfaces for input and output that can be run stand-alone. Prefer the construction of small model components that do only one thing. It is easy to combine several small, well-designed, components together to build a larger, more complex workflow task. It is generally much more difficult to divide large, complex, model components into smaller ones to form multiple workflow tasks. Avoid combining serial and parallel processing in the same workflow task unless the serial processing is very short in duration.

## Documentation
Detailed documentation is provided at http://christopherwharrop.github.io/rocoto/
Detailed documentation is provided at https://noaa-gsl.github.io/rocoto/

## Code Linting and Style (RuboCop)

Expand Down
Loading