[Bio] / Sprout / LoadSproutTables.pl Repository:
ViewVC logotype

View of /Sprout/LoadSproutTables.pl

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.18 - (download) (as text) (annotate)
Sun Jan 15 21:32:17 2006 UTC (14 years, 2 months ago) by parrello
Branch: MAIN
Changes since 1.17: +7 -3 lines
Converted to the new version of "StandardSetup".

#!/usr/bin/perl -w

=head1 Load Sprout Tables

=head2 Introduction

The Sprout database reflects a snapshot of the SEED taken at a particular point in
time. At some point in the future, it will be possible to add annotations to the
Sprout data. All records added to Sprout after the snapshot is taken are
specially-marked so that the changes can be copied to the SEED. The SEED remains
the live version of the data.

The snapshot is produced by reading the SEED data and writing it to sequential
files. There is one file per Sprout table, and each such file's name consists of
the table name with the suffix C<dtx>. Thus, the file for the C<Genome> table
would be named C<Genome.dtx>. These files are used to load the actual Sprout
database and to generate Glimpse indices.

To load all the Sprout tables and then validate the result, you need to issue three

    LoadSproutTables -dbLoad -dbCreate "*"

All three commands send output to the console. In addition, C<LoadSproutTables> and
C<TestSproutLoad> write tracing information to C<trace.log> in the FIG temporary
directory (B<$FIG_Config::Tmp>). At the bottom of the log file will be a complete
list of errors. If errors occur in C<LoadSproutTables>, then the data must be corrected
and the offending table group reloaded. So, for example, if there are errors in the
load of the B<MadeAnnotation> and B<Compound> tables, you would need to run

    LoadSproutTables -dbLoad Annotation Reaction

because B<MadeAnnotation> is in the C<Annotation> group, and B<Compound> is in the
C<Reaction> group. A list of the groups is given below.

You can omit the C<dbLoad> option to create the load files without
loading the database, and you can add a C<trace> option to change the trace level.
The command below creates the Genome-related load files with a trace level of 3 and
does not load them into the Sprout database.

    LoadSproutTables -trace=3 Genome

C<LoadSproutTables> takes a long time to run, so setting the trace level to 3 helps
to give you an idea of the progress.

Once the Sprout database is loaded, B<TestSproutLoad> can be used to verify the load
against the FIG data. Again, the end of the C<trace.log> file will contain a summary
of the errors found. Like C<LoadSproutTables>, C<TestSproutLoad> is a time-consuming
script, so you may want to set the trace level to 3 to see visible progress.

    TestSproutLoad -trace=3

Unlike C<LoadSproutTables>, in C<TestSproutLoad>, the individual errors found are
mixed in with the trace messages. They are all, however, marked with a trace type
of B<Problem>, as shown in the fragment below.

    11/02/2005 19:15:16 <main>: Processing feature fig|100226.1.peg.7742.
    11/02/2005 19:15:17 <main>: Processing feature fig|100226.1.peg.7741.
    11/02/2005 19:15:17 <Problem>: assignment "Short-chain dehydrodenase ...
    11/02/2005 19:15:17 <Problem>: assignment "putative oxidoreductase." ...
    11/02/2005 19:15:17 <Problem>: Incorrect assignment for fig|100226.1.peg.7741...
    11/02/2005 19:15:17 <Problem>: Incorrect number of annotations found in ...
    11/02/2005 19:15:17 <main>: Processing feature fig|100226.1.peg.7740.
    11/02/2005 19:15:18 <main>: Processing feature fig|100226.1.peg.7739.

The test may reveal that some tables need to be reloaded, or that a software
problem has crept into the Sprout.

Once all the tables have the correct data, C<index_sprout> can be run to create the
Glimpse indexes.

=head2 Procedure For Loading Sprout

=over 4

=item 1

Type C<LoadSproutTables -dbLoad -dbCreate "*"> and press ENTER. This will create
the C<dtx> files and load them.

=item 2

Type C<TestSproutLoad 100226.1 83333.1> and press ENTER. This will validate
the Sprout database against the SEED data.

=item 3

If any errors are detected in step (2), it is most likely due to a change in
SEED that did not make it to Sprout. Contact Bruce Parrello or Robert Olson
to get the code updated properly.

=item 4

Type C<index_sprout> and press ENTER. This will create the Glimpse indexes
for the Sprout data.


=head2 LoadSproutTables Command

C<LoadSproutTables> creates the load files for Sprout tables and optionally loads them.
The parameters are the names of the table groups whose data is to be created.
The legal table group names are given below.

=over 4

=item Genome

Loads B<Genome>, B<HasContig>, B<Contig>, B<IsMadeUpOf>, and B<Sequence>.

=item Coupling

Loads B<Coupling>, B<IsEvidencedBy>, B<PCH>, B<ParticipatesInCoupling>,

=item Feature

Loads B<Feature>, B<FeatureAlias>, B<FeatureTranslation>, B<FeatureUpstream>,
B<IsLocatedIn>, B<FeatureLink>.

=item Subsystem

Loads B<Subsystem>, B<Role>, B<SSCell>, B<ContainsFeature>, B<IsGenomeOf>,
B<IsRoleOf>, B<OccursInSubsystem>, B<ParticipatesIn>, B<HasSSCell>,
B<Catalyzes>, B<ConsistsOfRoles>, B<RoleSubset>, B<HasRoleSubset>,
B<ConsistsOfGenomes>, B<GenomeSubset>, B<HasGenomeSubset>, B<Diagram>,

=item Annotation

Loads B<SproutUser>, B<UserAccess>, B<Annotation>, B<IsTargetOfAnnotation>,

=item Property

Loads B<Property>, B<HasProperty>.

=item BBH

Loads B<IsBidirectionalBestHitOf>.

=item Group

Loads B<GenomeGroups>.

=item Source

Loads B<Source>, B<ComesFrom>, B<SourceURL>.

=item External

Loads B<ExternalAliasOrg>, B<ExternalAliasFunc>.

=item Reaction

Loads B<ReactionURL>, B<Compound>, B<CompoundName>,
B<CompoundCAS>, B<IsAComponentOf>, B<Reaction>.

=item *

Loads all of the above tables.


The command-line options are given below.

=over 4

=item geneFile

The name of the file containing the genomes and their associated access codes. The
file should have one line per genome, each line consisting of the genome ID followed
by the access code, separated by a tab. If no file is specified, all complete genomes
will be processed and the access code will be 1.

=item subsysFile

The name of the file containing the trusted subsystems. The file should have one line
per trusted subsystem. If no file is specified, all subsystems will be trusted.

=item trace

Desired tracing level. The default is 3.

=item dbLoad

If TRUE, the database tables will be loaded automatically from the load files created.

=item dbCreate

If TRUE, the database will be created. If the database exists already, it will be
dropped. Use the function with caution.

=item loadOnly

If TRUE, the database tables will be loaded from existing load files. Load files
will not be created. This option is useful if you are setting up a copy of Sprout
and have load files already set up from the original version.



use strict;
use Tracer;
use DocUtils;
use Cwd;
use FIG;
use SFXlate;
use File::Copy;
use File::Path;
use SproutLoad;
use Stats;
use SFXlate;

# Get the command-line parameters and options.
my ($options, @parameters) = StandardSetup(['SproutLoad', 'ERDBLoad', 'Stats',
                                            'ERDB', 'Load'],
                                            { geneFile => ["", "name of the genome list file"],
                                              subsysFile => ["", "name of the trusted subsystem file"],
                                              dbLoad => [0, "load the database from generated files"],
                                              dbCreate => [0, "drop and re-create the database"],
                                              loadOnly => [0, "load the database from previously generated files"]
                                            "<group1> <group2> ...",
# If we're doing a load-only, turn on loading.
if ($options->{loadOnly}) {
    $options->{dbLoad} = 1
if ($options->{dbCreate}) {
    # Here we want to drop and re-create the database.
    my $db = $FIG_Config::sproutDB;
    if ($FIG_Config::dbms eq "Pg") {
        my $dbport = $FIG_Config::dbport;
        my $dbuser = $FIG_Config::dbuser;
        Trace("Dropping old database (failure is okay).") if T(2);
        system("dropdb -p $dbport -U $dbuser $db");
        Trace("Creating new database.") if T(2);
        &FIG::run("createdb -p $dbport -U $dbuser $db");
    } elsif ($FIG_Config::dbms eq "mysql") {
        Trace("Dropping old database (failure is okay).") if T(2);
        system("mysqladmin -u $FIG_Config::dbuser -p drop $db");
        &FIG::run("mysqladmin -u $FIG_Config::dbuser -p create $db");
        Trace("Creating new database.") if T(2);
# Create the sprout loader object. Note that the Sprout object does not
# open the database unless the "dbLoad" option is turned on.
my $fig = FIG->new();
my $sprout = SFXlate->new_sprout_only(undef, undef, undef, ! $options->{dbLoad});
my $spl = SproutLoad->new($sprout, $fig, $options->{geneFile}, $options->{subsysFile}, $options);
# Insure we have an output directory.
# Process the parameters.
for my $group (@parameters) {
    Trace("Processing load group $group.") if T(2);
    my $stats;
    if ($group eq 'Genome' || $group eq '*') {
    if ($group eq 'Feature' || $group eq '*') {
    if ($group eq 'Coupling' || $group eq '*') {
    if ($group eq 'Subsystem' || $group eq '*') {
    if ($group eq 'Property' || $group eq '*') {
    if ($group eq 'Annotation' || $group eq '*') {
    if ($group eq 'BBH' || $group eq '*') {
    if ($group eq 'Group' || $group eq '*') {
    if ($group eq 'Source' || $group eq '*') {
    if ($group eq 'External' || $group eq '*') {
    if ($group eq 'Reaction' || $group eq '*') {

Trace("Load complete.") if T(2);


MCS Webmaster
ViewVC Help
Powered by ViewVC 1.0.3