Skip to content

Changes after review by Olaf #133

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sahehb merged 4 commits into from
Jan 20, 2026
Merged

Changes after review by Olaf #133

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
612d143
Changes after review by Olaf
sahehb Jan 20, 2026
52b7ea7
MLAB-6214
sahehb Jan 20, 2026
93f52b6
Additional changes after first review
sahehb Jan 20, 2026
8899f1c
ASSERT is always used, no explanation for EXPECT was given.
sahehb Jan 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions mevislab.github.io/content/tutorials/dataobjects/curves.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,5 +19,3 @@ menu:
Curves can be used in MeVisLab to print the results of a function as two-dimensional mathematical curves into a diagram.

![Curves in MeVisLab](images/tutorials/dataobjects/curves/Curves.png "Curves in MeVisLab")

In the given example, only modules available in commercial **MeVisLab Professional SDK** have been used. The non-commercial **MeVisLab Standard SDK** provides more modules for curves.
2 changes: 1 addition & 1 deletion mevislab.github.io/content/tutorials/summary/summary2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ Select your *.mlab* file from [Step 1](tutorials/summary/summary1/) and check *A

![Macro module wizard](images/tutorials/summary/Example2_4.png "Macro module wizard")

You do not have to define fields of your macro module now, we will do that later. Click *Create*. The Windows Explorer opens showing the directory of your macro module. It should be the same directory you selected for your Package.
You do not have to define fields of your macro module now, we will do that later. Click *Create*. The file explorer opens showing the directory of your macro module. It should be the same directory you selected for your Package.

### Directory Structure of a Macro Module
The directory structure for a macro module is as follows:
Expand Down
6 changes: 3 additions & 3 deletions mevislab.github.io/content/tutorials/summary/summary5.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ The directory contains the following files (and some more maybe):
* Installer (*.exe*) file
* MeVisLab Install (*.mlinstall*) file
* Shell (*.sh*) script
* Third-party list (*.csv*)
* Software Bill of Materials [SBOM] (*_sbom.json*)

#### Batch File
The batch file allows you to generate the executable again via a Windows batch file. You do not need the Project Wizard anymore now.
Expand All @@ -93,8 +93,8 @@ The file is initially generated by the Project Wizard. Having a valid file alrea
#### Shell Skript
The shell skript allows you to generate the executable again via a Unix shell like bash. You do not need the Project Wizard anymore now.

#### Third-party File
The third-party file contains all third-party software tools MeVisLab integrated into your installer from dependency analysis. The file contains the tool name, version, license, and general information about the tool.
#### Software Bill of Materials [SBOM]
The SBOM file includes a list of all third-party components, libraries and dependencies included into your installer by MeVisLab. We use the standard format *CycloneDX* which allows to import this file to standard evaluation tools like [Dependency-Track](https://dependencytrack.org).

### Install Your Executable
You can now execute the installer of your application.
Expand Down