Per issue #456 I found some undead data issues and @cchambe12 updated our data. This should lead to super tiny changes in the data, but Rangers and Traitors leads should re-run their code and report on any issues that we may need to address collectively.
@MoralesCastilla I feel this is TOO close to submission to ask you to re run everything especially given how small the changes are. But to check this plan is okay, I ran the new data through the model code TODAY and got:
@dbuona @MoralesCastilla @DeirdreLoughnan
Per issue #456 I found some undead data issues and @cchambe12 updated our data. This should lead to super tiny changes in the data, but Rangers and Traitors leads should re-run their code and report on any issues that we may need to address collectively.
@MoralesCastilla I feel this is TOO close to submission to ask you to re run everything especially given how small the changes are. But to check this plan is okay, I ran the new data through the model code TODAY and got:
... on quick glance this look identical to what you have (given MCMC errors) so I feel okay.
To get the code to run (as there is now a Juglans_spp that seems new) I added one line:
bb.stan <- subset(bb.stan, species!="spp")
Around line 104 so those lines look like:I think once at the requested revision stage it would be good to re-run everything if you think that's possible.