You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are urrently working on our 4th project using SCENIC. So far we have obtained good results, thank you for this amazing tool!
The usual workflow has been to use the CLI tool in a pipeline and after explore the results in a script: binarize, generate regulon tables, RSS, binary UMAPS, both for precalculated UMAP/tSNE in parallel Seurat analysis as well for auc_mtx UMAP, generate case and control comparatives if the experimental design allows and finally the clustermap for regulons vs cell clustering.
Roughly: From raw counts -> Filter cells -> Format dataset in loom file -> GRN (a)-> CTX (b) -> AUCELL (c) -> Script for SCENIC downstream.
Currently testing the other way proposed in the most recent paper, with the functions: grnboost2() (a) -> modules_from_adjacencies() -> prune2df() -> df2regulons() (b) -> aucell() (c) -> Script for SCENIC downstream.
Step (a) gives the same results both from CLI as well as the script.
Step (b) gives different results both in format and content.
Note about the format of the output:
ctx from CLI outputs a .csv where different modules (TFs - targets) with their motif ID can be observed together with other 7 Enrichment metrics. Where no direct regulon list can be observed (I'm assuming it is derived by merging all TFs-Targets modules)
On the other hand, from the sequence of functions to obtain regulons from the adjacencies in the script only the regulon list with importance values is stored (prune2df() function stores the rest of the metrics but this is not exported in the tutorials)
Step (c) gives same number or different number of regulons depending on the dataset but altogether different sets of regulons
Both analysis are using same annotations table v10.
Both analysis have been repeated and results are consistent between runs.
So, apparently Step (b) which would be Module generation with Motif enrichment and TF-regulon prediction (cisTarget step) has differences between pySCENIC CLI and pySCENIC script, how come?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi everyone,
We are urrently working on our 4th project using SCENIC. So far we have obtained good results, thank you for this amazing tool!
The usual workflow has been to use the CLI tool in a pipeline and after explore the results in a script: binarize, generate regulon tables, RSS, binary UMAPS, both for precalculated UMAP/tSNE in parallel Seurat analysis as well for
auc_mtx
UMAP, generate case and control comparatives if the experimental design allows and finally the clustermap for regulons vs cell clustering.Roughly:
From raw counts -> Filter cells -> Format dataset in loom file -> GRN (a)-> CTX (b) -> AUCELL (c) -> Script for SCENIC downstream.
Currently testing the other way proposed in the most recent paper, with the functions:
grnboost2() (a) -> modules_from_adjacencies() -> prune2df() -> df2regulons() (b) -> aucell() (c)
-> Script for SCENIC downstream.Note about the format of the output:
ctx
from CLI outputs a.csv
where different modules (TFs - targets) with their motif ID can be observed together with other 7 Enrichment metrics. Where no direct regulon list can be observed (I'm assuming it is derived by merging all TFs-Targets modules)prune2df()
function stores the rest of the metrics but this is not exported in the tutorials)So, apparently Step (b) which would be Module generation with Motif enrichment and TF-regulon prediction (cisTarget step) has differences between pySCENIC CLI and pySCENIC script, how come?
Hope it's clear the question,
Thank you so much,
Sebastián Zúñiga.
here's my session_info()
Beta Was this translation helpful? Give feedback.
All reactions