Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
E
ensembl
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Iterations
Wiki
Requirements
Jira
Code
Merge requests
1
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
Commits
3163615b
Commit
3163615b
authored
13 years ago
by
Andy Yates
Browse files
Options
Downloads
Patches
Plain Diff
Forgot about the registry option given to the command line
parent
737a041c
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
docs/pipelines/fasta.html
+11
-7
11 additions, 7 deletions
docs/pipelines/fasta.html
docs/pipelines/fasta.markdown
+11
-8
11 additions, 8 deletions
docs/pipelines/fasta.markdown
with
22 additions
and
15 deletions
docs/pipelines/fasta.html
+
11
−
7
View file @
3163615b
...
...
@@ -80,6 +80,8 @@ Bio::EnsEMBL::Registry->no_cache_warnings(1);
1;
</code></pre>
<p>
You give the registry to the
<strong>
init_pipeline.pl
</strong>
script via the
<strong>
-registry
</strong>
option
</p>
<h2
id=
"overriding_defaults_using_a_new_config_file"
>
Overriding Defaults Using a New Config File
</h2>
<p>
We recommend if you have a number of parameters which do not change
...
...
@@ -102,6 +104,8 @@ sub default_options {
1;
</code></pre>
<p>
If you do override the config then you should use the package name for your overridden config in the upcoming example commands.
</p>
<h2
id=
"environment"
>
Environment
</h2>
<h3
id=
"perl5lib"
>
PERL5LIB
</h3>
...
...
@@ -125,42 +129,42 @@ sub default_options {
<h3
id=
"to_load_use_normally"
>
To load use normally:
</h3>
<pre><code>
init_pipeline.pl Bio::EnsEMBL::Pipeline::PipeConfig:FASTA_conf \
-pipeline_db -host=my-db-host -base_path /path/to/dumps
-pipeline_db -host=my-db-host -base_path /path/to/dumps
-registry reg.pm
</code></pre>
<h3
id=
"run_a_subset_of_species_no_forcing_supports_registry_aliases"
>
Run a subset of species (no forcing
&
supports registry aliases):
</h3>
<pre><code>
init_pipeline.pl Bio::EnsEMBL::Pipeline::PipeConfig:FASTA_conf \
-pipeline_db -host=my-db-host -species anolis -species celegans -species human \
-base_path /path/to/dumps
-base_path /path/to/dumps
-registry reg.pm
</code></pre>
<h3
id=
"specifying_species_to_force_supports_all_registry_aliases"
>
Specifying species to force (supports all registry aliases):
</h3>
<pre><code>
init_pipeline.pl Bio::EnsEMBL::Pipeline::PipeConfig:FASTA_conf \
-pipeline_db -host=my-db-host -force_species anolis -force_species celegans -force_species human \
-base_path /path/to/dumps
-base_path /path/to/dumps
-registry reg.pm
</code></pre>
<h3
id=
"running_forcing_a_species"
>
Running
&
forcing a species:
</h3>
<pre><code>
init_pipeline.pl Bio::EnsEMBL::Pipeline::PipeConfig:FASTA_conf \
-pipeline_db -host=my-db-host -species celegans -force_species celegans \
-base_path /path/to/dumps
-base_path /path/to/dumps
-registry reg.pm
</code></pre>
<h3
id=
"dumping_just_gene_data"
>
Dumping just gene data:
</h3>
<h3
id=
"dumping_just_gene_data
_no_dna_or_ncrna
"
>
Dumping just gene data
(no DNA or ncRNA)
:
</h3>
<pre><code>
init_pipeline.pl Bio::EnsEMBL::Pipeline::PipeConfig:FASTA_conf \
-pipeline_db -host=my-db-host -dump_type cdna \
-base_path /path/to/dumps
-base_path /path/to/dumps
-registry reg.pm
</code></pre>
<h3
id=
"using_a_different_scp_user_identity"
>
Using a different SCP user
&
identity:
</h3>
<pre><code>
init_pipeline.pl Bio::EnsEMBL::Pipeline::PipeConfig:FASTA_conf \
-pipeline_db -host=my-db-host -scp_user anotherusr -scp_identity /users/anotherusr/.pri/identity \
-base_path /path/to/dumps
-base_path /path/to/dumps
-registry reg.pm
</code></pre>
<h2
id=
"running_the_pipeline"
>
Running the Pipeline
</h2>
...
...
This diff is collapsed.
Click to expand it.
docs/pipelines/fasta.markdown
+
11
−
8
View file @
3163615b
...
...
@@ -73,6 +73,8 @@ change to version here must be reflected in the configuration file.
1;
You give the registry to the
**init_pipeline.pl**
script via the
**-registry**
option
## Overriding Defaults Using a New Config File
We recommend if you have a number of parameters which do not change
...
...
@@ -94,6 +96,8 @@ root config file e.g.
1;
If you do override the config then you should use the package name for your overridden config in the upcoming example commands.
## Environment
### PERL5LIB
...
...
@@ -113,38 +117,37 @@ root config file e.g.
### To load use normally:
init_pipeline.pl Bio::EnsEMBL::Pipeline::PipeConfig:FASTA_conf \
-pipeline_db -host=my-db-host -base_path /path/to/dumps
-pipeline_db -host=my-db-host -base_path /path/to/dumps
-registry reg.pm
### Run a subset of species (no forcing & supports registry aliases):
init_pipeline.pl Bio::EnsEMBL::Pipeline::PipeConfig:FASTA_conf \
-pipeline_db -host=my-db-host -species anolis -species celegans -species human \
-base_path /path/to/dumps
-base_path /path/to/dumps
-registry reg.pm
### Specifying species to force (supports all registry aliases):
init_pipeline.pl Bio::EnsEMBL::Pipeline::PipeConfig:FASTA_conf \
-pipeline_db -host=my-db-host -force_species anolis -force_species celegans -force_species human \
-base_path /path/to/dumps
-base_path /path/to/dumps
-registry reg.pm
### Running & forcing a species:
init_pipeline.pl Bio::EnsEMBL::Pipeline::PipeConfig:FASTA_conf \
-pipeline_db -host=my-db-host -species celegans -force_species celegans \
-base_path /path/to/dumps
-base_path /path/to/dumps
-registry reg.pm
### Dumping just gene data:
### Dumping just gene data
(no DNA or ncRNA)
:
init_pipeline.pl Bio::EnsEMBL::Pipeline::PipeConfig:FASTA_conf \
-pipeline_db -host=my-db-host -dump_type cdna \
-base_path /path/to/dumps
-base_path /path/to/dumps
-registry reg.pm
### Using a different SCP user & identity:
init_pipeline.pl Bio::EnsEMBL::Pipeline::PipeConfig:FASTA_conf \
-pipeline_db -host=my-db-host -scp_user anotherusr -scp_identity /users/anotherusr/.pri/identity \
-base_path /path/to/dumps
-base_path /path/to/dumps -registry reg.pm
## Running the Pipeline
...
...
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