Skip to content

DCM estimates donot match with data #783

Answered by dominikbach
anudeep-uab asked this question in Q&A
Discussion options

You must be logged in to vote

Hi Anudeep

since the bidirectional filter isn't the root cause, I investigated further:

  1. I verified that indeed the constant values already appear in the raw VBA output, indicating that the algorithm sticks with the prior mean (presumably due to - loosely speaking - lack of sufficient information in the data). You can verify e.g. for participant 07, trial 5-7 with dcm.sn{1}.posterior(trl).muTheta(14), where 14 is the index of the first fixed response amplitude for this particular timing definition. You can also verify that this corresponds to the values in dcm.stats with exp(dcm.sn{1}.posterior(trl).muTheta(14))/dcm.sn{1}.eSCR_unit*dcm.sn{1}.newzfactor

  2. I noticed something unusual in th…

Replies: 3 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by dominikbach
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants