Improve error reporting from algorithms in multithreaded loops #8292
Labels
Framework
Issues and pull requests related to components in the Framework
Maintenance
Unassigned issues to be addressed in the next maintenance period.
Projects
This issue was originally TRAC 7446
http://trac.mantidproject.org/mantid/ticket/7325 & http://trac.mantidproject.org/mantid/ticket/7400 raised the issue that error messages thrown from multi-threaded loops can be misleading. They always end with something like:
where PeaksInRegion is the algorithm name.
The problem is you are generally looking at the log reading that message and there is no more information anywhere. We should try and improve the error reporting from OMP loops by maybe storing the last exception thrown and rethrowing it or at least store the message and remove the parts about seeing the log.
Keywords: Maintenance
The text was updated successfully, but these errors were encountered: