Error/warning reporting within MPI ranks about sundials HOT 5 CLOSED

@jrood-nrel By default SUNDIALS writes all warnings and error messages to stderr. If you're finding that this is not the case let me know what errors you're seeing and I'll check it out.

If you want to direct the output somewhere else, you can set an output file with the function *SetErrFile where * is the integrator specific prefix. For example, with CVODE the function is CVodeSetErrFile(cvode_mem, errfp). If errfp is NULL, then error/warning message output is disabled (we generally discourage disabling the output though).

Alternatively, a user-defined error handling function (of type *ErrHandlerFn where * is CV for CVODE, ARK for ARKODE, etc.) can be attached with the *SetErrHandlerFn function for greater control over error/warning message output. For more details on this option see the documentation for *ErrHandlerFn in the user guides.

Hope that helps and let me know if have any additional questions.

from sundials.

I think the user-defined error handler is ultimately what you're looking for as this could be used to coordinate messages between different instances of the integrator for output from a single rank.

from sundials.

Thanks. I think I'm actually fine with only reporting the messages encountered on the I/O rank as a first step. Right now I'm looking into using ARKStepSetErrFile and setting it to NULL on everything but the I/O rank.

from sundials.

That should work to get things started. You will lose the error messages from the other integrator instances since they don't coordinate with each other but as long as you're capturing the return values from ARKStepEvolve and handling any errors/warnings as needed everything should be good.

from sundials.

I don't want to leave this open perpetually. I think we have the information to work on this within our application so I will close it.

from sundials.