pyGenomeTracks needs a proper Galaxy integation. We will work on this as soon as we are back. hiCPLotTads has the TAD plot currently mandatory, that needs to be changed.
I think we are going to deprecated the hicPLotTads in favor of pyGenomeTracks
Gildas Le Corguillé
@lecorguille
Hum … I though that there was a tool within planemo to test a whole workflow but I can’t find where. Did I dream?
I am not sure which tool version, Galaxy version, etc is in use and I pointed them here for help. I don't know either of these wrappers well enough to help.
Alexander Lenail
@zfrenchee
What is the system path for the local reference data config file in galaxy?
yeah, it's the gene_id/transcript_id being the same value in UCSC GTFs. I know why the TB outputs the data that way but many people completely miss it .. and then get odd results --since the counts are really by transcript, not gene :(
Björn Grüning
@bgruening
either way I added a small comment to biostar, feel free to accept the answer :)
would be nice to ping them, if they are willing to update them and maybe contribute to IUC or offer conda integration
Jennifer Hillman-Jackson
@jennaj
ooh - I couldn't find that link!
Ok, I'll share that with the biostar post. I think someone from IUC should make contact, yes? And they were a sponsor, maybe this will work out :)
_
Björn Grüning
@bgruening
@jennaj I think you should make contact :)
You Main team member :)
Jennifer Hillman-Jackson
@jennaj
Ah, ok, will check with team first to make sure there isn't some contact going on already. Thanks!
Björn Grüning
@bgruening
Thanks Jen!
mblue9
@mblue9
Thanks to @jennaj and @bgruening for the notifications about those Biostars posts on Cutadapt featureCounts! (It made me finally get around to making a Biostars account :smile:)
Jennifer Hillman-Jackson
@jennaj
@CollardT You are working on the updated Ballgown wrapper, correct? A question came in about an error.
I haven't seen this before so don't know how to solve it or if this is a known issue -- is there anything you would like to add to my reply? https://biostar.usegalaxy.org/p/27454/
The tool is not installed at either usegalaxy.* .. so this error is on a local, docker, etc with the tool installed from the existing MTS repo
Jennifer Hillman-Jackson
@jennaj
Is this a bug with Salmon output files? Or should the output format be configurable? Seems like a normal use case, but I haven't used the tool that much. https://biostar.usegalaxy.org/p/23985/#27525
Oleksandr Moskalenko
@moskalenko
I'm doing a lot of tool installs to switch to conda for 18.01 from my much older previous production instance and I'm noticing a few broken packages in the toolshed. Where should I report the bugs?
@yhoogstrate Do you know if there are plans to update Varscan to include the newer "somatic" function? If not, what would be your (and others) suggested tool alternative?
Oh! I found the tools at usegalaxy.eu. Not sure how I missed those in the MTS! I'll point the user to the other server. Tx!
Alexander Lenail
@zfrenchee
Is it possible in 18.01 to run tools on subsets of collections, or to "explode"/"eject" collections into individual history items?
Alexander Lenail
@zfrenchee
@jmchilton
John Chilton
@jmchilton
You can drag and drop individual items into the tool form - if you have a more systematic way to indentify the elements there is also a tool that filters a collection from a tabular file - this isn’t super straight forward but it enables a high level of tracking and use within workflows
There isn’t an explode tool though in 18.05
I meant 18.01
Alexander Lenail
@zfrenchee
Thanks!
Jennifer Hillman-Jackson
@jennaj
Does anyone know if Deseq2 in Galaxy can be configured to run with single-end data? Or is paired-end input required?