XSD Documentation


posted Oct 14, 2009, 1:21 PM by Quan Tang   [ updated Oct 14, 2009, 1:24 PM ]

In paramRestDef, the refIDs show the IDs in the original model, which are to be combined into a new parameter (like a, b, g in source monitoring experiments), and the parameterString shows the new parameter name.

Therefore, we will have as many paramRestDef nodes as the new parameters that combined from original model nodes.


posted Oct 14, 2009, 12:56 PM by Quan Tang   [ updated Oct 14, 2009, 12:59 PM ]

As well, we use refID to express the ID of the ending nodes of each branch, and use category to show the observed categories of these ending nodes respectively.


posted Oct 14, 2009, 12:55 PM by Quan Tang   [ updated Oct 14, 2009, 1:00 PM ]

In treeDef, we use refID to denote the root ID of a tree, and frequency to the total frequency observed in this certain tree.


posted Oct 14, 2009, 12:17 PM by Xiangen Hu

The main part of the original model is the source trees. For instance, in a typical source monitoring experiment, we may have source trees A, B and N. Moreover, the nodes under a tree denotes the processing steps and their sequential relationship.

Main Structure

posted Oct 5, 2009, 9:15 AM by Quan Tang   [ updated Oct 14, 2009, 8:50 AM ]

 Main Structure
of the project shows the three basic parts of the project: originalModel, subModel, and dataSets.

Original Model

posted Oct 5, 2009, 9:14 AM by Quan Tang   [ updated Oct 14, 2009, 12:19 PM by Xiangen Hu ]

Original Model is a collection of trees. It is used to represent the structure of the original processing tree model in which no parameters or branches are combined. In other words, every single step/node in the tree has a unique parameter name.

Sub Model

posted Oct 5, 2009, 9:10 AM by Quan Tang   [ updated Oct 14, 2009, 1:26 PM ]

Sub Model  represents the sub models we intend to test. In this part, we use treeDef to define the root node of each processing tree and use  nodeDef to define the ending nodes paired with their categories respectively. As well, we recruit paramRestDef to define the nodes that share a same parameter in the sub model. Please note that we can have more than one sub models here if we merely create another set of these definitions without indicating the tree structure/nodes' relation that has already been fixed in the original model.

Data Sets

posted Oct 5, 2009, 9:09 AM by Quan Tang   [ updated Oct 14, 2009, 9:21 AM ]

Data Sets store the frequencies observed in an experiment. These frequencies are stored according to the source trees they belong to. In dataSets, we use observedData node to denote the data observed in the experiments, within which the TreeRootID shows the source tree that contains these data, and the DataCells contains the contingency table of the data according to their category names and the observed frequencies respectively. For example, in a source monitoring experiment that contain source tree A, B and N, we will have a 3*3 contingency table. Therefore, we will have three observedDate nodes for three source trees, and three DataCells for each tree indicating their responses in each category respectively.

1-8 of 8