Add APID to wraprun output file

Added ability to append the APID to wraprun output files.

Improved stability and bug fixes

This release adds a limit to the number of MPMD task groups that can be bundled (issue #11). Launching jobs consisting of too many groups can cause ALPS, schedulers, and other support and resource management tools to hang. For the sake of system stability, the number of separate MPMD tasks is limited to 2048. However, an arbitrary number of splits is still possible.

This release also fixes a bug where the executable argument passed by keyword to the API would fail to appropriately convert raw strings to a valid internal representation.

Custom stdout/stderr redirection file names

New group flag --w-oe allows redirected stdout and stderr streams for each task to be stored to custom filenames.

Environment modulefile has been updated to solve bug (originally fixed in-situ) where smithy builds would disregard the loaded programming environment and use a potentially compiler-incorrect build of libsplit.

Adds MPI_File_open support

Adds MPI_File_open to wrapped routines in libsplit. This solves an incompatibility with NetCDF.

Also adds a debugging option to run without setting LD_PRELOAD which should not ordinarily be used.

Python API and config files.

This release adds a python API and the ability to load bundles from YAML configuration files.

Fix location of redirected stdout/err

v0.1.12

Changing working directory before redirecting stdout/err

Adding -j support

v0.1.11

Fix syntax typo

Minor bug fixes

Minor bugs fixed.

Installation scripts modified to appropriately handle packaged python code without manual intervention.

Enforcing no-copy aprun flag and packaged python code

Wraprun now calls aprun via a python subprocess. This eliminates passing and evaluating large executable strings to a parent bash instance. The python code for parsing input has been placed in a standard python package that can be used outside of the CLI binary for testing.

An error was found in earlier releases where the no-copy "-b" flag to aprun was not being injected to the aprun call when it should be. This has been added and the warnings dumped to the log file fixed to show when it was forcibly added. To remove such warnings, users may manually include the flag in the aprun flags to the first executable. It is a syntax error to supply the '-b' flag more than once.

Enhancing signal handling capability

v0.1.8

Ehance signal handling capability