Difference between revisions of "High-Throughput Phenotyping Database"

From Poland Lab Wiki
Jump to: navigation, search

Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /home/customer/www/wiki.wheatgenetics.k-state.edu/public_html/includes/diff/DairikiDiff.php on line 434

Deprecated: assert(): Calling assert() with a string argument is deprecated in /home/customer/www/wiki.wheatgenetics.k-state.edu/public_html/includes/diff/DairikiDiff.php on line 437
(PheMU HTP Database)
Line 19: Line 19:
 
== PheMU HTP Database  ==
 
== PheMU HTP Database  ==
  
The set of PheMU database tables is shown in the figure below.
+
The diagram below illustrates the set of PheMU database tables and their relationships.
  
 
[[File:Phemu htp.png]]
 
[[File:Phemu htp.png]]

Revision as of 18:53, 17 May 2016

The High-Throughput Phenotyping database consists of a set of platform-specific tables for each data collection platform: pheMU, phenocart and phenocam. Each platform has an images table, an htp table and a run table.

  • The images table stores metadata about the images that were collected during each data collection run.
  • The htp table stores metadata about sensor measurements (observations) that were collected during each run.
  • The run table stores information about each data collection run such as date/time and geographical extent of the run.

Each set of platform-specific tables also relates to the plot_map table and the htp_instrument table.

  • The plot_map table contains information about the geographical coordinates of each plot associated with an experiment (field).
  • The htp_instrument table contains information about cameras and sensors used on each platform.

The diagram below illustrates the generalized set of HTP tables and their relationships.

HTP Database Tables.png

PheMU HTP Database

The diagram below illustrates the set of PheMU database tables and their relationships.

Phemu htp.png

HTP Database Table Structures

phemu_htp table