|
|
Line 1: |
Line 1: |
− | [http://www.wormbase.org/wiki/index.php/Caltech_documentation back]
| |
| | | |
− | = Dumping Phenote into .ace file =
| |
− |
| |
− | Connect to tazendra
| |
− |
| |
− | : ssh acedb@tazendra.caltech.edu
| |
− | Pswd
| |
− | : cd /home/acedb/work/allele_phenotype
| |
− | : ls //will see previous .ace files ‘allele_phenotype.ace.<date>', 'err.out.<date>', and dump script use_package.pl*
| |
− | : ./use_package.pl //dump info into .ace file//
| |
− |
| |
− | New allele_phenotype.ace and err.out files will be created as noted by date at the end of each name. <br>
| |
− | Note err.out to see if any errors were generated during the dump process. <br>
| |
− | Errors in .ace file should be indicated by "ERROR" in the .ace output, or as comments at the top of the form.<br>
| |
− | Over time these dump files will add up, so need to clean it up from time to time.<br>
| |
− |
| |
− | Copy allele_phenotype.ace to your local computer
| |
− | : scp allele_phenotype.ace.2008XX yook@scoobydoo.caltech.edu:/WS_acedump
| |
− |
| |
− | Script obsolete.pl is left over from phenotype CGI .ace dump instructions.<br>
| |
− | It made sure there were no obsolete phenotype annotations in the .ace file<br>
| |
− | /home/Postgres/work/citace_upload/allele_phenotype/obsolete.pl<br>
| |
− | --[[User:Kyook|kjy]] 02:20, 29 July 2010 (UTC)
| |
− |
| |
− | = 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 on altair or spika ==
| |
− |
| |
− | Send new allele_phenotype.ace to kyook on altair:
| |
− | : scp <.ace dump files> kyook@altair.caltech.edu:/home3/kyook/alle_phen.ace.latest
| |
− |
| |
− | == 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
| |
− | #Number '''strain objects'''
| |
− | #Number '''life stage objects'''
| |
− | #Number '''anatomy terms'''
| |
− | #Number '''alleles linked to phenotype terms:'''
| |
− | use either AQL query
| |
− | select all class variation where exists_tag ->phenotype
| |
− | select a, a-> variation from a in class phenotype where exists_tag a ->variation
| |
− | Number '''variations that are alleles:'''
| |
− | use WQL
| |
− | find variation variation_type=allele
| |
− |
| |
− | 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’
| |
− |
| |
− | 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.
| |
− |
| |
− | = Uploading .ace for Wen into Citace =
| |
− |
| |
− | Deposit .ace for Wen in citace:
| |
− | scp XXXXX citace@altair:~/Data_for_citace/Data_from_<YOU> /home/citace/Data_for_citace/Data_from_<YOU>/ <allele_phenotype_dump_WSxxx.ace>
| |