Skip to main content
Skip table of contents

Applications validation

The validation of the applications can be done via an executable in suite. The validation is in two steps.

Validation of the graphical interface

For that part, you need to follow the steps described here. It is a simple procedure to check that the installation is ok, the interface is ok and that the link between the interface and the calculation engine.

Validation of the Monolix

The validation can be done via an executable in MonolixSuite.

  1. Go to the installation folder of MonolixSuite, by default:

    • [Windows] C:/Program Files/Lixoft/MonolixSuite2024R1

    • [MAC] /Applications/MonolixSuite2024R1.app/Contents/Resources/monolixSuite

    • [LINUX] /home/<your username>/Lixoft/MonolixSuite2024R1

  2. Launch the following command line

    CODE
    [Windows OS] .\lib\validationSuite.exe --no-gui -s monolix -i .\resources\validationSuite\monolix
    [LinuxOS & MAC OS] ./lib/validationSuite --no-gui -s monolix -i ./resources/validationSuite/monolix
    • It runs 16 projects that cover all the features of Monolix. The validation matrix can be found here: validationMatrix_2014.pdf.

    • The results are in the user directory userDirectory\lixoft\monolix\monolix2024R1\tmp for the user that launched the validation suite. You can define the repository where to set the report using the “-o” command.

    • A summary called validation_suite_summary.txt is proposed and you should have only OKs as the one enclosed that I just run.

    • It takes around 40 minute on a classical laptop (a 4-core classical machine).

In case of a LinuxOS, the validation suite depends on the glibc version of the machine, thus, this writes

CODE
[LinuxOS] ./lib/validationSuite --no-gui -s monolix -i ./resources/validationSuite/linux64_glibc-<version>/monolix

where <version> can be 2.27, 2.28, or 2.29.

Alternatively, you can also use absolute paths. Note that on winddows, for the 2024 version installed in “Program Files”, the quotes “” are necessary around the path name to handle the space in the string. For instance:

CODE
"C:\Program Files\Lixoft\MonolixSuite2024R1\lib\validationSuite.exe" --no-gui -s monolix -i "C:\Program Files\Lixoft\MonolixSuite2024R1\resources\validationSuite\monolix"

Validation of PKanalix

The validation can be done via an executable in MonolixSuite. It is the same as for Monolix.

  1. Go to the installation folder of MonolixSuite, by default:

    • [Windows] C:/Program Files/Lixoft/MonolixSuite2024R1

    • [MAC] /Applications/MonolixSuite2024R1.app/Contents/Resources/monolixSuite

    • [LINUX] /home/<your username>/Lixoft/MonolixSuite2024R1

  2. Launch the following command line

    CODE
    [Windows OS] .\lib\validationSuite.exe --no-gui -s pkanalix -i .\resources\validationSuite\pkanalix
    [LinuxOS & MAC OS] ./lib/validationSuite --no-gui -s pkanalix -i ./resources/validationSuite/pkanalix
    • It runs 33 projects that cover all the features of PKanalix.

    • The results are in the user directory userDirectory\lixoft\pkanalix\pkanalix2024R1\tmp for the user that launched the validation suite. You can define the repository where to set the report using the “-o” command.

    • A summary called validation_suite_summary.txt is proposed and you should have only OKs as the one enclosed that I just run.

    • It takes couple of minutes on a classical laptop (a 4-core classical machine).

In case of a LinuxOS, the validation suite depends on the glibc version of the machine, thus, this writes

CODE
[LinuxOS] ./lib/validationSuite --no-gui -s pkanalix -i ./resources/validationSuite/linux64_glibc-<version>/pkanalix

where <version> can be 2.27, 2.28, or 2.29.

Validation of Simulx

The validation can be done via an executable in MonolixSuite. It is the same as for Monolix.

  1. Go to the installation folder of MonolixSuite, by default:

    • [Windows] C:/ProgramData/Lixoft/MonolixSuite2024R1

    • [MAC] /Applications/MonolixSuite2024R1.app/Contents/Resources/monolixSuite

    • [LINUX] /home/<your username>/Lixoft/MonolixSuite2024R1

  2. Launch the following command line

    CODE
    [Windows OS] .\lib\validationSuite.exe --no-gui -s simulx -i .\resources\validationSuite\simulx 
    [LinuxOS & MAC OS] ./lib/validationSuite --no-gui -s simulx -i ./resources/validationSuite/simulx
    • It runs around 60 projects that cover all the features of Simulx.

    • The results are in the user directory userDirectory\lixoft\simulx\simulx2024R1\tmp for the user that launched the validation suite. You can define the repository where to set the report using the “-o” command.

    • A summary called validation_suite_summary.txt is proposed and you should have only OKs as the one enclosed that I just run.

    • It takes less than 10 minutes on a classical laptop (a 4-core classical machine).

In case of a LinuxOS, the validation suite depends on the glibc version of the machine, thus, this writes

CODE
[LinuxOS] ./lib/validationSuite --no-gui -s simulx -i ./resources/validationSuite/linux64_glibc-<version>/simulx

where <version> can be 2.27, 2.28, or 2.29.

Validation on Mac devices with Apple silicon

The procedure to run validation suite on Mac devices with Apple silicon is the same as above, but references must be downloaded using this link. The path to the extracted references directory needs to be provided using the -i flag, instead of the default path in the above examples.

Validation on older versions

Validation is the same for the previous version of the MonolixSuite

  • For Monolix, it is available since the 2018R1 version.

  • For PKanalix, it is available since the 2019R1 version.

  • For Simulx, it is available since the 2020R1 version.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.