Would you mind please replying to us over on our private email address,
gsea...@broadinstitute.org? We don't send out these older versions through the public forum. It would be most helpful if you could provide a copy of the data causing the issue so we can investigate further. We will keep the data private and use it only for testing.
I should point out a few important things that might make you reconsider using GSEA 4.1.0:
- These older releases use Log4J which had severe security vulnerabilities reported. You are taking a risk installing this software and, if you are part of an institution, your IT department might require it to be removed.
- There are significant improvements coming soon and these will be based on the current code. By choosing to stick with an older version you will not have access to these improvements.
- This message indicates an actual problem with your data combined with the chosen analysis parameters. You would be better served trying to solve this problem than to work around it with an old version.
I should expand on this third point. We've actually fixed a number of bugs in this release which could be making the difference in this case, where an error condition spotted in 4.2.3 was somehow missed in 4.1.0. We fixed a number of issues related to metrics in this release and this is almost certainly one of them.
Regardless, this error message is real and points to a problem. Fixing that might involve changing your analysis parameters or doing some data preprocessing.