Known Issues
This section lists known issues with recent versions of BRAHMS. Items listed here may be fixed in a future release or patch; in the meantime, advice to work around each issue is given on this page.

BRAHMS 0.7.3

Issue

Advice

Status

Older processes abort when compiled/run against 0.7.3 (all platforms)
This is a bug in the legacy support in the 1199 bindings, and will be fixed in the next release.
Workaround
Download this version of brahms-1199.h (R2457) and use it to replace the one installed in your version 0.7.3 installation folder (at SYSTEMML_INSTALL_PATH/BRAHMS/include).
Fixed in HEAD
MPI execution does not pick up user-level Execution Parameters (Windows)
Since individual processes run under MPI as "LocalService", rather than the user that launched them, the user's Execution Parameters are not picked up.
Workaround
Set any Execution Parameters at the machine-level (see "brahms_manager" under Matlab).
Nothing Planned (you got any ideas?)
Following a hung thread on Linux, a segmentation fault may occur
pthreads doesn't mix well with C++ exceptions, leaving us unable to kill hung threads on linux. All we can do, afaik, is unload the modules under them. This, it seems, results in an abort (which i think makes sense). See developer note "pthread_kill".
Workaround
Whilst this is not an elegant state of affairs, there's no real hit, since the abort happens after the thread has been abandoned by the framework anyway. Ignore the message, fix the hang, and get on with your life.
Nothing Planned (you got any ideas?)

BRAHMS 0.7.2

Issue

Advice

Status

Abort/Exception when MaxThreadCount is parsed
A bug will cause an abort (windows) or an exception (linux) when MaxThreadCount is set to "unlimited". "unlimited" is indicated either by setting the value to "0" (zero) or to "" (the empty string). Confirm you have this problem by passing "--detail-5" to the executable; the failure should occur immediately after a message about "MaxThreadCount". Workaround is to set the value of MaxThreadCount to "999999" (i.e. practically unlimited).
Workaround
Set the value of MaxThreadCount to "999999" (i.e. practically unlimited).
Fixed in 0.7.3
Matlab/Python outputs corrupted when process has more than one output
A bug will corrupt output of Matlab/Python processes when those processes create more than output. Alternatively, on some installations, an abort may result.
Patch
Patch 2094 fixes this issue.
Fixed in 0.7.3
Incorrect Base Sample Rate displayed
A bug will cause the run-time GUI to display Base Sample Rate incorrectly if higher than 99999Hz. No other effects (computations are performed correctly).
Workaround
None required.
Fixed in 0.7.3