Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #300 from nickv2002/master
Added Info Page
- Loading branch information
Showing
1 changed file
with
9 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
It's confusing to understand the organization and connections between all the data we're tying to back up. Here's a few notes that might help make sense of what the data represents and prioritizing what to back up: | ||
|
||
1. Data is built up in Levels: L0 data is whatever considered raw off of instruments, L1 is when that has been ordered calibrated into standard units, L2 & up represent more calculations into different products. | ||
1. An L2 or L3 product will often depend on multiple inputs of other L1/2 products from different sources. This L2/L3 data might also require many days of computer processing time using non-public algorithms. | ||
1. There are some organized groups of data under various 'DAAC' sites but there is no unified organized system, which means data is spread out and often copied all over the place as needed. Each group owns their own products, but depends on other products too. | ||
1. It's really difficult to prioritize what data is most important. One could say X is important and Y isn't, but another research team might need Y. | ||
1. While L0 data is the most important in that it's the bottom level of the pyramid, it's often the least directly *used* because it take a lot of human/computational work to get something calibrated and standardized. | ||
|
||
So basically, all the data is connected in a complex web that's not easy to untangle. |