There are a lot of files not needed for timber supply analysis - it would be nice to be able to clone only those files needed.
A smaller repo would be easier to learn.
Adding a version number to the small repo would allow the version to be reported in the public discussion paper - and help with repeatability and transparency.
Being able to lock the model down to a version would ensure that the sensitivity analyses completed to understand the impact of one parameter on the base case is run on the exact same model the base case was run on.
Describe the solution you'd like
A sub repo containing all the files necessary, and no more, to run a timber supply model and versioning for the sub repo.
Alternatively, the necessary files could be copied locally and not linked to GitHub.
Local files solve the problem of locking down the files and allow for archiving. They don't have the benefit of enhancing repeatability and transparency, or reducing the learning overhead when adopting Castor as a timber supply model.
There are a lot of files not needed for timber supply analysis - it would be nice to be able to clone only those files needed.
A smaller repo would be easier to learn.
Adding a version number to the small repo would allow the version to be reported in the public discussion paper - and help with repeatability and transparency.
Being able to lock the model down to a version would ensure that the sensitivity analyses completed to understand the impact of one parameter on the base case is run on the exact same model the base case was run on.
Describe the solution you'd like
A sub repo containing all the files necessary, and no more, to run a timber supply model and versioning for the sub repo.
Alternatively, the necessary files could be copied locally and not linked to GitHub.
Local files solve the problem of locking down the files and allow for archiving. They don't have the benefit of enhancing repeatability and transparency, or reducing the learning overhead when adopting Castor as a timber supply model.