-
Notifications
You must be signed in to change notification settings - Fork 414
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
Wigbigwig #5704
Wigbigwig #5704
Conversation
blastxml doesn't crash - hard to test..
…nditionals. Such fun was had discovering this.
…- a test would be needed.
…a but need a proper reference/maf test
@bgruening no, I had accidentally edited the moab/tool_data_table_conf.xml.test so planemo was mixing things up. If you look higher up you'll see planemo linting moab. Seems fine now but it was an interesting experience to track it down...
|
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.
Would be cool to have this included here: https://github.com/galaxyproject/tools-iuc/tree/main/tools/ucsc_tools
tools/wigtobigwig/wigtobigwig.xml
Outdated
@@ -0,0 +1,133 @@ | |||
<tool id="wigtobigwig" name="Wig-BedGraph-to-bigWig" version="1.1.2" profile="22.05"> |
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 us a version macro and used here and in the requirement version.
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.
Can you open a PR removing the tool from the Galaxy code base / at least from the tool conf https://github.com/galaxyproject/galaxy/blob/fd45e1bd9fc1f351bb2bb203659758b13173d94c/lib/galaxy/config/sample/tool_conf.xml.sample#L78
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.
Maybe we can prefix the tool name by UCSC?
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.
Can you open a PR removing the tool from the Galaxy code base / at least from the tool conf https://github.com/galaxyproject/galaxy/blob/fd45e1bd9fc1f351bb2bb203659758b13173d94c/lib/galaxy/config/sample/tool_conf.xml.sample#L78
No, this needs to stay for reproducibility.
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.
You can hide it though (hidden="True"
in the tool conf file)
tools/wigtobigwig/wigtobigwig.xml
Outdated
#else: | ||
-clip | ||
#end if | ||
2>&1 || echo "Error running wigToBigWig." >&2 |
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.
Would prefer that stderr is not redirected to stdout.
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.
This is what the converter code has been since lasted touched 6 years ago :)
Not my idea but of course.
tools/wigtobigwig/wigtobigwig.xml
Outdated
@@ -0,0 +1,133 @@ | |||
<tool id="wigtobigwig" name="Wig-BedGraph-to-bigWig" version="1.1.2" profile="22.05"> | |||
<description>bedGraph or Wig to bigWig converter</description> |
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.
Just make this the tool name and remove the descrpition.
tools/wigtobigwig/wigtobigwig.xml
Outdated
</when> | ||
</conditional> | ||
<conditional name="settings"> | ||
<param name="settingsType" type="select" label="Converter settings to use" help="Default settings should usually be used."> |
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.
Can you make the indentation consistent?
tools/wigtobigwig/wigtobigwig.xml
Outdated
<conditional name="hist_or_builtin"> | ||
<param name="genome_type_select" type="select" label="Reference genome source" | ||
help="Was the Wig/bedgraph input constructed using a genome from your history, or a built-in genome?"> | ||
<option selected="True" value="indexed">Input data is for a built-in genome</option> |
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.
Can you add a test for the indexed
case?
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 cannot.
I have tried. Cannot get anyting to work in CI even if it passes biocontainer and ordinary tests - so someone will need to help out for that to work. Please fix if you know how. It's an odd situation because the genome is being read as metadata from the input, Not sure how to do that in tests so advice appreciated..
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.
Can you add the test case that should run .. then we can have a look on the error.
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.
will do tomorrow. Late here.
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.
Turns out to not be easy. chromInfo
seems to be a special case in Galaxy. I added a test but disabled it.
@bernt-matthias - it's up to the iuc to decide where it goes. I don't mind at all. How does the iuc decide where it wants this? |
There is no standard. I just like to have tools coming from the same source close together. |
@fubar2 I can take this over if you like. Thanks for your work! |
|
Ok, I moved the wrapper and fixed the review comments. |
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.
chromInfo also works (tested locally) .. but if I'm not wrong __dbkey__
is the better and testable way to go.
now present at IUC galaxyproject/tools-iuc#5704
now present at IUC galaxyproject/tools-iuc#5704
FOR CONTRIBUTOR:
What:
Why:
Moving this to the IUC was suggested by @mvdbeek in galaxyproject/galaxy#17261 (comment)
Ross agrees - the codebase is designed to be flavoured with plugin tools. Moving text/genome built in tools to IUC suites makes a lot of sense to me in the long term since not every server wants or needs them. They will all possibly want the upload tool.
Simpler and modular is going to help make the codebase more sustainable and the IUC seems a natural way to deal with these tools as they need fixing going forward. Not arguing for rip and replace - not broken enough and no resources...