bio-pipengine 0.9.3 → 0.9.4

Sign up to get free protection for your applications and to get access to all the features.
Files changed (5) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +15 -4
  3. data/VERSION +1 -1
  4. data/bin/pipengine +5 -2
  5. metadata +7 -7
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 82814e5bfa7e4fb2f89ac53262722ac769ce0ad7
4
- data.tar.gz: e595dc961368cde6009e039bfe40ad9607960450
3
+ metadata.gz: aa7bc3b6bb8a47fe8a210589319e47a6aec53c2d
4
+ data.tar.gz: e516a1204f81dd37258b08afa88005bde4e4f2ed
5
5
  SHA512:
6
- metadata.gz: 802301520a0405d748429810cfa8e398dfd92b9cec937d9fa37bcb217d7c2c507be61e6f2d25de2fa04dc0f0fe1ce863303748d09194772a62378a3c8ea2d2e4
7
- data.tar.gz: 8bf3b5a453843891c16b1d501209320868967203d23601dda97b59e22b07f96f1ff8d968318bdb6da339d0632c41260895c1cc69c38d3687a16ffb72a914b7a9
6
+ metadata.gz: bf5549e208b344164287c3e30b7a9daedf3588c462af5614f95143a09a5059c40b79e2a94e6cb17fd63ad17ab1eb99ae2d133110f019c3f9ca456b0dee400c9d
7
+ data.tar.gz: 1139a43b09f25463963e6b482d9af7c4d6214fb750d2ac6682a5d65cffca37e8e8c134a4cedd9c323c3fd36d26edc222098220170cbf9871737acde593083cef
data/README.md CHANGED
@@ -7,6 +7,9 @@ PipEngine will generate runnable shell scripts, already configured for the PBS/T
7
7
 
8
8
  PipEngine is best suited for NGS pipelines, but it can be used for any kind of pipeline that can be runned on a job scheduling system and which is "sample" centric, i.e. you have from one side a list of samples with their corresponding raw data, and from the other side a pipeline that you would like to apply to them.
9
9
 
10
+ PipEngine was developed to combine the typical flexibility and portability of shell scripts, with the concept of pipeline templates that can be easily applied on different input data to reproduce scientific results. The overall improvement over Makefiles or customised ad-hoc shell scripts is better readability of the pipelines using the YAML format, especially for people with no coding experience, the automated scripts generation which allows adding extra functionalities like error controls and logging directly into script jobs, and an enforced separation between the description of input data and the pipeline template, which improves clarity and reusability of analysis protocols.
11
+
12
+
10
13
  Installation
11
14
  ============
12
15
 
@@ -30,6 +33,8 @@ and then install PipEngine using RubyGems:
30
33
  gem install bio-pipengine
31
34
  ```
32
35
 
36
+ Pipengine has been tested and should work with Ruby >= 2.1.2
37
+
33
38
  :: Topics ::
34
39
  ============
35
40
 
@@ -49,10 +54,11 @@ gem install bio-pipengine
49
54
 
50
55
  [PBS Options](https://github.com/bioinformatics-ptp/bioruby-pipengine#-pbs-options-)
51
56
 
57
+ [Extending and contributing](https://github.com/bioinformatics-ptp/bioruby-pipengine#-extending-and-contributing-)
58
+
52
59
  :: Usage ::
53
60
  ===========
54
61
 
55
- PipEngine it's divided into two main sections:
56
62
 
57
63
  ```shell
58
64
  > pipengine -h
@@ -63,8 +69,6 @@ List of available commands:
63
69
  Command line for RUN mode
64
70
  -------------------------
65
71
 
66
- With this mode, PipEngine will submit pipeline jobs to the scheduler.
67
-
68
72
  **Command line**
69
73
  ```shell
70
74
  > pipenengine run -p pipeline.yml -f samples.yml -s mapping --tmp /tmp
@@ -651,7 +655,14 @@ within the job script.
651
655
 
652
656
  If a specific queue needs to be selected for sending the jobs to PBS, the ```--pbs-queue``` (short version **-q**) parameter can be used. This will pass to the ```qsub``` command the ```-q <queue name>``` taken from the command line.
653
657
 
658
+ :: Extending and contributing ::
659
+ ================================
660
+
661
+ Pipengine code is organized around main methods allowing for YAML parsing and command line arguments substitutions that are available in lib/bio/pipengine.rb. Specific logic for jobs, pipeline steps and samples is described in dedicated classes called Bio::Pipengine::Job, Bio::Pipengine::Step and Bio::Pipengine::Sample.
662
+
663
+ For instance, in case the support for different schedulers needs to be introduced, it will be sufficient to modify or extend the Job.to_script method, which is the one defining scheduler-specific options in the runnable bash script.
664
+
654
665
  Copyright
655
666
  =========
656
667
 
657
- &copy;2016 Francesco Strozzi, Raoul Jean Pierre Bonnal
668
+ &copy;2017 Francesco Strozzi, Raoul Jean Pierre Bonnal
data/VERSION CHANGED
@@ -1 +1 @@
1
- 0.9.3
1
+ 0.9.4
data/bin/pipengine CHANGED
@@ -3,7 +3,7 @@
3
3
  $:<< File.expand_path(File.join(File.dirname(File.dirname __FILE__),"lib"))
4
4
  require 'bio-pipengine'
5
5
 
6
- banner_text = "\nLauncher for Complex Biological Pipelines . Copyright(C) 2013 Francesco Strozzi, Raoul Jean Pierre Bonnal\n\n"
6
+ banner_text = "\nLauncher for Complex Biological Pipelines . Copyright(C) 2012 Francesco Strozzi, Raoul Jean Pierre Bonnal\n\n"
7
7
  version_text = File.read File.expand_path(File.join(File.dirname(File.dirname __FILE__),"VERSION"))
8
8
  SUB_COMMANDS = %w(run jobs)
9
9
 
@@ -46,12 +46,15 @@ when "run"
46
46
  # end
47
47
  when "-h"
48
48
  puts banner_text
49
- puts "List of available commands:\n\trun\tSubmit pipelines to the job scheduler\n\tjobs\tShow statistics and interact with running jobs\n"
49
+ puts "List of available commands:\n\trun\tSubmit pipelines to the job scheduler\n"
50
50
  exit
51
51
  else
52
52
  global_opts = Trollop::options do
53
53
  banner banner_text
54
54
  version "PipEngine v#{version_text}"
55
+ puts banner_text
56
+ puts "PipEngine v#{version_text}"
57
+ puts "List of available commands:\n\trun\tSubmit pipelines to the job scheduler\n\n"
55
58
  end
56
59
  end
57
60
 
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: bio-pipengine
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.9.3
4
+ version: 0.9.4
5
5
  platform: ruby
6
6
  authors:
7
7
  - Francesco Strozzi
@@ -9,7 +9,7 @@ authors:
9
9
  autorequire:
10
10
  bindir: bin
11
11
  cert_chain: []
12
- date: 2016-05-09 00:00:00.000000000 Z
12
+ date: 2017-08-12 00:00:00.000000000 Z
13
13
  dependencies:
14
14
  - !ruby/object:Gem::Dependency
15
15
  name: trollop
@@ -17,28 +17,28 @@ dependencies:
17
17
  requirements:
18
18
  - - ">="
19
19
  - !ruby/object:Gem::Version
20
- version: '0'
20
+ version: 2.1.2
21
21
  type: :runtime
22
22
  prerelease: false
23
23
  version_requirements: !ruby/object:Gem::Requirement
24
24
  requirements:
25
25
  - - ">="
26
26
  - !ruby/object:Gem::Version
27
- version: '0'
27
+ version: 2.1.2
28
28
  - !ruby/object:Gem::Dependency
29
29
  name: colorize
30
30
  requirement: !ruby/object:Gem::Requirement
31
31
  requirements:
32
32
  - - ">="
33
33
  - !ruby/object:Gem::Version
34
- version: '0'
34
+ version: 0.8.1
35
35
  type: :runtime
36
36
  prerelease: false
37
37
  version_requirements: !ruby/object:Gem::Requirement
38
38
  requirements:
39
39
  - - ">="
40
40
  - !ruby/object:Gem::Version
41
- version: '0'
41
+ version: 0.8.1
42
42
  - !ruby/object:Gem::Dependency
43
43
  name: warbler
44
44
  requirement: !ruby/object:Gem::Requirement
@@ -107,7 +107,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
107
107
  version: '0'
108
108
  requirements: []
109
109
  rubyforge_project:
110
- rubygems_version: 2.4.5
110
+ rubygems_version: 2.6.8
111
111
  signing_key:
112
112
  specification_version: 4
113
113
  summary: A pipeline manager