Hi @billy.l
It looks like a server issue. Maybe the server admins can help? ping @nate
Here is my history Galaxy
The links are in limma-voom Report datasets.
I tried several limma-voom versions,
Kind regards,
Igor
I was originally testing with an older dataset. I just reviewed another older rerun with the older version of Limma and it produced a report with usable Glimma graphics! So, the problem is inconsistent and appears to have been resolved some time ago (between March and May of 2021).
You could also simply rerun without changing the tool version to see if that is enough. If not, please share back your history so I can review your original run, the rerun, and the tool version. Maybe there is something else going on now.
Glimma reports seem to be working for me at UseGalaxy.org when using the most current version of the tool.
limma Perform differential expression with limma-voom or limma-trend (Galaxy Version 3.58.1+galaxy0)
However, I can reproduce the problem when running a much older version. It appears to have an installation problem. I’ve ticketed the issue here → (link pending) Not reproducible!
limma Perform differential expression with limma-voom or limma-trend (Galaxy Version 3.38.3+galaxy3)
What to do
Go to your existing dataset run of Limma (that used the older version)
Should you have a workflow yourself, or if you are using a tutorial workflow, and either includes the problematic tool version, try updating the workflow to use the newer tool version. Note: new tool versions do not always change the output, since some are technical changes (improved performance, bug fixes). I can’t think of a meaningful difference with respect to the tutorial above, or the one after, so this workaround should be fine if that is what you are doing.
Thanks for reporting the problem! And thanks for the ping @igor
Thanks @jennaj ! I rechecked the informations on my limma reports today and it seems that I was using the latest 3.58.1 when I encountered the problem. The glimma links work now. I also remember when I downloaded the reports and used the html link locally, the interactive page works. So I’m now just wondering if the problem was confined to that earlier date, and whatever that problem was, it’s fixed now.