File structure #8
brianlangseth-NOAA
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is flexible and open for discussion. I wanted to set up a file structure early and jot down what each would house. This is based on the one I used for canary, which differs a little from what was done for copper last time.
Early proposal:
code - any R code
data - post-processed non-confidential data outputs from functions used within code files, or data ready for input into SS3
data-raw - raw data from which files in "data" are derived. This folder is ignored because it should not be pushed to github. Include a subfolder here "CONFIDENTIAL" for data that is confidential to the group so as to make it easy to separate when we archive
docs - where we would put any website material for viewing
documents - place for report writing materials (either from sa4ss or the new HQ template)
models - folder for model runs.
If we want to add R functions, which is what most of the code appears to be from the copper assessment, we can do so in the code folder
Beta Was this translation helpful? Give feedback.
All reactions