Add files using upload-large-folder tool
Browse files- datasheet.md +6 -6
datasheet.md
CHANGED
@@ -18,12 +18,12 @@ This research was supported by the National AI Research Resource (NAIRR) under g
|
|
18 |
|
19 |
**What do the instances that comprise the dataset represent?**
|
20 |
|
21 |
-
The dataset represents 1,384
|
22 |
|
23 |
**How many instances are there in total (of each type, if appropriate)?**
|
24 |
|
25 |
The dataset includes:
|
26 |
-
- 1,384
|
27 |
- 911 input datasets from GEO and TCGA related to 132 traits
|
28 |
- 41.5 GB of input data with 152,415 total samples (average of 167 samples per dataset)
|
29 |
- 237,907 lines of analysis code (average 261 lines per dataset)
|
@@ -40,11 +40,11 @@ For each problem, the dataset contains:
|
|
40 |
2. Analysis code: Annotated code for data preprocessing and statistical analysis
|
41 |
3. Output data: Preprocessed datasets and the significant genes identified from statistical analyses
|
42 |
|
43 |
-
Note that each
|
44 |
|
45 |
**Is there a label or target associated with each instance?**
|
46 |
|
47 |
-
Yes, each
|
48 |
|
49 |
**Is any information missing from individual instances?**
|
50 |
|
@@ -98,7 +98,7 @@ The analysis code and results were directly created by a team of bioinformaticia
|
|
98 |
|
99 |
The input datasets were programmatically searched and downloaded from the GEO database using Entrez Utilities and from the TCGA Hub of the UCSC Xena platform. The scripts used for this process are included in the './download/' directory of the repository.
|
100 |
|
101 |
-
For the analysis part, a team of 4 researchers designed the problem list and developed example code for solving
|
102 |
|
103 |
<a id="sampling-strategy"></a>**If the dataset is a sample from a larger set, what was the sampling strategy?**
|
104 |
|
@@ -133,7 +133,7 @@ The authors mention engaging in extensive discussions and consultations to addre
|
|
133 |
|
134 |
Yes, extensive preprocessing was performed on the raw gene expression data according to a standardized pipeline. The preprocessing steps included:
|
135 |
|
136 |
-
1. **Dataset filtering and selection**: Filtering out irrelevant datasets and selecting the best dataset for each
|
137 |
|
138 |
2. **Gene expression data preprocessing**: For microarray data, starting with raw datasets identified by probe IDs and mapping these to gene symbols using platform-specific gene annotation data. For RNA-seq data, handling sequence reads that require alignment to a reference genome. Normalizing and deduplicating gene symbols by querying a local gene database to prevent inaccuracies arising from different gene naming conventions.
|
139 |
|
|
|
18 |
|
19 |
**What do the instances that comprise the dataset represent?**
|
20 |
|
21 |
+
The dataset represents 1,384 NGS analysis problems, each uniquely identified by a (trait, condition) pair. Each problem represents a scientific inquiry to identify significant genes associated with a specific trait (e.g., a disease) while accounting for the influence of a condition (e.g., age, gender, or another trait). The condition is either another trait, or 'Age', 'Gender', or 'None' for unconditional problems.
|
22 |
|
23 |
**How many instances are there in total (of each type, if appropriate)?**
|
24 |
|
25 |
The dataset includes:
|
26 |
+
- 1,384 NGS analysis problems (132 unconditional problems and 1,252 conditional problems)
|
27 |
- 911 input datasets from GEO and TCGA related to 132 traits
|
28 |
- 41.5 GB of input data with 152,415 total samples (average of 167 samples per dataset)
|
29 |
- 237,907 lines of analysis code (average 261 lines per dataset)
|
|
|
40 |
2. Analysis code: Annotated code for data preprocessing and statistical analysis
|
41 |
3. Output data: Preprocessed datasets and the significant genes identified from statistical analyses
|
42 |
|
43 |
+
Note that each NGS analysis problem reuses datasets related to its trait and condition. For example, if problem_1 is (trait_A, trait_B) and problem_2 is (trait_A, trait_C), then both problems use the preprocessed datasets for trait_A.
|
44 |
|
45 |
**Is there a label or target associated with each instance?**
|
46 |
|
47 |
+
Yes, each NGS analysis problem has associated "reference answer" in the form of significant genes identified by expert bioinformaticians following a standardized analysis pipeline. These are stored in JSON files with gene symbols, their coefficients, and absolute coefficients in the trained regression model.
|
48 |
|
49 |
**Is any information missing from individual instances?**
|
50 |
|
|
|
98 |
|
99 |
The input datasets were programmatically searched and downloaded from the GEO database using Entrez Utilities and from the TCGA Hub of the UCSC Xena platform. The scripts used for this process are included in the './download/' directory of the repository.
|
100 |
|
101 |
+
For the analysis part, a team of 4 researchers designed the problem list and developed example code for solving NGS analysis problems. They extracted common patterns from these examples to develop guidelines for the entire benchmark. Then, a team of 9 bioinformaticians was assembled and trained to analyze the complete set of problems following these guidelines. They submitted their analysis code and results weekly over a period of 20 weeks.
|
102 |
|
103 |
<a id="sampling-strategy"></a>**If the dataset is a sample from a larger set, what was the sampling strategy?**
|
104 |
|
|
|
133 |
|
134 |
Yes, extensive preprocessing was performed on the raw gene expression data according to a standardized pipeline. The preprocessing steps included:
|
135 |
|
136 |
+
1. **Dataset filtering and selection**: Filtering out irrelevant datasets and selecting the best dataset for each NGS analysis problem based on relevance, quality, and sample size.
|
137 |
|
138 |
2. **Gene expression data preprocessing**: For microarray data, starting with raw datasets identified by probe IDs and mapping these to gene symbols using platform-specific gene annotation data. For RNA-seq data, handling sequence reads that require alignment to a reference genome. Normalizing and deduplicating gene symbols by querying a local gene database to prevent inaccuracies arising from different gene naming conventions.
|
139 |
|