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
For this task, we should aim to provide informative logs for errors raised by hdxstats::differentialUptakeKinetics
Currently, when this function fails at the back end logs are formatted as in the screenshot.
Ideally, I think, it should provide clear structured information about
For what peptides analysis fails, and
What was the reason for the failure was
And decide whether this information should be raised as an error (rlog::log_error), warning (rlog::log_warning), or something else
For this task, we should aim to provide informative logs for errors raised by hdxstats::differentialUptakeKinetics
Currently, when this function fails at the back end logs are formatted as in the screenshot.
Ideally, I think, it should provide clear structured information about
rlog::log_error
), warning (rlog::log_warning
), or something elseLet me know what you think @ococrook

The text was updated successfully, but these errors were encountered: