-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ability to extract raw samples #221
Conversation
Thanks @gowerc , sounds good - one thought on shorter naming, how about |
@danielinteractive - Pending CICD corrections this is now ready for review. Regarding the function name I feel very conflicted. General convention for methods is to be verb focused "extract", "as", "sample", "get". Part of me wonders if
I do appreciate / agree the current method name is a bit excessively verbose but the alternative doesn't quite feel "right" to me. |
Ok yeah good thoughts on the naming. Not super important so can leave as is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @gowerc I browsed through it and looks good to me, only found some typos
Another alternative is to move the implementation to the constructor so that the call is slightly shorter e.g.
|
Code Coverage Summary
Diff against main
Results for commit: 5971760 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Closes #220
Fixes previous regression of not being able to return the individual quantity samples. I ended up having to re-work the functions a little bit as it was getting too nested. With this change the api has gone from:
to
To summarise
generated_quantities
has been moved into the constructor-method rather than the individualpredict
/autoplot
methodsas.data.frame
method to return the raw samplespredict
has been re-named assummary
which I felt better reflected what was happeningSurvivalQuantities
(think this slightly better represents what they are)Currently marked as "draft" as I still need to update the documentation / unit tests