These are UI bugs when using pace-neutrons with Spyder.
When typing commands, Spyder uses the getdoc method to get instant documentation... but we don't provide this, so get errors like Unrecognized function or variable 'saveNXSPE.getdoc'. Edit: the cause of this error is in IPython - the getdoc method doesn't exist and Matlab returns an error which is caught and ignored by Python but Matlab also prints out a message which is not ignored, due to some stuff in the Matlab-Python bridge / stdout/err redirection.
Some commands don't work when run in a cell (using the Spyder runcell because of stdout/stderr redirection causes Matlab to give a Error on flush (see here)
After some processing, Spyder does something which causes the Matlab runtime library to lose its initialization. This manifests as an ImportError on matlab_pysdk.runtime.NumberOfOutputArgumentsError because the *Error classes are actually in the MCR C++ extension and are patched into the module at runtime (see here). Edit: the cause of this issue is that Spyder deletes the modules here [a normal reload is not an issue].
These are UI bugs when using
pace-neutrons
with Spyder.getdoc
method to get instant documentation... but we don't provide this, so get errors likeUnrecognized function or variable 'saveNXSPE.getdoc'.
Edit: the cause of this error is in IPython - thegetdoc
method doesn't exist and Matlab returns an error which is caught and ignored by Python but Matlab also prints out a message which is not ignored, due to some stuff in the Matlab-Python bridge / stdout/err redirection.runcell
because ofstdout
/stderr
redirection causes Matlab to give aError on flush
(see here)ImportError
onmatlab_pysdk.runtime.NumberOfOutputArgumentsError
because the*Error
classes are actually in the MCR C++ extension and are patched into the module at runtime (see here). Edit: the cause of this issue is that Spyder deletes the modules here [a normal reload is not an issue].