Technical data

Phoenix Concepts

Phoenix Work Concepts

» User-created worksheets and workbooks.

» Worksheets that are the results of operational objects.

How is data used in Phoenix?

» The Data folder contains all the imported or created data sets that are used

in a project.

» All data sets used in a workflow are contained internally within Phoenix.

» Changes made to imported data sets do not change the original data set.

» Data must be mapped to an operational object before it can be used.

Data mapping

Data mapping is the process of associating a data set 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 data set from the Data folder to an object’s

input, or using the Select Object dialog to select a data set.

There are two types of data mapping in Phoenix: mapping data to an object, and

mapping the variables or parameters in the data set to an object’s contexts.

Mapping to an object:

» Data sets 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 to a context:

» Context mapping is the process of linking a specific column in a data set 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 data set with

contexts in an operational object.

– For example, Phoenix can be set to automatically map a concentration

column named conc to an operational object’s concentration context.