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
In order to facilitate debugging the warning system could use something similar to the error system and show the nesting of all the function calls that led to the warning.
I believe that it could be quite useful for streamlined used of PsPM, for instance if multiple dataset are analyzed but an issue arise in only one of them. This would provide the (advanced) user with a place to look at to understand the issue, without blocking the processing of the other data sets.
The expected behaviour would look like this:
functionA uses functionB which uses functionC which raises a warning message XXX.
The actual displayed message would be something like :
"/!\ Warning message: /!\
XXX
arised in functionC, from the stack trace:
functionA --> functionB --> functionC "
This could probably be implemented through a special pspm_warning function that would take the same input as the usual warning function but would append the stack trace to the message. To get the stack trace, a function like dbstack (https://uk.mathworks.com/help/matlab/ref/dbstack.html) could be helpful.
The text was updated successfully, but these errors were encountered:
In order to facilitate debugging the warning system could use something similar to the error system and show the nesting of all the function calls that led to the warning.
I believe that it could be quite useful for streamlined used of PsPM, for instance if multiple dataset are analyzed but an issue arise in only one of them. This would provide the (advanced) user with a place to look at to understand the issue, without blocking the processing of the other data sets.
The expected behaviour would look like this:
functionA uses functionB which uses functionC which raises a warning message XXX.
The actual displayed message would be something like :
"/!\ Warning message: /!\
XXX
arised in functionC, from the stack trace:
functionA --> functionB --> functionC "
This could probably be implemented through a special pspm_warning function that would take the same input as the usual warning function but would append the stack trace to the message. To get the stack trace, a function like dbstack (https://uk.mathworks.com/help/matlab/ref/dbstack.html) could be helpful.
The text was updated successfully, but these errors were encountered: