-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with running scenicplus grn_inference eGRN
#532
Comments
Hi @zhli12 This error would occur when an empty dataframe is passed to Can you check wether any of these dataframes is empty import pandas as pd
region_to_gene = pd.read_table("bulk_region_to_gene_adj2.tsv")
CORRELATION_COEFFICIENT_NAME="rho"
rho_threshold=0.001
repressing_adj = region_to_gene.loc[
region_to_gene[CORRELATION_COEFFICIENT_NAME] < -rho_threshold]
activating_adj = region_to_gene.loc[
region_to_gene[CORRELATION_COEFFICIENT_NAME] > rho_threshold]
print(f"Repressing: {len(repressing_adj)}")
print(f"Activating: {len()activating_adj}") Best, Seppe |
Hi Seppe, Thank you for your reply! The output to the code you suggested is
As this suggests that the issue might be caused by the inclusion of repressing enhancers, I modified the scenicplus parameters to
where I added the addition argument However, even with this modification, I still get the same error. I'm not whether this is because setting |
Hello,
When trying to run the command
scenicplus grn_inference eGRN
, I received an error sayingafter the message "GSEA INFO Thresholding region to gene relationships".
The function worked fine when I ran the tutorial, so it's probably not an issue with package versions. However, for my purpose, I am using bulk ATAC-seq data instead, so I modified the
region_to_gene_adj_fname
where the region-gene relationship is entirely based on a distance cutoff with correlation and importance being a constant (I've attached the screenshot below).The full command I used is
I'm wondering whether anyone has tried something similar or has some idea on how to fix the error. Any help would be greatly appreciated!
The text was updated successfully, but these errors were encountered: