Malformed parmdb leads to strange error message
Created by: aroffringa
Handing a malformed parmdb to applycal, like this:
mv solutions.h5 solutions.unknown
DPPP msin=obs.ms msout=test.ms steps=[applycal] applycal.parmdb=solutions.unknown applycal.correction=fulljones
...results in the following error:
std exception detected: distributed parm facade not available
We should see if we can catch such wrong usage before calling parmdb, or otherwise rewrite the exception message to make users aware of what's going wrong.