-
Notifications
You must be signed in to change notification settings - Fork 448
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
Added AEGeAn toolkit #3397
Added AEGeAn toolkit #3397
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this the tool? https://bio.tools/gaeval If so can you add a bio.tools ID and edam ontologies to this tool here (probably as macros)
Please use 4 spaces indentation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @gallardoalba
tools/aegean/.shed.yml
Outdated
@@ -0,0 +1,14 @@ | |||
name: suite_aegean |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gallardoalba if you have multiple tools in such a suite, please use a suite-shed.yml file ... example here: https://github.com/galaxyproject/tools-iuc/blob/master/tools/hyphy/.shed.yml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you give me more details about which part should I modify? Should I just need to add it?
auto_tool_repositories: name_template: "{{ tool_id }}" description_template: "Wrapper for the HyPhy batch operation: {{ tool_name }}"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please see here: https://planemo.readthedocs.io/en/latest/standards/docs/best_practices/shed_yml.html#advanced-parameters
Also there are a lot of examples in this repo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I modified it; I guess that now is correct.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please see here: https://github.com/galaxyproject/tools-iuc/blob/master/tools/dada2/.shed.yml (note that the duplicate category entry is not necessary).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @bernt-matthias, when should I use auto_tool_repositories in the .shed.yml file? I read about it but I'm confused because it does not appear in many cases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's the way to go if you want to add a set of tools in a single directory.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that now it fits with that structure.
Test file canon-output_test3.gff3 is missing and one other test is failing with |
Test variable format. Co-authored-by: M Bernt <[email protected]>
Test variable format. Co-authored-by: M Bernt <[email protected]>
Sure, I'll include it. |
Hi @gallardoalba I fixed the outputtype problem here: 3859099 Could you also use |
Btw. is it intended that sections are not expanded? |
HI!, do you think that it is better to expand them by default? Also, I'm trying to solve the html issue (link the html file with the css which is generated in the same folder), but not sure what it doesn't work. |
Depends. I would expand them if the intention of sections is to structure the options and hide them if they contain only advanced options.
What exactly is the problem. I could have a look tomorrow. |
Thanks! Bjorn helped me to find the problem with the css file. About the sections, I have expanded those that I consider basics. |
Excellent. Just noticed that the html output is incomplete (reported upstream here: BrendelGroup/AEGeAn#257). Since the browser still renders this nicely we can go ahead and merge this anyway .. or wait for the feedback of the author. |
@bernt-matthias your call :) |
Lets wait for the fix. Seems that @gallardoalba is on it. |
Fixed. Let me know if any additional modification is necessary. |
Great work @gallardoalba |
Thank you and @bgruening for your help. |
FOR CONTRIBUTOR:
Four tools belonging to the AEGEaN toolkit have been added: