|
|
Post by DAVID user on Jul 22, 2020 10:58:06 GMT -5
Based on the release note, GO category (GO Direct) provides GO mappings directly annotated by the source database (no parent terms included) and GO category (GO FAT) filters out very broad GO terms based on a measured specificity of each term (not level-specificity). Is there a reason why "GO direct" is chosen as the default? Thanks.
|
|
|
|
Post by DAVID user on Jul 22, 2020 10:58:34 GMT -5
In our analysis, we prefer the more specific terms which is why we created GO FAT as opposed to GO Slim sets that typically include the broader, more non-specific terms (http://geneontology.org/docs/go-subset-guide/). As Gene Ontology has grown we felt that the GO Direct mappings offered a sufficient set of terms as a default for DAVID tools. However, these defaults are easily customized in the Annotation Summary view. For example, by unchecking the GO Direct categories in the summary and checking the GO Fat, GO All, etc categories, these categories will now be included in the Table, Chart and Clustering output..  |
|
|
|
Post by DAVID user on Jul 22, 2020 10:59:42 GMT -5
Thank you so much for your response.
|
|
