Fixed Effects sub-tab

The Fixed Effects tab allows entering initial, lower bound, and upper bound values for the fixed effects. Every selection made in the Structural tab changes the code for the modified structural parameter. These code changes are displayed in the Model Text tab.

phenoEmaxFixedEffectstab

Entering lower and upper bound values for the fixed effects are optional. (See the “Using upper and/or lower bounds” section below for additional information.)

For each fixed effect, enter an Initial value, a Lower limit value, and an Upper limit value, if needed, in the corresponding field.

Check the Freeze checkbox to fix the parameter estimates to the values entered in the initial, lower, and upper fields.

The Estimate area is blank before a model is executed but will automatically show parameter estimates after the model is successfully executed. These estimates can then be accepted as the new initial estimates. (See the “Parameters panel” section for more information on estimate setup.)

Press Accept All Fixed+Random to copy all new initial estimates values for all fixed effects, random effects, and the standard deviation.

IndmodelingiconThe Estimate area only shows the results of the last model run, so when modeling individual subjects, only the estimates of the last subject are displayed.

In the Units field(s), enter the desired unit of measurement for the fixed effect. When executed, the units are applied to the output. If the data has units, the fields are disabled. (See the “Units labeling” section for more information on handling of units.)

Note that if initial parameter estimates are entered in the Fixed Effects tab, then each sort level model will use the same initial estimates. On the other hand, if the initial parameter estimates are entered using a worksheet that is mapped to the Parameters panel from the Setup list (either internal or external worksheet), then different initial estimates can be used per sort.

Use the Initial Estimates tab to visually determine a set of parameter estimates that approximate the data. See the “Initial Estimates tab” section.

Using upper and/or lower bounds

Only use the lower and upper bounds if the model converges on a solution that makes no physical sense, such as a negative rate constant or negative volume. If bounds are entered, the program automatically transforms the parameter to an unbounded space.

For a one-sided bound, a square root transformation is used. For a two-sided bound, a square root transformation is first applied to the original parameter, and then an arcsine transformation is applied to the resulting parameter. To avoid obtaining a negative value, a logarithm transformation is used for the standard deviation of the last residual error, with its lower bound automatically set to be 0.001. This applies to all the engines except for the QRPEM and Naïve-Pooled engines, where the lower bound is set to 0. Moreover, for the QRPEM engine, all bounds are ignored except the embedded lower bound for the last residual error.

It is worth pointing out that all transformations are done internally during the optimization phase and the transformed parameter never appears in any reported results. The internal parameter in unbounded space is always transformed back to the original bounded space before results are reported.

In situations where Multiplicative+Additive residual error models are used or any custom error model involving the standard deviations of some residual errors, there is a possibility of a negative result being obtained for the standard deviation. In such situations, the absolute value of the standard deviation should be considered as the concluding result. To avoid this, set a lower bound (e.g., 0) for the parameter.

Units labeling

Model parameters (primary as well as secondary) can be labeled with units. Note, however, that these units do not play a role in the model fitting and no conversion takes place.

When an input dataset has the pertinent columns with units that define units for the model parameters (e.g., for a PK model without covariates: time, concentration, and dose), then these units are carried to the output for fixed effects and secondary parameters. In this case, changing the units when specifying the model is not permitted. The units for each column need to be part of the header for the application to understand them as units and carry them forward to the model results. Note that as long as there is text in the unit location, it will be used as unit labels for the fixed effects and secondary parameters. Other tools require that the units be valid (as denoted by being within parentheses) to perform unit transformations, but this is not a requirement for this application as the units are merely used as labels.

input_dataset_units

If the input dataset has no column units, the units can optionally be entered for each of the fixed effects as well as secondary parameters.

Parameterunits

There are no requirements for the units as they are used as labels, but it is a good practice to ensure that the units make sense within the dataset (e.g., the concentration mass unit is the same as the dose unit) and that the initial estimates are provided in the expected units.

It is recommended that the input dataset be consistent regarding units that define the model parameters. In other words, data values should preferably be in the same mass, time, volume, etc. units.

The Data Wizard can be used to do any unit transformation prior to modeling. See the “Data Wizard” description.


Legal Notice | Contact Certara
© Certara USA, Inc. All rights reserved.