CoNTExT takes as input the full transcriptomic data of your neural progenitor and differentiated cell cultures, measured via microarray chip, and compares it to in vivo transcriptomic atlases of brain development. Your data is uploaded to the server, processed, and the results files are emailed to you.
Step 1: Acquire transcriptomic data of neural progenitor and differentiated cultures. Importantly, 3 biological replicates each of neural progenitor and differentiated cultures are needed for the pipeline (minimum 6 total samples). These samples should be profiled on a microarray chip, and either run simultaneously on one chip, or randomized to a chip and batch corrected via ComBat or other method.
Step 2: Format the data. CoNTExT requires 3 files to run, which must be formatted in the appropriate way. All three files must be comma separated value files (*.csv). You can make these files in MS Excel but we caution you that this program often changes values inadvertently. We advise you to make these files in the R package.
Annotation file: This file contains the mapping of probes to genes. The rownames are the probes and should match exactly to the rownames of the expression file. The SYMBOL column represents the HGNC gene symbol. The ENTREZ_GENE_ID is the Entrez gene ID from NCBI. All of this information will be found on the website of the chip manufacturer, but must be organized in the following way. Here is an example file:
"SYMBOL","ENTREZ_GENE_ID"
"ILMN_1762337","7A5",346389
"ILMN_2055271","A1BG",1
"ILMN_1736007","A1BG",1
"ILMN_2383229","A1CF",29974
"ILMN_1806310","A1CF",29974
"ILMN_1779670","A1CF",29974
"ILMN_1653355","A26C3",23784
"ILMN_1717783","A26C3",23784
"ILMN_1705025","A26C3",23784
…
Metadata file: This file contains the mapping of samples to their culture status and line. The rownames are the sample identifiers and should match exactly to the columns of the expression file. The Status column should be labeled with either “Progenitor” or “Differentiated” indicating the differentiation state of the culture. The Replicate column should be used to describe which samples came from the same line which can be defined as any of the following: same subject, same clone, or same line. Replicate is used to properly account for samples which are more similar to each other than other samples as a random effect in a mixed effect smodel. Here is an example file:
"Status","Replicate"
"1","Progenitor","Line 1"
"2","Progenitor","Line 2"
"3","Progenitor","Line 3"
"4","Progenitor","Line 2"
"5","Progenitor","Line 3"
"6","Progenitor","Line 1"
"7","Differentiated","Line 2"
"8","Differentiated","Line 3"
"9","Differentiated","Line 1"
"10","Differentiated","Line 1"
"11","Differentiated","Line 2"
"12","Differentiated","Line 3"
Expression file: This file contains the expression of each probe for each sample. Prior to input, expression files should be log2 transformation, quantile normalized, and batch corrected (if necessary). The columns of the expression file should correspond exactly to the rows of the metadata file. The rows of the expression file should correspond exactly to the rows of the annotation file. Here is an example file:
"1","2","3","4","5","6","7","8","9","10","11","12"
"ILMN_1762337",7.35,7.27,7.28,7.07,7.10,7.10,7.17,7.16,7.17,7.09,7.14,7.19
"ILMN_2055271",7.28,7.44,7.48,7.33,7.63,7.41,7.43,7.50,7.66,7.52,7.48,7.46
"ILMN_1736007",7.60,7.50,7.27,7.54,7.40,7.36,7.70,7.96,7.77,7.72,7.73,7.88
"ILMN_2383229",7.09,7.19,7.27,7.23,7.36,7.16,7.13,7.11,7.21,7.13,7.33,6.97
"ILMN_1806310",7.31,7.15,7.31,7.13,7.26,7.14,7.26,7.27,7.39,7.29,7.15,7.31
Step 3: Register. In order to prevent overuse or misuse of the servers, we ask that each contributor register with their name, email address, and institution. Registrations are manually approved, so we’ll try to get back to you within a day to approve your account. Registration is only necessary one time. If you are a netbot, you must demonstrate devoted interest to neural stem cells and pass a Turing test.
Step 4: Upload. After logging in, the user can upload the three files to the server. After clicking submit, the job will be executed on the server. Running time is approximately 3-4 hours but may be longer if others are also running. The user will receive an email with the results attached when the job is completed. If you do not receive an email within 4 hours, please first check the FAQs page and if your problem is not solved, send an email to the developers.