Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
E
ensembl-hive
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Iterations
Wiki
Requirements
Jira
Code
Merge requests
7
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ensembl-gh-mirror
ensembl-hive
Commits
c8cb331d
Commit
c8cb331d
authored
11 years ago
by
ens-lg4
Browse files
Options
Downloads
Patches
Plain Diff
further markdowning of unmarkdownable
parent
1169d031
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+12
-13
12 additions, 13 deletions
README.md
with
12 additions
and
13 deletions
README.md
+
12
−
13
View file @
c8cb331d
...
...
@@ -31,19 +31,18 @@ PipeConfig file defines Analyses and dependency rules of the pipeline
Hive pipeline databases are molded according to PipeConfig files which are Perl modules conforming to a special interface.
A PipeConfig file defines the stucture of the pipeline, which is a graph whose nodes are Analyses
(with their code, parameters and resource requirements) and edges are various dependency rules:
*
Dataflow rules define how data that flows out of an Analysis can be used to trigger creation of Jobs in other Analyses
[creation depenency]
*
Control rules define dependencies between Analyses as Jobs' containers
("Jobs of Analysis Y can only start when all Jobs of Analysis X are done")
[execution dependency]
*
Semaphore rules define dependencies between individual Jobs on a more fine-grained level
[combined creation and execution dependency]
*
Dataflow rules define how data that flows out of an Analysis can be used to trigger creation of Jobs in other Analyses
*
Control rules define dependencies between Analyses as Jobs' containers ("Jobs of Analysis Y can only start when all Jobs of Analysis X are done")
*
Semaphore rules define dependencies between individual Jobs on a more fine-grained level
There are also other parameters of Analyses that control, for example:
*
how many Workers can simultaneously work on a given Analysis,
*
how many times a Job should be tried until it is considered failed,
*
what should be autimatically done with a Job if it needs more memory/time,
etc.
*
how many Workers can simultaneously work on a given Analysis,
*
how many times a Job should be tried until it is considered failed,
*
what should be autimatically done with a Job if it needs more memory/time,
etc.
Contact us (mailing list)
-------------------------
...
...
@@ -52,9 +51,9 @@ for running Comparative Genomics pipelines, but since then it has been separated
into a separate software tool and is used in many projects both in Genome Campus, Cambridge and outside.
There is a Hive users' mailing list for questions, suggestions, discussions and announcements.
To subscribe to it please visit:
To subscribe to it please visit:
http://listserver.ebi.ac.uk/mailman/listinfo/ehive-users
After subscribing you will be able to post to:
After subscribing you will be able to post to:
ehive-users@ebi.ac.uk
This diff is collapsed.
Click to expand it.
Preview
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment