Open codyevers opened 1 year ago
As a group, we decided that yes, we will archive this to it's own branch, but that before we do this, we want to make sure that (a) it's contained to a very specific area of the code (so that it doesn't become too big an issue to graft it back into a latter version; (b) create a test dataset called test_fire
that lives alongside test_forest
and can be used to demonstrate and/or test functionality when this does get revived.
I've created a new test_fire
dataset and saved it in forsys/inst/extfiles/
. I will incorporate this into the package datasets (and document all the variables for both).
@michelledayusfs, thinking it might be worth documenting in the readme.md... better yet a vignette once we convert documentation to parckage down.
Should we archive forsys with fire? Probably yes for the open-source version. Yet, given continued development of the 4-scenario paper, we can't loose this data, and might want to pick this up again on very short notice.