Closed teixeirak closed 4 years ago
@teixeirak - it should already be up. Its embedded within the "non-soil" data. For GROA, I've only been using the variables that quantify distinct pools (litter only, CWD only) rather than combined pools. Abby can extract the variables she wants and I'm fine with that becoming the master. Let me know if you spot any issues and I'll fix them on my end. Also, I've been pouring through the litter/CWD all day today. There is still plenty for Abby to tackle, but maybe a phone call would be helpful so Abby is not starting at ground zero with GROA data?
Thanks, @CookPatton. Let's set up a phone call early next week to review this with Abby. I'll send an email about this.
@CookPatton, a few clarifications: 1- Is this the master file? 2- non_soil_data.csv (older file) contains only a handful of records. Delete? 3- What is the difference between soil.csv and soiltosurface.csv](https://github.com/forc-db/GROA/blob/master/data/soiltosurface.csv)?
Looking forward to chatting today!
@teixeirak Yes, that is the master file. Please delete the other non_soil_data.csv which only had a handful of records. You can also delete the soil.csv file. The soiltosurface.csv data provides a cumulative amount of SOC from max depth to the surface (instead of from 10 cm to 20 cm, for example). I provided this because it better matched the structure of ForC.
I've deleted non_soil_data.csv. It might make sense to keep (update?) soil.csv if its going to be the master version.
@teixeirak and @CookPatton, Could you please re-clarify what files are the "good ones"? Should I import data from soil.csv or soiltosurface.csv?
Don't worry about soil data for Abby's analysis. You want nonsoil_litter_CWD.
@CookPatton, Could you please upload dead wood & litter data, in as close to "final" format as possible, by next Monday (11/5), when Abby starts working with us, so that she can get started with it? Of course it probably won't be totally final, but could we manage the GitHub version as the master so that we have something fairly stable to work with on this end? It also would be good to have something that we could edit if need be. (It may be worth a phone conversation about how to manage this.)