Hi,
I'm experiencing the same problem after I configured the web
application scaling- although I have to say I still have the june 03
version from central. Has this been resolved in newer updates?
Cheers,
Jelle
On Mon, Jul 30, 2012 at 7:03 PM, Fields, Christopher J
cjfie...@illinois.edu wrote:
Hi Patrick,
the issue you are having is partly related to the idea of Galaxy to
ensure reproducible science and saving each intermediate step and
output files. For example in your current workflow in Galaxy you can
easily do something else with each intermediate file - feed it to a
different tool
Hi Chaolin,
Although I haven't tested this, the following changes should probably work.
In the datatypes_conf.xml change on this line:
datatype extension=data type=galaxy.datatypes.data:Data
mimetype=application/octet-stream
max_optional_metadata_filesize=1048576 /
the
Hi Kostas,
I recently talked with Bodo Vossen from MPI who has created this
functionality and made available:
https://bitbucket.org/Bodolski/galaxy-central-adding-tools
He added this functionality to the Admin page of Galaxy which allows to add
tools without restarting the server. Unfortunately
Hi Greg,
I do see the concern of uploading data through the api but I don't think
filtering on file types is the right solution. It seems to be an issue with
allowing everyone to register. Wouldn't it be better to at least validate
e-mail addresses of new users on the main instance? This would
', 'scf' ]
On Jul 22, 2011, at 11:52 AM, Jelle Scholtalbers wrote:
Hi Greg,
I used that link when trying to create the support. The jpg datatype was
already present in the datatypes_conf.xml (
datatype extension=jpg type=galaxy.datatypes.images:Image
mimetype=image/jpeg/ )
, so I first
Hi all,
I would like to be able to upload images to my Galaxy instance - in
particular jpg/png to data libraries. I can't however find out how to
overcome the problem of inappropriate content in binary file.
How to go about?
When I create a sniffer class in the galaxy.datatypes.images.py that
