Data mapping is the process of associating a dataset with an operational object so that objects can use the data in an analysis or other function. Data mapping in Phoenix is as simple as dragging a dataset from the Data folder to an object’s input, or using the Select Object dialog to select a dataset.
There are multiple types of data mapping in Phoenix:
-
Mapping a dataset to an operational object: Datasets can be mapped to the different panels in an object’s Setup list, or they can be mapped to an object’s inputs in the Diagram tab.
-
Mapping context associations: Context mapping is the process of linking a specific column in a dataset to a specific context in an operational object, such as Time or Concentration.
Phoenix can complete context mappings if a column header in a worksheet matches the context name in an operational object. The Global Contexts and Context Association panels in the Preferences dialog can be used to automatically associate columns in a dataset with contexts in an operational object. For example, Phoenix can be set to map a concentration column named conc to an operational object’s concentration context.
Mapping a dataset to an operational object
Every operational object includes a data input panel in the Setup tab that is used to identify how input variables are used in an operational object.
Most primary data input panels contain two tabs: the Mapping tab (where dataset columns are mapped to an object’s inputs) and a sort order tab (allows users to sort dataset columns). The Table, NONMEM, PsN, R, SAS, and SigmaPlot objects only have a Mappings panel.
Users can map a dataset or other worksheet to almost any item in the Setup tab list using the instructions listed below. Note that the R and SAS Shell objects must have a script mapped to them before their inputs are defined. The PsN Shell object must have at least one model mapped to it before the input can be defined.
To map a dataset using the data mappings panel
In the data mappings panel, click 
(Show Sources icon).
In the dialog, click the (+) sign next to the Data folder.
Select a dataset and click Select.
Or use the pointer to drag a dataset from the Data folder to the Mappings panel.
To map a dataset using the Diagram tab
Select the Workflow object in the Object Browser.
In the Diagram tab, click 
to expand the object box.
Click the (+) sign next to Inputs.
Drag the dataset from the Data folder to the primary data input.
The line between the External Sources box and the object box represents the data mapping.
To map a dataset using the “Send To” menu option
Select the object in the Object Browser to return to the Setup tab.
Right-click an imported worksheet and select Send To > <object group> > <operational object>.
The Send To command inserts the new object into the Workflow with the right-clicked worksheet already mapped as the input source.
Mapping results to an operational object
The results worksheet of any operational object can also be mapped to another operational object.
To map results from the Setup tab
Click 
(Select Source icon) in the operational object’s Setup tab.
In the dialog, click the (+) signs to expand the menu tree.
Select the results worksheet and click Select.
To map results from the worksheet
Right-click a results worksheet and select Send To > <object group> > <operational object>.
Context associations are inputs to an operational object. Contexts that must have data mapped to them so the object can perform its function are shaded orange. Most items in an operational object’s Setup list have a Mappings panel that allows users to match columns in a dataset to inputs in an operational object.
Column headers in the dataset are displayed on the left side and context associations for the operational object are displayed across the top.
Context associations for NCA model 200
Select the option button to connect the input dataset column containing the data (row) to the corresponding context (column).
Repeat for each item in the Setup tab list that requires mapping data to inputs.
