Re: [galaxy-dev] Problem previewing a tool in the Toolshed

2012-02-29 Thread Carlos Borroto
Hi Greg, After restarting the galaxy instance to get a hold on the starting log, sqlite now shows up in the upload form. I was able to reproduce this behavior in a clean instance. The problem now is I'm back to getting: "An error occurred running this job: The uploaded binary file contains inappr

Re: [galaxy-dev] Problem previewing a tool in the Toolshed

2012-02-29 Thread Greg Von Kuster
Is your datatype lading into your Galaxy instance correctly (either when you start your Galaxy instance or when you install your tool from the tool shed)? If so, it should be displaying in the upload form. What does your paster log say? On Feb 29, 2012, at 1:06 PM, Carlos Borroto wrote: > H

Re: [galaxy-dev] Problem previewing a tool in the Toolshed

2012-02-29 Thread Carlos Borroto
On Wed, Feb 29, 2012 at 12:28 PM, Peter Cock wrote: > On Wed, Feb 29, 2012 at 5:14 PM, Greg Von Kuster wrote: >> Hi Carlos, >> >> You can certainly add support for a sqlite database datatype to your local >> galaxy instance.  As you say, it may be no more complex / fragile than h5 >> or other bin

Re: [galaxy-dev] Problem previewing a tool in the Toolshed

2012-02-29 Thread Carlos Borroto
Hi Greg, I did follow that link and I think the datatypes_conf.xml in the tool repository is correctly written: I thought by adding display_in_upload="true" that would make the datatype to appear as an option when uploading a file, but this is not happening. Do I need to declare typ

Re: [galaxy-dev] Problem previewing a tool in the Toolshed

2012-02-29 Thread Peter Cock
On Wed, Feb 29, 2012 at 5:14 PM, Greg Von Kuster wrote: > Hi Carlos, > > You can certainly add support for a sqlite database datatype to your local > galaxy instance.  As you say, it may be no more complex / fragile than h5 > or other binary datatypes - I've not gone far enough down the analysis p

Re: [galaxy-dev] Problem previewing a tool in the Toolshed

2012-02-29 Thread Greg Von Kuster
Hi Carlos, You can certainly add support for a sqlite database datatype to your local galaxy instance. As you say, it may be no more complex / fragile than h5 or other binary datatypes - I've not gone far enough down the analysis path to provide good reasons why it may or may not be reasonable

Re: [galaxy-dev] Problem previewing a tool in the Toolshed

2012-02-29 Thread Carlos Borroto
Hi Greg, Thanks for looking and resolving this issue. After deleting all the files in the repo and re-adding them, everything is working as expected. Please see my comments inline about the other two issues. On Tue, Feb 28, 2012 at 1:57 PM, Greg Von Kuster wrote: > Hi Carlos, > > I've uploaded

Re: [galaxy-dev] Problem previewing a tool in the Toolshed

2012-02-28 Thread Greg Von Kuster
Hi Carlos, I've uploaded a fix for the problem you saw when attempting to reset all metadata on your cummerbund tool. Thanks for reporting this issue. Looking at your change sets, it seems that you are attempting to use the public tool shed hosted by Penn State as a source code repository for

Re: [galaxy-dev] Problem previewing a tool in the Toolshed

2012-02-15 Thread Carlos Borroto
Hi Greg, Thanks for your answer. Would be great to get the tool to preview correctly but is not a big deal. I'm having a few more problems. I'm getting this error from time to time when I do "hg push" or even when I delete all files from the toolshed and upload new ones: "Version information for

Re: [galaxy-dev] Problem previewing a tool in the Toolshed

2012-02-14 Thread Greg Von Kuster
Hi Carlos, Not every tool form parameter will properly display when previewing the tool in the tool shed because the tool shed doesn't have access to some Galaxy components (e.g., a Galaxy history ) that are required for some tool parameter types. When I get a chance, I'll take a closer look,

[galaxy-dev] Problem previewing a tool in the Toolshed

2012-02-14 Thread Carlos Borroto
Hi, I'm currently developing my first Galaxy tool. I'm working on a wrapper for R's library cummeRbund[1]. I got to the point where the tool although incomplete on functionality, I think is ready to be uploaded to the Toolshed. I was able to do so. I also made sure I could then install it on my lo