-
Notifications
You must be signed in to change notification settings - Fork 5
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
How to predict from prior-sampled model (+ how to have choice and rt as a separate input) #19
Comments
I'm not quite sure how to fix the issue. It might be good to ask the Turing team for advice for this specific model. Yesterday, Kiante and I made changes that I believe were supposed to prevent the no matching method error. Have you upgraded to the most recent version? |
Also, if you don't mind, I will add your solution to the documentation. |
I did, but the
Of course :) Thanks! |
@DominiqueMakowski, the following code runs without a method error. However,
|
I have been wondering whether the solution to this problem is to define a type called |
I agree with your vision of striving at implementing things "the proper way" without hacks and workarounds - when possible. Unfortunately I cannot help much you directly with the code (still a Julia newbie) - but I can assist with testing things, trying to get external help and all that |
I feel like this question lies somewhere between SequentialSamplingModels and Turing itself, but let's assume the following basic LBA model:
(note that it is made to run with a dataframe input for convenience)
I can easily sample from priors. What I like to do next is to make generate predictions from these priors (to visualize a prior predictive check).
My first instinct was to simply run:
But it returns nothing - which I thought was a bug. The Turing team clarified the solution: it was to set the outcome variable to
missing
, which is straightforward in a linear model, but not here.Attempt 1: Re-instantiating the model on a data with missing for
choice
:Attempt 2: Re-write the model to have choice and rt as separate inputs, which would also make it more flexible (for instance to add predictor variables in the future).
Turing doesn't seem to like the tuple output. So maybe we can workaround by creating the
data
tuple inside the model?Unfortunately no. I am not sure what else to try, and any pointers and thoughts are more than welcome☺️
The text was updated successfully, but these errors were encountered: