Closed sbfnk closed 1 week ago
what about 5. have them in the session folder as a .stan
file? Or are we expecting people to work through the session without having clone the repo?
There is the added complexity of if we want to share functions across sessions but I think we can get to that when we get to it
what about 5. have them in the session folder as a
.stan
file? Or are we expecting people to work through the session without having clone the repo?
We don’t expect them to clone in mfiidd (or expect them to interact with git at any time) but yes that’s another option.
So how do they work through the sessions? Copy and pasting from the website? I dunno that feels error prone to me but I guess if it works it works. Working with a download of the repo != using git. We could also pass around a USB (😆 ) or have a short URL they can download from and write the code down or something?
How would we do it without copying & pasting? Provide R scripts alongside the qmd
files? Or expect them to re-render the qmd
s?
they would use the qmd as an interactive notebook in Rstudio?
After discussion decided on (5)
We probably want to use cmdstanr and thus need to read in models as files. The question is how we serve the models to course participants.
Options are:
write_stan_file
) - downside is that it clutters the code and has to be written out first,download.file
- downside is will have to decide where to put etc.nfidd
package ininst
(once installed), using e.g.system.file(package = "nfidd")
- downside is that it won't be straightforward to editOf these I think (1) might still be best as people can operate from a single script file and don't have to go back and forth but there might be options that I have missed.