prepare repo to go public

[teixeirak]

@camerondow35 , we'll want to be ready to make this public fairly rapidly. I'll add some specifics later.

[teixeirak]

@camerondow35 , before going public, let's:

• [x] wait until at least Monday afternoon so that coauthors have a chance to raise any concerns
• [x] clean up climwin results -- definitely delete "old" folder, probably daily
• [x] if possible, rename "bert" folder in scripts to something that makes sense outside our group, or delete if no longer used
• [ ] ideally, it would be nice to fix up the organization / add readmes and metadata to make sure all the file contents and origins are clear, and the organization intuitive. But the most important is to make sure there's nothing that shouldn't be public in case the editor wants it public.

[teixeirak]

Here are some suggestions to make the organization better:

• [ ] it would be best to have raw_data and processed_data folders, with folders for each data stream/ analysis nested within
• [x] nest climate data within data folder (or raw and processed folders, if applied)
• [x] consistently use folders labeled with intuitive names for the various groupings of data/ results. This will make it much easier to navigate. For example:
• [x] create a folder within "Data" for all the dendrometer data
• [x] in results, intuition is to look in "tree_cores" folder for tree-ring results, but most them are just in the main folder.

I'd be happy to help with this, but don't want to break your code by changing file path names.

[camerondow35]

I'd be happy to help with this, but don't want to break your code by changing file path names.

Yes, i'll take care of it - it'll be better if I can do it step-by-step.

Is this something we definitely want done by Monday?

[teixeirak]

No, please enjoy your weekend!

[teixeirak]

It is okay with coauthors to go ahead and make this public once it is ready.

[camerondow35]

This should be mostly done.

it would be best to have raw_data and processed_data folders, with folders for each data stream/ analysis nested within

When you get a chance, could you take a look at how I have it organized now and let me know if this is what you meant?

add readmes and metadata to make sure all the file contents and origins are clear

I'll add these next. I'm thinking links to the climate portal & NCDC for the climate data, and maybe a citation for the tree cores. What else?

[teixeirak]

@camerondow35 , there are a few more things I'd do to make the organization more intuitive:

• [x] move quiltplot_data to results. Actually, it looks like the same files are already there. So confirm that we have all the latest in results, then delete from "data"
• [x] tree_rings/ processed_data should be in the results folder
• [x] clarify the difference between the two folders highlighted blue in the image below:

[teixeirak]

@camerondow35 , I think that once the items above are done, we're good to go with making it public. Adding some readmes will be helpful for others to understand, but the new organization already makes it far more intuitive.

[camerondow35]

So confirm that we have all the latest in results, then delete from "data"

we need all the csv's in there. Versions in "all" folder are combined and sorted while versions in other folders are separated by the three categories.

[camerondow35]

clarify the difference between the two folders highlighted blue in the image below

I honestly don't remember exactly what the pre-cleaned folder was for but it's not used any where so I just deleted it.

[teixeirak]

Thanks! So it seems we're ready to make it public any time.

One other little thing I noticed: could you remove the raw_data folder highlighted in the image below, and just nest the tree-ring data directly in tree_rings? ("Raw data" is misleading, as it's the starting point of your analysis but not the raw data.)