-
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
Claret Bruno Model #350
Claret Bruno Model #350
Conversation
Unit Tests Summary 1 files 150 suites 6m 46s ⏱️ Results for commit e667dcd. ♻️ This comment has been updated with latest results. |
Unit Test Performance Difference
Additional test case details
Results for commit dc4538b ♻️ This comment has been updated with latest results. |
Hmm @danielinteractive , would you mind focusing on the dsld code. For some reason the joint model is working perfectly with no links but as soon as I add the DSLD link it and the lambda_0 parameter go very wrong. For example with link_dsld = -0.1, link_ttg=0.2 and lambda_0=1 I am getting the following:
I've been staring at the code for ages now and I can't see any obvious place where I have gone wrong :( EDIT - NVM just spotted a couple of mistakes / missing brackets in my formula. Am re-testing again now...
|
Code Coverage Summary
Diff against main
Results for commit: e667dcd Minimum allowed coverage is ♻️ This comment has been updated with latest results |
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 think I found something
@danielinteractive - Unfortunately still not working :( With real values of I'm getting samples of:
|
@danielinteractive - @gravesti managed to work out that there was no issue with the implementation, the problem was that my simulation parameters were too extreme and the majority of people were dying instantly. Using more sensible parameters the model works as expected and is able to recover all the known parameters 🎉 |
Great news!! Thanks both!! |
@danielinteractive are you able to still do the review for this or should I transfer to @gravesti instead? |
Hi @gowerc , yeah sure, anything specific to check still? |
@danielinteractive - Not really, I would say the Stan code is probs the highest risk area though. |
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, otherwise looks good
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 Craig!
Closes #338
Most details are in the linked issue. Otherwise not too much special here just based most off the code off of the existing SF model with no real fundamental changes.
Only concern I have is that the ESS seems to be quite low at ~10%. Though this model has a double exponential and some terms that are hard to pick a part so I don't think its a validity concern, its not like the old non-central b parameter that only had single figure ess even with thousands of samples.... but yer not 100% sure that this is ok to ignore but my gut feeling says it is.
EDIT - Talking to Francois he was saying that the SB model tends to have slightly worse performance metrics than the GSF which means we are roughly in line with this expectation so I think this is safe to ignore.