write_pao seems to throw a weird issue

[cjcarlson]

Hey folks! I thought your paper was really cool so I wanted to look over the code - I can't run it directly from the package, though, because 'inst/' in write_pao points to a file path that's not being created on my machine by here::here. I'm not sure if it's an OS issue (I'm on Windows)?

[crushing05]

Hmm, I can take a look, though I suspect it might be related to the RPresence package, which underwent some changes between when I originally wrote this code and when the paper came out. I haven't really had time to sort out how to modify this code to work with the new RPresence. That said, the pao stuff if only needed to create initial values, which is somewhat specific to the BBS examples. If you're interested in using any of this code for your own data, you could just modify the JAGS file to match the structure of your data and then adapt the model running code accordingly. Also be warned that for the BBS examples, model run time is obscenely long for convergence (several weeks or more).

[trashbirdecology]

I believe this issue is due to discrepancies between path and file writing across multiple functions (e.g. GetInits, write_pao).

For example, in some functions the user can specify path (e.g. as here::here("/output")), yet the files are written to here::here("/inst/output"), which DNE unless the user specifies path as inst/output.

I was planning to submit a PR, but wasn't sure whether you had a good reason for saving the output files in /inst, as, I believe (please correct me if I am wrong!) inst should be reserved for raw data files to be included in the packaged package.