== Using XMLPipeDB match to Validate the XML Results from the TallyEngine==

== Using XMLPipeDB match to Validate the XML Results from the TallyEngine==

[[How_Do_I_Count_Thee%3F_Let_Me_Count_The_Ways | Follow the instructions found on this page to run XMLPipeDB match.]]

[[How_Do_I_Count_Thee%3F_Let_Me_Count_The_Ways | I followed 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?

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

For more information, [[How_Do_I_Count_Thee%3F_Let_Me_Count_The_Ways | see this page.]]

For more information, [[How_Do_I_Count_Thee%3F_Let_Me_Count_The_Ways | 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:

I looked for counts at the SQL level, using some variation of a ''select count(*)'' query:

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

  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.

In ''pgAdmin III'', I issued 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.

[[Image:Pgadminiii-query.png]]

[[Image:Pgadminiii-query.png]]

==OriginalRowCounts Comparison==

==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.

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

*I got 7664 OrderedLocusNames using the OrigonalRowCounts on Microsoft Access for both .gdb files.

*I got 7664 OrderedLocusNames using the OrigonalRowCounts on Microsoft Access for both .gdb files.

Benchmark .gdb file:

Benchmark .gdb file: