Difference between revisions of "Lena Week 9"

From LMU BioDB 2013
Jump to: navigation, search
(Export Information: Note export end time.)
(OriginalRowCounts Comparison)
 
(12 intermediate revisions by one user not shown)
Line 14: Line 14:
  
  
GO OBO-XML filename:
+
GO OBO-XML filename: OBOXML_LH20131022.obo-xml
 
* GO OBO-XML version (The version information can be found in the file properties after the file downloaded from the [http://beta.geneontology.org/page/download-ontology GO Download page] has been unzipped): OBOXML_LH20131022.obo-xml
 
* GO OBO-XML version (The version information can be found in the file properties after the file downloaded from the [http://beta.geneontology.org/page/download-ontology GO Download page] has been unzipped): OBOXML_LH20131022.obo-xml
 
* Time taken to import: 5.96 minutes
 
* Time taken to import: 5.96 minutes
 
* Time taken to process: 4.44 minutes
 
* Time taken to process: 4.44 minutes
  
GOA filename:
+
GOA filename: GOA_LH20131022.goa
 
* GOA version (News on [http://www.ebi.ac.uk/GOA/ this page] records past releases; current information can be found in the Last modified field on the [ftp://ftp.ebi.ac.uk/pub/databases/GO/goa/proteomes/ FTP site]):GOA_LH20131022.goa
 
* GOA version (News on [http://www.ebi.ac.uk/GOA/ this page] records past releases; current information can be found in the Last modified field on the [ftp://ftp.ebi.ac.uk/pub/databases/GO/goa/proteomes/ FTP site]):GOA_LH20131022.goa
 
* Time taken to import: 0.06 minutes
 
* Time taken to import: 0.06 minutes
Line 25: Line 25:
 
Name of .gdb file:VC_LH20131022.gdb
 
Name of .gdb file:VC_LH20131022.gdb
 
* Time taken to export .gdb: time started: 10:34
 
* Time taken to export .gdb: time started: 10:34
* Upload your file and link to it here.
+
* Upload your file and link to it here. [[Media:VC_LH20131022.gdb]]
  
 
Note: Export ended 12:10:26 pm.
 
Note: Export ended 12:10:26 pm.
Line 32: Line 32:
  
 
Run the TallyEngine in GenMAPP Builder and record the number of records for UniProt and GO in the XML data and in the PostgreSQL databases (or you can upload and link to a screenshot of the results).
 
Run the TallyEngine in GenMAPP Builder and record the number of records for UniProt and GO in the XML data and in the PostgreSQL databases (or you can upload and link to a screenshot of the results).
 +
:
 +
[[Image:Tallyresults.PNG]]
  
 
== Using XMLPipeDB match to Validate the XML Results from the TallyEngine==
 
== Using XMLPipeDB match to Validate the XML Results from the TallyEngine==
Line 38: Line 40:
  
 
Are your results the same as you got for the TallyEngine?  Why or why not?
 
Are your results the same as you got for the TallyEngine?  Why or why not?
 +
:
 +
At first, no, because we did not account for the possibility of an A in the name. (TCA-####)
 +
 +
[[Image:Matches.PNG]]
 +
:We ran the search again, accounting for the A, and got the same number.
 +
[[Image:Matches2.PNG]]
  
 
== Using SQL Queries to Validate the PostgreSQL Database Results from the TallyEngine==
 
== Using SQL Queries to Validate the PostgreSQL Database Results from the TallyEngine==
Line 50: Line 58:
  
 
Copy the OriginalRowCounts table and paste it here:
 
Copy the OriginalRowCounts table and paste it here:
 +
:
 +
:[[Image:Originalrowcounts.PNG]] [[Image:Externaloriginalrowcount.PNG]]
  
Note:
+
Note: There are a lot more matched for Gene Ontology in the more recent one, and more matches with Uniprot.  It makes sense for the more recent one to be more comprehensive because it has all the data that has been collected since the last one was updated.
  
 
==Visual Inspection==
 
==Visual Inspection==
Line 96: Line 106:
  
 
===GOA===
 
===GOA===
 +
 +
Electronic Journal by [[user:Lena|Lena Hunt]]

Latest revision as of 01:22, 26 October 2013

Contents

[edit] Download and Extract Data Source Files

[edit] Export Information

Version of GenMAPP Builder: 2.0 Beta 70

Computer on which export was run: front row, furthest computer to the right

Postgres Database name: VibrioCholera_LH20131022_GMB2B70

UniProt XML filename: Uniprot_LH20131022.xml

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


GO OBO-XML filename: OBOXML_LH20131022.obo-xml

  • 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): OBOXML_LH20131022.obo-xml
  • Time taken to import: 5.96 minutes
  • Time taken to process: 4.44 minutes

GOA filename: GOA_LH20131022.goa

  • GOA version (News on this page records past releases; current information can be found in the Last modified field on the FTP site):GOA_LH20131022.goa
  • Time taken to import: 0.06 minutes

Name of .gdb file:VC_LH20131022.gdb

Note: Export ended 12:10:26 pm.

[edit] TallyEngine

Run the TallyEngine in GenMAPP Builder and record the number of records for UniProt and GO in the XML data and in the PostgreSQL databases (or you can upload and link to a screenshot of the results).

Tallyresults.PNG

[edit] 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?

At first, no, because we did not account for the possibility of an A in the name. (TCA-####)

Matches.PNG

We ran the search again, accounting for the A, and got the same number.

Matches2.PNG

[edit] Using SQL Queries to Validate the PostgreSQL Database Results from the TallyEngine

Follow the instructions on this page to query the PostgreSQL Database.

[edit] 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: (for the Week 9 Assignment, use the "Vc-Std_External_20101022.gdb" as your benchmark, downloadable from here.

Copy the OriginalRowCounts table and paste it here:

Originalrowcounts.PNG Externaloriginalrowcount.PNG

Note: There are a lot more matched for Gene Ontology in the more recent one, and more matches with Uniprot. It makes sense for the more recent one to be more comprehensive because it has all the data that has been collected since the last one was updated.

[edit] 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:

[edit] .gdb Use in GenMAPP

Note:

[edit] 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:

[edit] 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:

[edit] Coloring a MAPP with expression data

Note:

[edit] Running MAPPFinder

Note:

[edit] 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:


[edit] GOA

Electronic Journal by Lena Hunt

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox