Currently, singularity/create_links.sh along with singularity/libexec/kqclib.sh is used for creating commands like kqclib and ElmerSolver to be runnable on host OS. I think the inner implementation should be changed from manual bash files runnning singularity exec to Singularity Apps. See also Reproducible SCI-F Apps.
This would change the implementation to something standardised.
Use case
Using Singularity apps, one exposes an interface given in the Singularity definition file
singularity run --app ElmerSolver /some/path [args...]
Though the current exec solution is also possible with apps.
The functionality overlaps with the exposed kqc command (kqc simulate and kqc mask). So maybe that should kept as a main runscript instead of something like
Description
Currently,
singularity/create_links.shalong withsingularity/libexec/kqclib.shis used for creating commands like kqclib and ElmerSolver to be runnable on host OS. I think the inner implementation should be changed from manual bash files runnningsingularity execto Singularity Apps. See also Reproducible SCI-F Apps. This would change the implementation to something standardised.Use case
Using Singularity apps, one exposes an interface given in the Singularity definition file
Though the current exec solution is also possible with apps.
The functionality overlaps with the exposed
kqccommand (kqc simulateandkqc mask). So maybe that should kept as a main runscript instead of something like