-
Notifications
You must be signed in to change notification settings - Fork 6
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
Error: group_humann2_uniref_abundances_to_go #42
Comments
Hi ..do we have an update on the new version for Group Abundance tool! |
@bebatut It seems like you fixed this on your stand-alone tool as seen in this commit. The issue here is that it has not been updated on the usegalaxy.eu dependency side. Reinstalling the tool might fix it. For example: Prior to 8/4/16, the
Post 8/4/16 (after the remediating commit), the code was bumped up to line 70.
The error @subinamehta posted shows an error from the previous version. On that note... If we reinstall it, should we remove the Galaxy Toolshed packages in the wrapper and use Conda recipes instead? Here are my proposed changes. |
Thanks @jraysajulga for investigating. I did not remember this change... Yes we should remove the full |
@bebatut. The conda recipes are up-to-date if we update Humann2 to 0.11.2. How about the group_abundances script? The conda recipe doesn't seem to work... Should we keep that portion in the tool_dependencies.xml? |
so we should make the conda recipe work. What is failing for it? |
|
@bebatut I looked more into it. The Conda recipe is still drawing from version 1.2.0 (has the error described above). So, on the ASaiM/group_humann2_uniref_abundances_to_GO GitHub repo, we should publish another version (ex: 1.2.1) that contains the UNGROUPED fix. Then we can update the Conda recipe (meta.yaml) to use the updated source: |
@bebatut
I ran the ASAIM workflow on usegalaxy.eu. The tool group_humann2_uniref_abundances_to_go gets completed but doesn't give an output apart from the header. I looked at the stderr and it showed me the error pasted below.
Error:
The text was updated successfully, but these errors were encountered: