List of known bugs

The list of known bugs in every version of MonolixSuite can be found in the release notes of the next version.

We list below the known bugs in MonolixSuite 2024R1 (they will be fixed in the next version). The 2024R1 version of Monolix can be downloaded here.

Monolix

When changing the structural model for a model with additional observation ids, the mapping for the additional observation ids is not done automatically.
[Bootstrap] After running bootstrap on a project where there are effects of several covariates on the same parameter, with at least one of the covariates that is transformed, the beta values for covariate effects are swapped in the table of estimated population parameters in Estimation compared to the bootstrap results.
[TGI library] The TGI model named TG_Exp_NoFeat_TS0par_TGI_t0Trt_LK_Const_Claret_SD_NoFeat includes a parameter tau that is not used in the model, while it should be used to define a delay.
Typical values of population parameters by categories of categorical covariates are not displayed for latent covariates.
copyData is an option available in config files to run model building, but not for convergence assessment even though the option is available in the GUI.
[Obs versus Pred plot] When all observations and predictions are negatives (this can happen when working with observations which are already log-transformed), the unity line is not shown.
[reporting] when a placeholder has no colors specified, it takes colors from the pevious placeholder instead of the default colors from the project
[Export to Simulx] Exporting a Monolix project with Filters leads to a crash of the Monolix application.
Workaround: Instead of doing an “Export to” in Monolix, do an “Import from” in Simulx.

PKanalix

Clicking on Check lambda_z tab triggers a star (unsaved changes) even though the project has not changed.
Exporting to Simulx a PKanalix project where a covariate is used in a custom NCA parameter, without that covariate, generates an error in Simulx
Exporting to Simulx a PKanalix project where units are defined using a scaling factor generates an error in Simulx
Ctau and AUC_TAU are not correctly calculated when there is no observation points at the end of the interval (time=tau) and lambda_z could not be calculated. Instead of being NaN, Ctau is equal to Clast and AUC_TAU is equal to AUC_last. This bug is also present in previous versions. Note that when lambda_z is available, Ctau and AUC_tau are correctly calculated bu extrapolating the concentration until time=tau using lambda_z.
[Plot Individual fits] label for y-axis is not saved when saving the project and yLabel setting in reporting placeholder is ignored

Simulx

Importing a Monolix or PKanalix project with Filters leading to less occasions than in the unfiltered dataset generates a crash or wrong tables for mlx_XXX elements in Simulx
Importing a Monolix or PKanalix project with a dataset having regressors which are missing (indicated as dots) on some lines and several Obs ID may generate an error “Invalid subject-occasion first regressor value detected at line XXX” when filtering by one ObsId would generate a dataset with only missing regressor values for some individuals.
[reload] When reloading a saved Simulx project which was created by importing a Monolix project into Simulx, error “Missing values for the second part”. This happens when in the Monolix project some categorical covariate columns have only a single value, or when the dataset has been filtered such that only one category remains for some categorical covariates.
Workaround:
If you don’t use mlx_CovDist, manually delete the line defining mlx_CovDist in the .smlx file. The line number of indicated in the error message.
If you use mlx_CovDist in the “Simulation” tab, you can add the definition which are missing for the covariates which have a single category.
If the covariate definition in the model is the following:
```
<MODEL>
[COVARIATE]
input = {TREAT, WTKG, SEX, STDY}
TREAT = {type=categorical, categories={'A','B'}}
SEX = {type=categorical, categories='0'}
STDY = {type=categorical, categories='101'}
```
with SEX and STUDY having a single category, the wrong definition of mlx_CovDist will be the following, containing only WTKG and TREAT:
```
COVARIATE:
continuousCovariates={WTKG}
categoricalCovariates={TREAT, SEX, STDY}
```
```
'mlx_CovDist' = {{distribution=logNormal, typical=70, sd=0.3}, {categories={'A', 'B'}, probabilities={0.6, 0.3}}}
```
It needs to be extended to include also SEX and STUDY, using the same category as listed in the <MODEL> section and probability 1. Note that the order of the definition must match the order of covariates listed above.
```
'mlx_CovDist' = {{distribution=logNormal, typical=70, sd=0.3}, {categories={'A', 'B'}, probabilities={0.6, 0.3}}, {categories={'0'}, probabilities={1}}, {categories={'101'}, probabilities={1}}}
```

Sycomore

Double-clicking on a Sycomore project opens a new Sycomore session without loading that project.

Connectors

[Monolix] A VPC split by some groups generated with plotVpc() can show issues in the prediction intervals if the max binLimit is different across groups. The workaround is to use filter instead of split to generate the VPC separately for each group.
[Simulx] getOutputElements() returns data truncated to 5000 lines, similarly to what is done in the GUI to speed up the display.
[Simulx] Regressor elements are missing from the output displayed by printSimulationSetup(), although the regressors are correctly applied in the project.
[Simulx] when exporting a simulx project to Monolix or Pkanalix using exportProject() with argument “modelFileName”, the modelFilename is not used and the model is saved as model.txt instead.
[PKanalix] in plotCAObservationsVsPredictions(), when using log-scale and with some observations being zero, the dots with value zero are being shown at the border of the plot instead of being hidden.
[PKanalix] in plotNCAIndividualFits(), when using splitOccasions=F, the number of subplots is not properly adjusted.

All applications

When a column is tagged as SS and a column is tagged as ADDL, the setting “number of steady-state doses” does not appear. The workaround is to first ignore the ADDl column, set the number of doses and then tag the ADDL column.