Difference between revisions of "Kzebrows Week 9"

From LMU BioDB 2015
Jump to: navigation, search
(Create page and copy/paste Gene Database Testing Report)
 
(Template and category additions)
Line 1: Line 1:
 
==Electronic Lab Notebook==
 
==Electronic Lab Notebook==
Export of ''Vibrio cholerae'' GenMAPP Gene Database was used following the instructions on the [https://xmlpipedb.cs.lmu.edu/biodb/fall2015/index.php/Week_9 Week 9] assignment page. The Gene Database Testing Report we used was found [https://xmlpipedb.cs.lmu.edu/biodb/fall2015/index.php/Gene_Database_Testing_Report_Sample here].
+
Export of ''Vibrio cholerae'' GenMAPP Gene Database was used following the instructions on the [https://xmlpipedb.cs.lmu.edu/biodb/fall2015/index.php/Week_9 Week 9] assignment page. The Gene Database Testing Report template we used was found [https://xmlpipedb.cs.lmu.edu/biodb/fall2015/index.php/Gene_Database_Testing_Report_Sample here].
  
 
==Export Information==
 
==Export Information==
Line 112: Line 112:
  
 
Note:
 
Note:
 +
 +
{{Template:Kzebrows}}
 +
[[Category : Journal Entry]]

Revision as of 21:56, 27 October 2015

Electronic Lab Notebook

Export of Vibrio cholerae GenMAPP Gene Database was used following the instructions on the Week 9 assignment page. The Gene Database Testing Report template we used was found here.

Export Information

Version of GenMAPP Builder:

Computer on which export was run:

Postgres Database name:

UniProt XML filename (give filename and upload and link to compressed file):

  • UniProt XML version (The version information can be found at the UniProt News Page):
  • UniProt XML download link:
  • Time taken to import:
    • Note:

GO OBO-XML filename (give filename and upload and link to compressed file):

  • GO OBO-XML version (The version information can be found in the file properties after the file downloaded from the GO Download page has been unzipped):
  • GO OBO-XML download link:
  • Time taken to import:
  • Time taken to process:
    • Note:

GOA filename (give filename and upload and link to compressed file):

  • GOA version (News on this page records past releases; current information can be found in the Last modified field on the FTP site):
  • GOA download link:
  • Time taken to import:
    • Note:

Name of .gdb file (give filename and upload and link to compressed file):

  • Time taken to export:
    • Start time:
    • End time:

Note:

TallyEngine

  • Run the TallyEngine in GenMAPP Builder and record the number of records for UniProt and GO in the XML data and in the Postgres databases.
    • Choose the menu item Tallies > Run XML and Database Tallies for UniProt and GO...
    • Take a screenshot of the results. Upload the image to the wiki and display it on this page.
    • For more information, see this page.

Using XMLPipeDB match to Validate the XML Results from the TallyEngine

Follow the instructions found on this page to run XMLPipeDB match.

Are your results the same as you got for the TallyEngine? Why or why not?

Using SQL Queries to Validate the PostgreSQL Database Results from the TallyEngine

For more information, see this page.

You can also look for counts at the SQL level, using some variation of a select count(*) query. This requires some knowledge of which table received what data. Here’s an initial tip: the gene/name tags in the XML file land in the genenametype table. A query on this table counting values from this table that were marked as ordered locus in the XML file matching the pattern VC_[0-9][0-9][0-9][0-9] would look like this:

select count(*) from genenametype where type = 'ordered locus' and value ~ 'VC_[0-9][0-9][0-9][0-9]';

In pgAdmin III, you can issue these queries by clicking on the pencil/SQL icon in the toolbar, typing the query into the SQL Editor tab, then clicking on the green triangular Play button to run.

Pgadminiii-query.png

Are your results the same as reported by the TallyEngine? Why or why not?

OriginalRowCounts Comparison

Within the .gdb file, look at the OriginalRowCounts table to see if the database has the expected tables with the expected number of records. Compare the tables and records with a benchmark .gdb file.

Benchmark .gdb file:

Copy the OriginalRowCounts table from the benchmark and new gdb and paste them here:

Note:

Visual Inspection

Perform visual inspection of individual tables to see if there are any problems.

  • Look at the Systems table. Is there a date in the Date field for all gene ID systems present in the database?
  • Open the UniProt, RefSeq, and OrderedLocusNames tables. Scroll down through the table. Do all of the IDs look like they take the correct form for that type of ID?

Note:

.gdb Use in GenMAPP

Note:

Putting a gene on the MAPP using the GeneFinder window

  • Try a sample ID from each of the gene ID systems. Open the Backpage and see if all of the cross-referenced IDs that are supposed to be there are there.

Note:

Creating an Expression Dataset in the Expression Dataset Manager

  • How many of the IDs were imported out of the total IDs in the microarray dataset? How many exceptions were there? Look in the EX.txt file and look at the error codes for the records that were not imported into the Expression Dataset. Do these represent IDs that were present in the UniProt XML, but were somehow not imported? or were they not present in the UniProt XML?

Note:

Coloring a MAPP with expression data

Note:

Running MAPPFinder

Note:


Compare Gene Database to Outside Resource

The OrderedLocusNames IDs in the exported Gene Database are derived from the UniProt XML. It is a good idea to check your list of OrderedLocusNames IDs to see how complete it is using the original source of the data (the sequencing organization, the MOD, etc.) Because UniProt is a protein database, it does not reference any non-protein genome features such as genes that code for functional RNAs, centromeres, telomeres, etc.

Note:


Assignments

Individual Journal Assignment Pages

Week 1
Week 2
Week 3
Week 4
Week 5
Week 6
Week 7
Week 8
Week 9
Week 10
Week 11
Week 12
Week 14
Week 15

Individual Journal Assignments

Kzebrows Week 1
Kzebrows Week 2
Kzebrows Week 3
Kzebrows Week 4
Kzebrows Week 5
Kzebrows Week 6
Kzebrows Week 7
Kzebrows Week 8
Kzebrows Week 9
Kzebrows Week 10
Kzebrows Week 11
Kzebrows Week 12
Kzebrows Week 14
Kzebrows Week 15
Final Individual Reflection

Shared Journal Assignments

Class Journal Week 1
Class Journal Week 2
Class Journal Week 3
Class Journal Week 4
Class Journal Week 5
Class Journal Week 6
Class Journal Week 7
Class Journal Week 8
Class Journal Week 9
Oregon Trail Survivors Week 10
Oregon Trail Survivors Week 11
Oregon Trail Survivors Week 12
Oregon Trail Survivors Week 14

Additional Links

User Page: Kristin Zebrowski
Class Page: BIOL/CMSI 367-01
Team Page: Oregon Trail Survivors