Improve error message for DDS
Issue
We need to improve error message for DDS when the observations are missing for optimization. ATM we get a developer level message
which is completely out of context for mhm users who don't know much about the source code. In general, the mhm error messages should transition from developer level
to user level
.
Location
Complexity
However, this example is a bit different to others in the sense that the message is embedded in mo_dds
which is part of FORCES library.
Challenge
To find a way to communicate with mhm user based on errors occurring at modules of shared/ external libraries like FORCES.