Closed thigm85 closed 6 years ago
The first time it's indeed overhead from compiling the model (as you should be able to verify with verbose=TRUE
).
Re-running the filter should indeed be much quicker, but there was a bug preventing this. It should be fixed if you reinstall with install_github
, as per 0617aa7a27f92ec18f0264c59f8b3a5631bcc2e7.
The commit mentioned above fixed the issue when target="posterior"
. However, the model compilation happens every time I use target="prediction"
.
Looking at the code I see that this code block indeed trigger model compilation every time prediction is used as a target.
Is this really necessary, or would it be enough to simply call libBi with --init-file
without triggering model compilation every time?
I think you're right - there is no more need for this code block. Please re-open if this is not fixed by 6267561.
Thanks for addressing this. I will let you know if this is not fixed.
I was playing around with RBi and noticed that even very simple
filter
operations would take a long time to run:while the display of the libbi obj would claim a much faster run time:
And this happens even after I have already run an operation with a model, so that compilation should not be the reason for that time difference AFAIK.
Is there a reason for this duration diff?