Skip to content
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

Merged
merged 43 commits into from
Jan 3, 2021
Merged

Added AEGeAn toolkit #3397

merged 43 commits into from
Jan 3, 2021

Conversation

gallardoalba
Copy link
Contributor

FOR CONTRIBUTOR:

  • - I have read the CONTRIBUTING.md document and this tool is appropriate for the tools-iuc repo.
  • - License permits unrestricted use (educational + commercial)
  • - This PR adds a new tool or tool collection
  • - This PR updates an existing tool or tool collection
  • - This PR does something else (explain below)

Four tools belonging to the AEGEaN toolkit have been added:

  • ParsEval is a program for comparing distinct sets of gene structure annotations for the same sequence(s).
  • CanonGFF3 is a tool for preprocessing GFF3 data.
  • LocusPocus is a program for computing gene loci from one or more gene prediction sets.
  • GAEVAL is a program for computing coverage and integrity scores for gene models using transcript alignments.

Copy link
Member

@bgruening bgruening left a 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

@gallardoalba gallardoalba changed the title Added AEGeAN toolkit Added AEGeAn toolkit Dec 25, 2020
Copy link
Member

@bgruening bgruening left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @gallardoalba

@@ -0,0 +1,14 @@
name: suite_aegean
Copy link
Member

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

Copy link
Contributor Author

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 }}"

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

@gallardoalba gallardoalba Dec 28, 2020

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.

Copy link
Contributor

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).

Copy link
Contributor Author

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.

Copy link
Contributor

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.

Copy link
Contributor Author

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.

@bgruening
Copy link
Member

Test file canon-output_test3.gff3 is missing and one other test is failing with Please only use letters, numbers or underscores in sample label

gallardoalba and others added 2 commits December 29, 2020 21:33
Test variable format.

Co-authored-by: M Bernt <[email protected]>
Test variable format.

Co-authored-by: M Bernt <[email protected]>
@gallardoalba
Copy link
Contributor Author

Great work @gallardoalba

A few more comments from my side .. I consider all of them as optional. The tools are already good to go.

Just let us know if you want to implement any of them or not.

Sure, I'll include it.

@bernt-matthias
Copy link
Contributor

bernt-matthias commented Jan 1, 2021

Hi @gallardoalba I fixed the outputtype problem here: 3859099

Could you also use argument instead of name as in 37fed22 (and edba35e) in the other tools. The name is generated automatically and the advantage is that the user will see the argument in the parameter help.

@bernt-matthias
Copy link
Contributor

Btw. is it intended that sections are not expanded?

@gallardoalba
Copy link
Contributor Author

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.

@bernt-matthias
Copy link
Contributor

Btw. is it intended that sections are not expanded?

HI!, do you think that it is better to expand them by default?

Depends. I would expand them if the intention of sections is to structure the options and hide them if they contain only advanced options.

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.

What exactly is the problem. I could have a look tomorrow.

@gallardoalba
Copy link
Contributor Author

gallardoalba commented Jan 2, 2021

Btw. is it intended that sections are not expanded?

HI!, do you think that it is better to expand them by default?

Depends. I would expand them if the intention of sections is to structure the options and hide them if they contain only advanced options.

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.

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.

@bernt-matthias
Copy link
Contributor

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.

@bgruening
Copy link
Member

@bernt-matthias your call :)

@bernt-matthias
Copy link
Contributor

Lets wait for the fix. Seems that @gallardoalba is on it.

@gallardoalba
Copy link
Contributor Author

Lets wait for the fix. Seems that @gallardoalba is on it.

Fixed. Let me know if any additional modification is necessary.

@bernt-matthias bernt-matthias merged commit e6c0151 into galaxyproject:master Jan 3, 2021
@bernt-matthias
Copy link
Contributor

Great work @gallardoalba

@gallardoalba
Copy link
Contributor Author

Great work @gallardoalba

Thank you and @bgruening for your help.

@gallardoalba gallardoalba deleted the aegean-toolkit branch January 3, 2021 15:32
@gallardoalba gallardoalba restored the aegean-toolkit branch January 5, 2021 19:17
@gallardoalba gallardoalba deleted the aegean-toolkit branch January 5, 2021 19:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants