You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running SimQPN.sh from the command line, all the outputs go to stdout while stderr stays empty
As a result, all errors and stacktraces that are printed while starting the environment also go to the resulting output (file).
Therefor, to only obtain the relevant information when running the CLI, it is necessary to split/filter the resulting file.
It would be desirable that all warning/error messages from the Eclipse ecosystem would go to stderr and only the QPME- and simulation-specific output would go to stdout.
The text was updated successfully, but these errors were encountered:
When running
SimQPN.sh
from the command line, all the outputs go tostdout
whilestderr
stays emptyAs a result, all errors and stacktraces that are printed while starting the environment also go to the resulting output (file).
Therefor, to only obtain the relevant information when running the CLI, it is necessary to split/filter the resulting file.
It would be desirable that all warning/error messages from the Eclipse ecosystem would go to
stderr
and only the QPME- and simulation-specific output would go tostdout
.The text was updated successfully, but these errors were encountered: