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
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.
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.
The text was updated successfully, but these errors were encountered:
Have you checked the docs?
Description of the bug
Several issues found for module gprofiler2/gost:
--organism mmusculus
or notRunning 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.set_base_url
and then rungost
on an archived database works locally but somehow gives error in the CI (https://github.com/nf-core/modules/actions/runs/13199316156/job/36850361811)gmt_file
given by user, iforganism
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 rungost
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 howgost
interact with old archives.The text was updated successfully, but these errors were encountered: