9 # initialize the database and build the graph in it (it will also print the value of EHIVE_URL) :
12 # optionally also seed it with your specific values:
13 seed_pipeline.pl -url $EHIVE_URL -logic_name take_b_apart -input_id
'{ "a_multiplier" => "12345678", "b_multiplier" => "3359559666" }'
16 beekeeper.pl -url $EHIVE_URL -loop
20 This is a special version of LongMult_conf with hive_use_param_stack mode switched on.
22 This is the PipeConfig file
for the
long multiplication pipeline example.
23 The
main point of
this pipeline is to provide an example of how to write Hive Runnables and link them together into a pipeline.
27 The setting. Let's assume we are given two loooooong numbers to multiply. Reeeeally long.
28 Soooo long that they do not fit into registers of the CPU and should be multiplied digit-by-digit.
29 For the purposes of this example we also assume this task is very computationally intensive and has to be done in parallel.
31 The long multiplication pipeline consists of three "analyses" (types of tasks):
32 'take_b_apart', 'part_multiply' and 'add_together' that we use to examplify various features of the Hive.
34 * A 'take_b_apart' job takes in two string parameters, 'a_multiplier' and 'b_multiplier',
35 takes the second one apart into digits, finds what _different_ digits are there,
36 creates several jobs of the 'part_multiply' analysis and one job of 'add_together' analysis.
38 * A 'part_multiply' job takes in 'a_multiplier' and 'digit', multiplies them and accumulates the result in 'partial_product' accumulator.
40 * An 'add_together' job waits for the first two analyses to complete,
41 takes in 'a_multiplier', 'b_multiplier' and 'partial_product' hash and produces the final result in 'final_result' table.
43 Please see the implementation details in Runnable modules themselves.
47 See the NOTICE file distributed with this work for additional information
48 regarding copyright ownership.
50 Licensed under the Apache License,
Version 2.0 (the "License"); you may not use this file except in compliance with the License.
51 You may obtain a copy of the License at
55 Unless required by applicable law or agreed to in writing, software distributed under the License
56 is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
57 See the License for the specific language governing permissions and limitations under the License.
61 Please subscribe to the
Hive mailing list: http:
71 use base ('Bio::EnsEMBL::Hive::PipeConfig::HiveGeneric_conf'); # All
Hive databases configuration files should inherit from HiveGeneric, directly or indirectly
75 =head2 pipeline_create_commands
78 In addition to the standard creation of the database and populating it with
Hive tables and procedures it also creates two pipeline-specific tables used by Runnables to communicate.
82 sub pipeline_create_commands {
85 @{$self->SUPER::pipeline_create_commands}, # inheriting database and hive tables
' creation
87 # additional tables needed for long multiplication pipeline's operation:
88 $self->db_cmd(
'CREATE TABLE final_result (a_multiplier varchar(255) NOT NULL, b_multiplier varchar(255) NOT NULL, result varchar(255) NOT NULL, PRIMARY KEY (a_multiplier, b_multiplier))'),
93 =head2 pipeline_wide_parameters
95 Description : Interface method that should
return a hash of pipeline_wide_parameter_name->pipeline_wide_parameter_value pairs.
96 The value doesn
't have to be a scalar, can be any Perl structure now (will be stringified and de-stringified automagically).
97 Please see existing PipeConfig modules for examples.
101 sub pipeline_wide_parameters {
104 %{$self->SUPER::pipeline_wide_parameters}, # here we inherit anything from the base class
111 sub hive_meta_table {
114 %{$self->SUPER::hive_meta_table}, # here we inherit anything from the base class
116 'hive_use_param_stack
' => 1, # switch on the new param_stack mechanism
121 =head2 pipeline_analyses
123 Description : Implements pipeline_analyses() interface method of Bio::EnsEMBL::Hive::PipeConfig::HiveGeneric_conf that defines the structure of the pipeline: analyses, jobs, rules, etc.
124 Here it defines three analyses:
125 * 'take_b_apart
' that is auto-seeded with a pair of jobs (to check the commutativity of multiplication).
126 Each job will dataflow (create more jobs) via branch #2 into 'part_multiply
' and via branch #1 into 'add_together
'.
128 * 'part_multiply
' with jobs fed from take_b_apart#2.
129 It multiplies input parameters 'a_multiplier
' and 'digit
' and dataflows 'partial_product
' parameter into branch #1.
131 * 'add_together
' with jobs fed from take_b_apart#1.
132 It adds together results of partial multiplication computed by 'part_multiply
'.
133 These results are accumulated in 'partial_product
' hash.
134 Until the hash is complete the corresponding 'add_together
' job is blocked by a semaphore.
138 sub pipeline_analyses {
141 { -logic_name => 'take_b_apart
',
143 -meadow_type=> 'LOCAL
', # do not bother the farm with such a simple task (and get it done faster)
144 -analysis_capacity => 2, # use per-analysis limiter
146 { 'a_multiplier
' => '9650156169
', 'b_multiplier
' => '327358788
' },
147 { 'a_multiplier
' => '327358788
', 'b_multiplier
' => '9650156169
' },
151 '#digit#>1
' => [ 'part_multiply
' ], # will create a semaphored fan of jobs; will use param_stack mechanism to pass parameters around
153 'A->1
' => [ 'add_together
' ], # will create a semaphored funnel job to wait for the fan to complete and add the results
157 { -logic_name => 'part_multiply
',
159 -analysis_capacity => 4, # use per-analysis limiter
161 1 => [ '?accu_name=partial_product&accu_address={digit}&accu_input_variable=product
' ],
165 { -logic_name => 'add_together
',
167 # -analysis_capacity => 0, # this is a way to temporarily block a given analysis
169 1 => [ '?table_name=final_result
', 'last
' ],
173 { -logic_name => 'last
',