Internal documentation for new resstock users to help get their development environments set up. We have more stable releases and more users, so may be something to think about.
Make resstock more accessible. Separate into "analysis" and "development" groups.
Set up documentation into 1) run and 2) develop based on best practices.
Bare minimum is documented in the resstock/buildstockbatch docs and is fine for external users. There is probably a number of extra items to help new users internally. Things like WinSCP, accessing HPC, AWS groups/credentials.
A table where the rows are Software Name and the columns are Basic User, Advanced User, Developer.
ResStock is at a good point where we could document the fixed steps that are recommended to get started. Could hand this off and end up saving time every time someone needs to get up to speed on resstock-related tools.
A compatibility matrix of resstock, buildstockbatch, OS, and OS-HPXML could be helpful for this.
Internal documentation for new resstock users to help get their development environments set up. We have more stable releases and more users, so may be something to think about.
Make resstock more accessible. Separate into "analysis" and "development" groups.
Set up documentation into 1) run and 2) develop based on best practices.
Bare minimum is documented in the resstock/buildstockbatch docs and is fine for external users. There is probably a number of extra items to help new users internally. Things like WinSCP, accessing HPC, AWS groups/credentials.
A table where the rows are Software Name and the columns are Basic User, Advanced User, Developer.
ResStock is at a good point where we could document the fixed steps that are recommended to get started. Could hand this off and end up saving time every time someone needs to get up to speed on resstock-related tools.
A compatibility matrix of resstock, buildstockbatch, OS, and OS-HPXML could be helpful for this.