It doesn't look like you're using workflow parameters in this workflow. Or were you trying to, and something perhaps went wrong? As to your "None" error, in the sort in step 21 of the workflow you shared it looks like the column selection is None, and I'm guessing that's the problem here. Let me know if entering a valid column there doesn't resolve this and I can investigate. -Dannon On Apr 20, 2011, at 12:47 PM, David Matthews wrote:
Done, many thanks...
Best Wishes, David.
__________________________________ Dr David A. Matthews
Senior Lecturer in Virology Room E49 Department of Cellular and Molecular Medicine, School of Medical Sciences University Walk, University of Bristol Bristol. BS8 1TD U.K.
Tel. +44 117 3312058 Fax. +44 117 3312091
D.A.Matthews@bristol.ac.uk
On 20 Apr 2011, at 17:44, Dannon Baker wrote:
I'll take a look at the workflow in question, if you'd like to share it with me at this email address, 'dannonbaker@me.com'.
-Dannon
On Apr 20, 2011, at 12:42 PM, David Matthews wrote:
Hi,
I've followed this thread with interest. I have had a problem on one of my workflows, it fails to perform a sort on a dataset returning the error "sort: invalid number at field start: invalid count at start of `None,Nonen'". However, this error makes no sense. When I ask it to run the job again with the input it is supposed to sort it works just fine. When the workflow is getting ready to be submitted I've checked and double checked all the links and they are correct too. Is my error related in some way? Does this make sense?
Best Wishes, David.
__________________________________ Dr David A. Matthews
Senior Lecturer in Virology Room E49 Department of Cellular and Molecular Medicine, School of Medical Sciences University Walk, University of Bristol Bristol. BS8 1TD U.K.
Tel. +44 117 3312058 Fax. +44 117 3312091
D.A.Matthews@bristol.ac.uk
On 20 Apr 2011, at 15:47, Dannon Baker wrote:
The issue you're seeing is actually related to improper initialization of the workflow parameters index in the special case where a particular parameter is only used in a rename action and not in a tool step. This is fixed in revision 5400:6cacf178a129.
-Dannon
On Apr 20, 2011, at 10:28 AM, Peter Cock wrote:
Hi all,
I noticed a new problem with our local Galaxy (recently updated), but found it happens on the public installation too.
I can edit workflows, and create run time parameters like ${Name} or ${Name with spaces}, but when I come to run the workflow I get an error:
Server Error An error occurred. See the error logs for more information. (Turn debug on to display exception reports here)
e.g. This trivial example takes a FASTA file, does a minimum length filter, and tries to rename the output to a run time parameter string:
http://main.g2.bx.psu.edu/u/peterjc/w/test-workflow-filter-fasta-min-length-...
Is this a known issue? I couldn't find a match on the bitbucket tracker.
Thanks,
Peter ___________________________________________________________ The Galaxy User list should be used for the discussion of Galaxy analysis and other features on the public server at usegalaxy.org. Please keep all replies on the list by using "reply all" in your mail client. For discussion of local Galaxy instances and the Galaxy source code, please use the Galaxy Development list:
http://lists.bx.psu.edu/listinfo/galaxy-dev
To manage your subscriptions to this and other Galaxy lists, please use the interface at:
___________________________________________________________ The Galaxy User list should be used for the discussion of Galaxy analysis and other features on the public server at usegalaxy.org. Please keep all replies on the list by using "reply all" in your mail client. For discussion of local Galaxy instances and the Galaxy source code, please use the Galaxy Development list:
http://lists.bx.psu.edu/listinfo/galaxy-dev
To manage your subscriptions to this and other Galaxy lists, please use the interface at: