Skip to content
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

filtering GSEA results by NES assumes positives are in one file and negatives are in another #526

Open
risserlin opened this issue Aug 10, 2023 · 3 comments
Labels
Milestone

Comments

@risserlin
Copy link
Contributor

Using FGSEA to analyze data and create "fake" GSEA results files but putting all results into one file (with both positive and negative in the same file to reduce amount of files that I create).
Run EM with "NES (GSEA) only option --> positive" and it shows both positive and negative results.

If you then divide the file, one positive with +ve NES values and one negative with all the -ve NES values, then it works.

Problem - if you put the negative file in the positive spot in the input panel and the positive file in the negative spot in the input panel EM creates the wrong network and assumes the negative file are actually positive!

@risserlin risserlin added the bug label Aug 10, 2023
@mikekucera mikekucera added this to the 3.4.0 milestone Mar 11, 2024
@mikekucera
Copy link
Contributor

What is the format of the header row of your files? It looks like EM is assuming that GSEA results have 11 columns.

@risserlin
Copy link
Contributor Author

here is the header row for fGSEA results that I have created -
name description GS details SIZE ES NES pval padj FWER Rank at Max leading edge genes
(truthfully I am not sure which file the above is referring to but I have a generic method for creating fGSEA results and they all look like this)

@mikekucera
Copy link
Contributor

Hi Ruth,
What is the actual problem? I just tried creating a network from a GSEA data set and I swapped the positive and negative files and it appears to still have worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants