-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/17/2014 12:10 PM, Björn Grüning wrote:
Am 17.07.2014 18:51, schrieb Peter Cock:
On Thu, Jul 17, 2014 at 5:45 PM, Björn Grüning <bjoern.gruening@gmail.com> wrote:
Hi,
I think you are right John. Datatypes have many issues in that regard as I can tell, from a few bug reports. Imho datatypes should be handled like "Tool dependency definitions". There should be only one "installable revsion".
But that aside, emboss datatypes are already broken. For example asn1 was added into Galaxy but it still exists in emboss_datatypes.
Moreover, howto add a proper genbank datatype with sniffer, split and merge functions? Ideally, every datatype should have its own repository, but that is an overhead I would like to omit ... any other ideas?
We could use something like what I do, CI scripts and hidden .yaml files to manage which folders get pushed to which toolshed repositories and when. My initial version of that blindly updates things when there are changes, but I'm working to add support for things like "create a new versioned toolshed repository on major version # changes". That would remove a lot of the overhead for maintaining that many repositories.
I would love to discuss that issue further, maybe a hangout with Greg and Peter?
Thanks John for your input, Bjoern
This could be high level, e.g. "other sequence file formats" repository covering GenBank, EMBL, SwissProt plain text, UniProt XML, etc; one for multiple sequence alignments; one for EMBOSS' own output...
That was my initial idea. Starting point is here: https://github.com/bgruening/galaxytools/tree/master/datatypes
But it wouldn't be that much more work to do one ToolShed repo per additional file format, would it?
Uploading and creating descriptions in the toolshed will take most of the time :) Lets see if I can use a train trip to do that ... but the problem will stay the same ... one repository can have multiple versions ...
And how to solve that? You're right, datatypes shouldn't have multiple revisions since the file format should not be changing. I don't have an answer for this either unfortunately :/
One reason I have been meaning to do some of these is familiarity with many of these formats from looking after/writing parsers in Biopython.
Peter, similar case here with BioPerl. All of my tools can output the full range of Bio::SeqIO output formats, so having datatypes would be great. Happy to contribute there.
Having this done sooner rather than later ought to head off too many incompatible datatype names which worries me. Is it too late to adopt something like the EDAM ontology for the datatypes within Galaxy?
Peter
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
- -- Eric Rasche Programmer II Center for Phage Technology Texas A&M University College Station, TX 77843 404-692-2048 esr@tamu.edu rasche.eric@yandex.ru -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJTyAfbAAoJEMqDXdrsMcpVcFUQAJMQMyZ7eDM3fDhppOHjPgxU 16hpuQ14MW2UqZsAl4V0H8R+1C1xnBIH1rErUPfvaloEAVk6FWogDY5L79XHz6b5 6G7UkDM+7K+zKb6pDyVynm8Kx5Kg+D7gHtu0R2HTFxYGRhVbuldskKJfp9g8aziP NPVALTLUi+hotzsNSJpP8rBct6WYWNNIM3o1TIKLVVsQfrhlTfYXuYF8Xb0n8GTs Tf3ad6ZIY7BJTftGdlzE0O3ZPgXe5J/cb9RCyzTN69R6uKUIhg1XaOGHlA+JubbG 161e9fiuNzFF54bmQZYCIZTR9YBPF7aRjRQJcRVjBvTaQ3NbTmUdzvhW1fLT9Yuv 8WPVKIyB0lWECVx85fuSGE1PH7rwJZATO0bkHgsxqUT2TI7TFy0HWl6hJaPolP5/ 1u3uvvsBu4aDiBK9uI+fzkqn+fu4D+A8GwllL0sOsyNcDlbjBUXWfYA0xVI41+m1 PFeQ6MRHf332kY/iqhnX5GJfzQIp0KHmEwpDTzwa9SkDSnZm7SLhZi46vFZpQAgR AvBObz8ztstZP9yRwNF1cXYIap+tFQ0vKa9uqNTeC3sTWwypsK5SKl1jCfHUI71T saxqNuML+G+uJiVPaFmeh19eVrHAPSR1oQLYl0fC2X4Qt9Jw2/Tgj8cEl08Cj3NO LAMs0NIOwRhkJ556uA/P =JeRi -----END PGP SIGNATURE-----