Difference between revisions of "Nanguiano Week 9"

From LMU BioDB 2015
Jump to: navigation, search
(→‎Coloring a MAPP with expression data: Added information)
(→‎Running MAPPFinder: Added images)
Line 143: Line 143:
 
====Running MAPPFinder====
 
====Running MAPPFinder====
  
−
Note:
+
* After running MAPPFinder, these were my main results:
 +
[[Image:Week9_MAPPFinder_01_Main_NA.png]]
 +
* Opening the biological process dropdown gave this result:
 +
[[Image:Week9_MAPPFinder_BioProc_NA.png]]
 +
* I attempted to open one of the processes in MAPPFinder but obtained the following error:
 +
[[Image:Week9_MAPPFinder_Error_NA.png]]
 +
* Selecting Show Ranked List showed the following result:
 +
[[Image:Week9_MAPPFinder_GO_results_NA.png]]
  
 
== Links ==
 
== Links ==
 
{{Template:Nanguiano}}
 
{{Template:Nanguiano}}

Revision as of 04:37, 17 September 2016

Running GenMAPP Builder

I followed the process from the Running GenMAPP Builder Tutorial Page.

Software

The following software was utilized:

  1. Any tool that can unpack .gz and .zip files
  2. PostgreSQL on Windows (http://www.enterprisedb.com/products-services-training/pgdownload)
  3. GenMAPP Builder version 3.0.0 build 5 (https://github.com/lmu-bioinformatics/xmlpipedb/releases)
  4. Java JDK 1.8 64-bit
  5. GenMAPP 2 can be downloaded here. The file to download is "GenMAPPv2Setup.exe".
  6. XMLPipeDB match utility (https://sourceforge.net/projects/xmlpipedb/files/) for counting IDs in XML files
  7. Microsoft Access or any other tool that can read .mdb files

Quality Assurance

The template for this information was taken from the Gene Database Testing Report Sample Page.

Export Information

Version of GenMAPP Builder: 3.0.0 build 5

Computer on which export was run: Seaver 120-14, HP LV2311 Windows 7 Enterprise

Postgres Database name: V_Cholerae_20160916_gmbuilder03b5

UniProt XML filename (give filename and upload and link to compressed file): uniprot-organism%3A243277.xml

GO OBO-XML filename (give filename and upload and link to compressed file): go_daily-termdb.obo-xml

GOA filename (give filename and upload and link to compressed file): 46.V_cholerae_ATCC_39315.goa

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

  • Time taken to export: 5.15 hours
    • Start time: 09/16/16, 12:26:08 PM
    • End time: 09/16/16, 7:16:23 PM
      • Note: There was a time during the export in which the computer was locked and not running the export, from 2:56pm - 4:19pm.

TallyEngine

  • The procedure for Tally Engine and the rest of the checks is transcribed from How Do I Count Thee? Let me Count The Ways.
  • I ran TallyEngine in GenMAPP Builder to record the number of records for UniProt and GO in the XML data and in the Postgres databases.
    • I chose the menu item Tallies > Run XML and Database Tallies for UniProt and GO...

Tallyengine Vcholerae results NA.png

    • Count for Ordered Locus: 3,831

Using XMLPipeDB match to Validate the XML Results from the TallyEngine

  • After entering into the directory containing the match utility and the uniprot xml file, I ran the command 
java -jar xmlpipedb-match-1.1.1.jar "VC_[0-9][0-9][0-9][0-9]" < uniprot-organism%3A243277.xml
  • It returned a total of 2,738 unique matches.

Xmlpipedb match results NA.png

  • My results were not the same as my results for Tally Engine. Tally Engine returned 3,789 unique matches, while this returned 2,738. This is likely due to potentially due to differently formatted names in the xml file, as we are only checking for names in the structure VC_####.

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

  • Next, I checked the values in SQL to see if they would validate the results from Tally Engine or the match utility.
  • In PgAdminIII, I ran the command: 
select count(*) from genenametype where type = 'ordered locus' and value ~ 'VC_[0-9][0-9][0-9][0-9]';

SQL Query Results NA.png

  • The results were not the same as the ones reported by Tally Engine, nor were they the same as the ones reported by the match utility. It returned 2,737 matches, one less than the result returned by the match utility. While it is less than the Tally Engine perhaps due to a different naming convention, I don't fully understand why it would be off by one from the match utility.

OriginalRowCounts Comparison

  • Within the .gdb file, I looked at the OriginalRowCounts table to see if the database had the expected tables with the expected number of records. I compared it with a benchmark .gdb file.
  • Benchmark .gdb file (2010): Vc-Std_External_20101022
  • Original GDB:
  • Week9 Benchmark gdb tables 1 NA.png
  • Week9 Benchmark gdb tables 2 NA.png
  • New GDB:
  • Week9 New gdb tables 1 NA.png
  • Week9 New gdb tables 2 NA.png
  • The new gdb had 10 additional tables.
  • The have the same number of OrderedLocusNames, 7,664, but most of the other values are different.

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?
    • No. The majority of systems to not have a date included in their date field.
  • 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?
    • The UniProt IDs all look correct.
    • The RefSeq IDs also all look correct.
    • The IDs in OrderedLocusNames appear to take two forms: one which is of the form VC_####, and one of the form VC_A####. This seems to prove the hypothesis that the difference between Tally Engine and the match/SQL results was due to a difference in searched names.
      • To test this, the command java -jar xmlpipedb-match-1.1.1.jar "VC_A?[0-9][0-9][0-9][0-9]" < uniprot-organism%3A243277.xml returns 3,831 unique matches, the same as the Tally Engine. Running the command select count(*) from genenametype where type = 'ordered locus' and value ~ 'VC_A?[0-9][0-9][0-9][0-9'; in SQL also returns 3,831. Therefore, I am decently confident that this was the reason the utilities were returning different results. I am still uncertain as to why SQL returned one less value than the match utility at first, before this new filter.

.gdb Use in GenMAPP

Putting a gene on the MAPP using the GeneFinder window

  • In the main GenMAPP Drafting Board window, left-click on the icon for "Gene" in the upper left corner of the window. Click on the Drafting Board to place the Gene on the MAPP. Now, right-click on the gene to access the GeneFinder window. Type or paste a gene ID into the Gene ID field. Select the appropriate Gene ID system from the drop-down menu and click the Search button.
    • I chose the Gene ID "VC0017" from the "OrderedLocusNames" system.
  • Double-clicking the gene to get the backpage returned the following webpage:

Week9 VC0017 Backpage NA.png

  • All crosslinks that were supposed to be present were present.

Creating an Expression Dataset in the Expression Dataset Manager

  • I selected "Data" then "Expression Dataset Manager". I selected "Expression Dataset" then "New Dataset". I first attempted using the tab-delineated text file I had created last year, but it would not function properly with GenMAPP. I defaulted to using a file I was certain functioned properly, the Merrel compiled raw data from Anu Varshneya's Week 8 Files.
  • No columns contained text, so I selected "Ok", and waited for the raw expression data to be converted.
    • 121 errors were detected in the raw data.
    • All of the error codes in the file stated Gene not found in OrderedLocusNames or any related system.
    • 5,221 total IDs were imported.
    • I checked the UniProt-OrderedLocusNames table for four genes listed as errors: VC2209, VC2338, VCA0595, and VC0284. None of them were found in the table. From this, it can be assumed that the missing genes are not part of the UniPort XML.
  • I typed in "AvgLogFCAll" as the Name of the Color Set, and selected "Avg_LogFC_All" as the gene value.
  • I defined two criteria:
    • Increased: [Avg_LogFC_all] > 0.25 AND [Pvalue] < 0.05, Color: Green
    • Decreased: [Avg_LogFC_all] < -0.25 AND [Pvalue] < 0.05, Color: Red
  • Then, I selected "Expression Datasets" -> "Save".

Coloring a MAPP with expression data

  • I launched the MAPPFinder tool from Tools -> MAPPFinder. Then I selected "Calculate New Results". The .gex file was correct, so I hit "Ok."
  • I selected the color set "AvgLogFCAll", and the Criteria "Increased". I selected the box next to "Gene Ontology" and "Click here to calculate p values".
  • I chose to save the results as "MAPPFinder-Increased-09162016-NA". Then I selected "Run MAPPFinder".

Running MAPPFinder

  • After running MAPPFinder, these were my main results:

Week9 MAPPFinder 01 Main NA.png

  • Opening the biological process dropdown gave this result:

Week9 MAPPFinder BioProc NA.png

  • I attempted to open one of the processes in MAPPFinder but obtained the following error:

Week9 MAPPFinder Error NA.png

  • Selecting Show Ranked List showed the following result:

Week9 MAPPFinder GO results NA.png

Links

Nicole Anguiano
BIOL 367, Fall 2015

Assignment Links
Individual Journals
Shared Journals
Retrieved from "https://xmlpipedb.lmucs.io/biodb/fall2015/index.php?title=Nanguiano_Week_9&oldid=8260"