-
Notifications
You must be signed in to change notification settings - Fork 22
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
merging Nhood with logFC of opposite sign #270
Comments
Hi @gianfilippo as stated on the github repo landing page please report the output of your sessionInfo() when reporting issues. |
sorry about it. Here it is Matrix products: default locale: attached base packages: other attached packages: loaded via a namespace (and not attached): |
Please up date Milo the current Bioc release first. |
Hi, da_results = groupNhoods(miloOBJ, da_results, da.fdr=0.05) logFC PValue FDR Nhood SpatialFDR NhoodGroup What do you think ? Thanks |
Have you previously run |
Hi, I start from a Seurat integrated object, scdata. Then |
Ok - either don't run |
I will give a try to both options Thanks |
Hi, I tried both suggestions. Here are the results:
What do you think ? What am I doing wrong ? |
Hi, did you have time to look into this issue ? Thanks |
I seems that if I define subset.nhoods (= to the DA Nhoods in my case), the logFC are concordant within each group, although the logFC difference can be larger than the max.lfc.delta. |
Any update on this @MikeDMorgan |
my present solution is to use a combination of cell cluster and logFC sign to define groups. I am not sure about "mixed" nhoods, should I include them in marker analysis or filter them out ? |
hoping for an update on this, thank you! |
Hi,
I am running the groupNhoods function on the da_results data.frame.
The da_results shows the following
logFC logCPM F PValue FDR Nhood SpatialFDR
946 6.555608 7.725746 20.33434 3.864789e-04 0.2744 946 0.2281628
1221 -2.679248 8.772024 26.29051 9.286647e-05 0.2744 1221 0.2281628
2178 -3.034338 8.446574 20.82294 3.465521e-04 0.2744 2178 0.2281628
2248 -2.549574 8.700925 20.51058 3.239712e-04 0.2744 2248 0.2281628
2291 -3.060969 8.536979 22.01882 2.303425e-04 0.2744 2291 0.2281628
da_results = groupNhoods(miloobj, da_results, da.fdr=FDR)
logFC logCPM F PValue FDR Nhood SpatialFDR. NhoodGroup
946 6.555608 7.725746 20.33434 3.864789e-04 0.2744 946 0.2281628. 9
1221 -2.679248 8.772024 26.29051 9.286647e-05 0.2744 1221 0.2281628. 14
2178 -3.034338 8.446574 20.82294 3.465521e-04 0.2744 2178 0.2281628. 9
2248 -2.549574 8.700925 20.51058 3.239712e-04 0.2744 2248 0.2281628. 1
2291 -3.060969 8.536979 22.01882 2.303425e-04 0.2744 2291 0.2281628. 1
It looks like the Nhoods 946 and 2178 are placed in teh same group, even though the logFC is of opposite sign.
Note: I am using a FDR cut-off of 0.25, because in this run I only had N=2
I am running miloR version 1.5.0
Am I missing something ?
Thanks
The text was updated successfully, but these errors were encountered: