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

issues with gprofiler2/gost #7451

Open
2 tasks done
suzannejin opened this issue Feb 7, 2025 · 0 comments
Open
2 tasks done

issues with gprofiler2/gost #7451

suzannejin opened this issue Feb 7, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@suzannejin
Copy link
Contributor

suzannejin commented Feb 7, 2025

Have you checked the docs?

Description of the bug

Several issues found for module gprofiler2/gost:

  1. Inconcistency between using --organism mmusculus or not
    Running with --organism mmusculus vs running with --organism null --gmt_file gprofiler_full_mmusculus.ENSG.gmt (gmt obtained by downloading from their website) will return different results.
  2. Fixing the database using set_base_url and then run gost on an archived database works locally but somehow gives error in the CI (https://github.com/nf-core/modules/actions/runs/13199316156/job/36850361811)
  3. By default, the module will not use the gmt_file given by user, if organism is specified. Maybe it should be the other way around?

Other issues that makes testing the module using nf-test difficult:
4. Fixing the database using set_base_url and then run gost on an archived database is extremely slow even for test dataset (about 8 min vs 30s when using the updated database). Not sure why, but it could be related to how gost interact with old archives.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant