Model decisions

[mnky9800n]

• Summary of changes (Bug fix, feature, docs update, ...)
  creates tutorial page that describes where and when you should use fixed or random effects

• Please check if the PR fulfills these requirements

• Closes Decision tree for modelling decisions #113
• Tests added and passed
• All code checks passing - styler run over code
• Vignettes updated/added
• Added an entry in the latest CHANGELOG.md file if fixing a bug or adding a new feature
• Any new libraries added to DESCRIPTION

[XueqingYin]

Thanks @mnky9800n . In the YAML headers, the entry under %\VignetteIndexEntry{ } should be updated, replacing "Priors exploration". Additionally, it seems that how to obtain the DIC values for each model is missing in the section ### Comparing the output. Other than these, everything looks good to me.

Xueqing

[mnky9800n]

what about a decision tree diagram? because i didn't really come up with anything like that. And i think ultimately it doesn't make sense unless we incorporate all of the specific models available in INLA/inlabru. but i dont think we should do that.

…

On Fri, Sep 22, 2023 at 5:04 PM XueqingYin ***@***.***> wrote: @XueqingYin requested changes on this pull request. Thanks @mnky9800n . In the YAML headers, the entry under %\VignetteIndexEntry{ } should be updated, replacing "Priors exploration". Additionally, it seems that how to obtain the DIC values for each model is missing in the section ### Comparing the output. Other than these, everything looks good to me. Xueqing — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

-- John M. Aiken, PhD Consultant, Expert Analytics Researcher, The Njord Centre, University of Oslo mnky9800n.github.io

[XueqingYin]

"decision tree diagram" is fine. And I agree with your second point.

Xueqing

[mnky9800n]

Thanks @mnky9800n . In the YAML headers, the entry under %\VignetteIndexEntry{ } should be updated, replacing "Priors exploration". Additionally, it seems that how to obtain the DIC values for each model is missing in the section ### Comparing the output. Other than these, everything looks good to me.

Xueqing

i was going to use all of the different methods that @gareth-j will implement in the model evaluation tool. that's why i didn't do it yet.