Difference between revisions of "Phenote .ace citace upload"

From WormBaseWiki
Jump to navigationJump to search
Line 1: Line 1:
[http://www.wormbase.org/wiki/index.php/Caltech_documentation back]
+
[http://www.wormbase.org/wiki/index.php/Caltech_documentation back]  
  
 
= Dumping Phenote into .ace file  =
 
= Dumping Phenote into .ace file  =
Line 6: Line 6:
  
 
  : ssh  acedb@tazendra.caltech.edu
 
  : ssh  acedb@tazendra.caltech.edu
 
+
Pswd
Pswd <span class="Apple-style-span" style="line-height: 16px;">cd /home/acedb/work/allele_phenotype  
+
<span class="Apple-style-span" style="line-height: 16px;">cd /home/acedb/work/allele_phenotype  
</span>
+
: ./use_package.pl </span>
 
+
::
:./use_package.pl  
 
:
 
  
 
Can open err.out to see if any errors were generated during the dump process. Errors should be indicated at the top of the form.  
 
Can open err.out to see if any errors were generated during the dump process. Errors should be indicated at the top of the form.  
Line 18: Line 16:
  
 
  : scp allele_phenotype.ace.20080407 yook@scoobydoo.caltech.edu:/Users/Yook/WS_latest/ace_dump/var_phen.ace
 
  : scp allele_phenotype.ace.20080407 yook@scoobydoo.caltech.edu:/Users/Yook/WS_latest/ace_dump/var_phen.ace
pswd  
+
pswd
 
+
 
<br>
 
  
 
&lt;left over from CGI .ace dump instructions&gt;&nbsp;  
 
&lt;left over from CGI .ace dump instructions&gt;&nbsp;  
  
Make sure that there are no obsolete phenotype annotations: - Script for finding obsolete terms is find_obsolete.pl at path listed below on tazendra: /home/Postgres/work/citace_upload/allele_phenotype/
+
Make sure that there are no obsolete phenotype annotations: - Script for finding obsolete terms is find_obsolete.pl at path listed below on tazendra: /home/Postgres/work/citace_upload/allele_phenotype/  
 
 
= Testing Phenote .ace for upload =
 
 
 
Evaluate how the uploaded data impacts WB by comparing object numbers before and after data upload. This means that you need access to the latest WS and have the means to edit the WS to read the .ace dump.
 
  
 +
= Testing Phenote .ace for upload  =
  
 +
Evaluate how the uploaded data impacts WB by comparing object numbers before and after data upload. This means that you need access to the latest WS and have the means to edit the WS to read the .ace dump.<br>
  
 
== Test file locally on Acedb  ==
 
== Test file locally on Acedb  ==
Line 46: Line 41:
 
#Number '''life stage objects'''  
 
#Number '''life stage objects'''  
 
#Number '''anatomy terms'''  
 
#Number '''anatomy terms'''  
#Number '''allele-phenotype connection'''
+
#Number '''variation''''''-phenotype connection'''
  
  use either AQL query
+
  use either AQL query:
 
select all class variation where exists_tag -&gt;phenotype
 
select all class variation where exists_tag -&gt;phenotype
 
select p, p-&gt; variation from p in class phenotype where exists_tag p-&gt;variation
 
select p, p-&gt; variation from p in class phenotype where exists_tag p-&gt;variation
Line 68: Line 63:
 
  select v from v in class variation where exists_tag v-&gt;phenotype
 
  select v from v in class variation where exists_tag v-&gt;phenotype
  
Checking that the .ace dump file is readable: Load in .ace dump Hit ‘Edit..‘ button Choose ‘Read .ace file’ Accept change in write priviledges Select ‘Open ace file’ Find and select file to open Select ‘Read all’  
+
Check that the .ace dump file is readable:  
 +
 
 +
to load in .ace dump  
 +
 
 +
Select ‘Edit..‘ ‘Read .ace file’, &nbsp;Accept change in write privileges, &nbsp;Select ‘Open ace file’, &nbsp;Find and select file to open, &nbsp;Select ‘Read all’  
  
 
If the .ace file is okay, then 100% of the lines will have been read in. This will be noted in the second line called ‘Line:’. If the dump produced a bad file, the read in will stop at the point where the problem occurred. You can go to that line in the .ace file and check it out.  
 
If the .ace file is okay, then 100% of the lines will have been read in. This will be noted in the second line called ‘Line:’. If the dump produced a bad file, the read in will stop at the point where the problem occurred. You can go to that line in the .ace file and check it out.  
  
Checking that the file does not alter any objects it shouldn’t: Once .ace dump loaded in redo counts for all objects as above. Compare object numbers between latest database and new .ace file to make sure data in the dump looks reasonable, i.e., no lost data or inflated numbers.
+
Check that the file does not alter any objects it shouldn’t:  
 +
 
 +
Once .ace dump is loaded in to acedb, &nbsp;redo counts for all objects as above. Compare object numbers between latest database and new .ace file to make sure data in the dump looks reasonable, i.e., no lost data or inflated numbers.  
  
 
= Uploading .ace for Wen into Citace  =
 
= Uploading .ace for Wen into Citace  =

Revision as of 21:55, 22 April 2008

back

Dumping Phenote into .ace file

The phenote-> .ace dump script is called ./use_package.pl and is on tazendra in /home/acedb/work/allele_phenotype. This script takes about 10 minutes and will create two files: ‘allele_phenotype.ace.<date> and err.out.<date>. NOTE: these files will accumulate over time so make sure to clear them out every once in a while.

: ssh  acedb@tazendra.caltech.edu

Pswd cd /home/acedb/work/allele_phenotype

./use_package.pl

Can open err.out to see if any errors were generated during the dump process. Errors should be indicated at the top of the form.

New allele_phenotype.ace and err.out files will be created as noted by date at the end of each. Send them to your computer e.g. ace_dump on scoobydoo changing name to var_phen.ace:

: scp allele_phenotype.ace.20080407 yook@scoobydoo.caltech.edu:/Users/Yook/WS_latest/ace_dump/var_phen.ace

pswd


<left over from CGI .ace dump instructions> 

Make sure that there are no obsolete phenotype annotations: - Script for finding obsolete terms is find_obsolete.pl at path listed below on tazendra: /home/Postgres/work/citace_upload/allele_phenotype/

Testing Phenote .ace for upload

Evaluate how the uploaded data impacts WB by comparing object numbers before and after data upload. This means that you need access to the latest WS and have the means to edit the WS to read the .ace dump.

Test file locally on Acedb

This step is to test two things: First, that the file is readable. Second, that the file does not alter any objects it shouldn’t.

Launch local acedb:

$ cd Desktop/acedb

$ ./xace /Users/Yook/WS_latest/WS188

Comparing data builds: From the latest build, record

  1. Number strain objects
  2. Number life stage objects
  3. Number anatomy terms
  4. Number variation'-phenotype connection'
use either AQL query:

select all class variation where exists_tag ->phenotype select p, p-> variation from p in class phenotype where exists_tag p->variation

5. Number variations that are alleles:

use WQL

find variation variation_type=allele

or AQL

select a from a in class variation where exists_tag a->allele 
6. Number alleles with a phenotype

Find all alleles with a phenotype

select v from v in class variation where exists_tag v->phenotype

Check that the .ace dump file is readable:

to load in .ace dump

Select ‘Edit..‘ ‘Read .ace file’,  Accept change in write privileges,  Select ‘Open ace file’,  Find and select file to open,  Select ‘Read all’

If the .ace file is okay, then 100% of the lines will have been read in. This will be noted in the second line called ‘Line:’. If the dump produced a bad file, the read in will stop at the point where the problem occurred. You can go to that line in the .ace file and check it out.

Check that the file does not alter any objects it shouldn’t:

Once .ace dump is loaded in to acedb,  redo counts for all objects as above. Compare object numbers between latest database and new .ace file to make sure data in the dump looks reasonable, i.e., no lost data or inflated numbers.

Uploading .ace for Wen into Citace

Deposit .ace for Wen in citace:

scp var_phen.ace citace@spica.caltech.edu:/home/citace/Data_for_citace/Data_from_Karen