- galaxy-dev - lists.galaxyproject.org

Galaxy tools for docking protein-compounds.
by Léo Biscassi 15 Mar '16

15 Mar '16

Hi folks, I've been developing Galaxy tools for docking protein-compounds. My docking program is Autodock Vina. In [1] is my repository. I'm writing here for two purpose: 1) Is there someone working in this way? I've found the project [2]. 2) I would like to share these tools to Galaxy project. Are they welcome for Galaxy project? Let me know the best practices for developing tools to be shared in Galaxy project. [1] https://github.com/leobiscassi/galaxy_tools [2] https://toolshed.g2.bx.psu.edu/ Thanks for any help. Att. -- *Léo Biscassi* Facebook - https://pt-br.facebook.com/lbiscassi Linkedin - https://br.linkedin.com/in/leobiscassi Skype - biscassi.leo Twitter - https://twitter.com/leobiscassi

4 19

Tool-install error with yaml file
by Rathert, Philipp, Dr. 15 Mar '16

15 Mar '16

Dear all, I want to install a bunch of tools using the install-tools function. In my yaml file tool.yml i have specified the url if my docker instance wit the ip adress i use in the web browser and the api_key is admin When i run install-tools tool.yml I get the error below and nothing happens. I attached my tool.yml file in case the error comes from there. Anybody has an idea whats wrong? root@galaxy:/galaxy-central# install-tools tool.yml * Starting PostgreSQL 9.3 database server [ OK ] starting Galaxy Activating virtualenv at .venv Ignoring indexes: https://pypi.python.org/simple /galaxy-central/.venv/local/lib/python2.7/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:315: SNIMissingWarning: An HTTPS request has been made, but the SNI (Subject Name Indication) extension to TLS is not available on this platform. This may cause the server to present an incorrect TLS certificate, which can cause validation failures. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#snimissingwarning. SNIMissingWarning /galaxy-central/.venv/local/lib/python2.7/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:120: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwar…. InsecurePlatformWarning Requirement already up-to-date: pip==8.0.2+gx2 in ./.venv/lib/python2.7/site-packages Requirement already satisfied (use --upgrade to upgrade): bx-python==0.7.3 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 2)) Requirement already satisfied (use --upgrade to upgrade): MarkupSafe==0.23 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 3)) Requirement already satisfied (use --upgrade to upgrade): PyYAML==3.11 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 4)) Requirement already satisfied (use --upgrade to upgrade): SQLAlchemy==1.0.8 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 5)) Requirement already satisfied (use --upgrade to upgrade): mercurial==3.4.2 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 7)) Requirement already satisfied (use --upgrade to upgrade): numpy==1.9.2 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 8)) Requirement already satisfied (use --upgrade to upgrade): pycrypto==2.6.1 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 9)) Requirement already satisfied (use --upgrade to upgrade): Paste==2.0.2 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 16)) Requirement already satisfied (use --upgrade to upgrade): PasteDeploy==1.5.2 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 17)) Requirement already satisfied (use --upgrade to upgrade): docutils==0.12 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 18)) Requirement already satisfied (use --upgrade to upgrade): wchartype==0.1 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 19)) Requirement already satisfied (use --upgrade to upgrade): repoze.lru==0.6 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 20)) Requirement already satisfied (use --upgrade to upgrade): Routes==2.2 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 21)) Requirement already satisfied (use --upgrade to upgrade): WebOb==1.4.1 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 22)) Requirement already satisfied (use --upgrade to upgrade): WebHelpers==1.3 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 23)) Requirement already satisfied (use --upgrade to upgrade): Mako==1.0.2 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 24)) Requirement already satisfied (use --upgrade to upgrade): pytz==2015.4 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 25)) Requirement already satisfied (use --upgrade to upgrade): Babel==2.0 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 26)) Requirement already satisfied (use --upgrade to upgrade): Beaker==1.7.0 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 27)) Requirement already satisfied (use --upgrade to upgrade): Cheetah==2.4.4 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 30)) Requirement already satisfied (use --upgrade to upgrade): Markdown==2.6.3 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 31)) Requirement already satisfied (use --upgrade to upgrade): bioblend==0.6.1 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 34)) Requirement already satisfied (use --upgrade to upgrade): boto==2.38.0 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 35)) Requirement already satisfied (use --upgrade to upgrade): requests==2.8.1 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 36)) Requirement already satisfied (use --upgrade to upgrade): requests-toolbelt==0.4.0 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 37)) Requirement already satisfied (use --upgrade to upgrade): kombu==3.0.30 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 40)) Requirement already satisfied (use --upgrade to upgrade): amqp==1.4.8 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 41)) Requirement already satisfied (use --upgrade to upgrade): anyjson==0.3.3 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 42)) Requirement already satisfied (use --upgrade to upgrade): sqlalchemy-migrate==0.10.0 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 45)) Requirement already satisfied (use --upgrade to upgrade): decorator==4.0.2 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 46)) Requirement already satisfied (use --upgrade to upgrade): Tempita==0.5.3dev in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 47)) Requirement already satisfied (use --upgrade to upgrade): sqlparse==0.1.16 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 48)) Requirement already satisfied (use --upgrade to upgrade): pbr==1.8.0 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 49)) Requirement already satisfied (use --upgrade to upgrade): six==1.9.0 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 51)) Requirement already satisfied (use --upgrade to upgrade): Parsley==1.3 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 52)) Requirement already satisfied (use --upgrade to upgrade): nose==1.3.7 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 53)) Requirement already satisfied (use --upgrade to upgrade): SVGFig==1.1.6 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 54)) Requirement already satisfied (use --upgrade to upgrade): Fabric==1.10.2 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 57)) Requirement already satisfied (use --upgrade to upgrade): paramiko==1.15.2 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 58)) Requirement already satisfied (use --upgrade to upgrade): ecdsa==0.13 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 59)) Requirement already satisfied (use --upgrade to upgrade): Whoosh==2.4.1+gx1 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 66)) Requirement already satisfied (use --upgrade to upgrade): pysam==0.8.4+gx1 in ./.venv/lib/python2.7/site-packages (from -r requirements.txt (line 69)) You are using pip version 8.0.2+gx2, however version 8.1.0 is available. You should consider upgrading via the 'pip install --upgrade pip' command. Requirement already satisfied (use --upgrade to upgrade): psycopg2==2.6.1 in ./.venv/lib/python2.7/site-packages (from -r /dev/stdin (line 1)) Requirement already satisfied (use --upgrade to upgrade): drmaa in ./.venv/lib/python2.7/site-packages (from -r /dev/stdin (line 2)) You are using pip version 8.0.2+gx2, however version 8.1.0 is available. You should consider upgrading via the 'pip install --upgrade pip' command. Activating virtualenv at .venv Daemon is already running (PID: 323 from PID file galaxy_install.pid) Galaxy is running. PLAY ************************* TASK [galaxy_tools : include] **************** skipping: [localhost] TASK [galaxy_tools : include] **************** included: /home/galaxy/ansible/galaxy-tools-playbook/roles/galaxy_tools/tasks/tools.yml for localhost TASK [galaxy_tools : Create/invoke script virtualenv] ******** fatal: [localhost]: UNREACHABLE! => {"changed": false, "msg": "All items completed", "results": [{"item": "pyyaml", "msg": "Authentication or permission failure. In some cases, you may have been able to authenticate and did not have permissions on the remote directory. Consider changing the remote temp path in ansible.cfg to a path rooted in \"/tmp\". Failed command was: ( umask 22 && mkdir -p \"echo $HOME/.ansible/tmp/ansible-tmp-1457708936.13-72771790334072\" && echo \"echo $HOME/.ansible/tmp/ansible-tmp-1457708936.13-72771790334072\" ), exited with result 1", "unreachable": true}, {"item": "bioblend", "msg": "Authentication or permission failure. In some cases, you may have been able to authenticate and did not have permissions on the remote directory. Consider changing the remote temp path in ansible.cfg to a path rooted in \"/tmp\". Failed command was: ( umask 22 && mkdir -p \"echo $HOME/.ansible/tmp/ansible-tmp-1457708936.15-89736978480357\" && echo \"echo $HOME/.ansible/tmp/ansible-tmp-1457708936.15-89736978480357\" ), exited with result 1", "unreachable": true}]} to retry, use: --limit @tools.retry PLAY RECAP *********************** localhost : ok=1 changed=0 unreachable=1 failed=0

1 0

external_chown_script.py and the local job runner
by Peter Cock 15 Mar '16

15 Mar '16

On Mon, Jan 25, 2016 at 11:33 AM, Peter Cock <p.j.a.cock(a)googlemail.com> wrote: > Hello all, > > We're currently looking at changing our Galaxy setup to link user accounts > with Linux user accounts for better cluster integration (running jobs as the > actual user on SGE). As part of this, we've tried setting up a fresh > installation on a new VM which has thrown up some issues. > > [snip] We eventually got Galaxy to talk to SGE and submit jobs successfully as the individual user's Linux account, with external_chown_script.py being called to handle ownership of the files. However, we would like to have some jobs (like the upload tool) configured to run on the Galaxy server itself - and the easiest way to do that is via the local job runner. We tried both the "upload1" and "Convert characters1" tools. These jobs would start and seem to run, but then fail with a file permission error (I don't have a stack trace to hand). From watching the Galaxy terminal output from run.sh we could see external_chown_script.py being called. As a test, when we disabled the external_chown_script setting in config/galaxy.ini then the local jobs would work. When using the local job runner, does Galaxy run the child process as the Galaxy user (my guess - no chown needed), or as the job owner's Linux account (calling chown would be needed)? Thanks, Peter

2 5

Mapping users to slurm
by Pardo Diaz, Alfonso 14 Mar '16

14 Mar '16

Hello, I have connected my galaxy to a Slurm cluster via DRMAA. Galaxy can send jobs to the cluster without problems. But then I configure galaxy to use “real users” I got this error: "User myuser(a)mydomain.es<mailto:myuser@mydomain.es> is not mapped to any real user, and not permitted to start jobs” Could you help me? Tanks!! This is my job_con.xml: <?xml version="1.0"?> <job_conf> <plugins workers="6"> <plugin id="drmaa" type="runner" load="galaxy.jobs.runners.drmaa:DRMAAJobRunner" workers="2"> <param id="drmaa_library_path">/opt/slurm-drmaa/lib/libdrmaa.so</param> </plugin> </plugins> <handlers default="handlers"> <handler id="main" tags="handlers"/> </handlers> <destinations default="drmaa"> <destination id="drmaa" runner="drmaa"> <param id="galaxy_external_runjob_script">/opt/galaxy/scripts/drmaa_external_runner.py</param> <param id="galaxy_external_killjob_script">/opt/galaxy/scripts/drmaa_external_killer.py</param> <param id="galaxy_external_chown_script">/opt/galaxy/scripts/external_chown_script.py</param> </destination> </destinations> </job_conf> this is my auth_conf.xml: <?xml version="1.0"?> <auth> <authenticator> <type>ldap</type> <options> <auto-register>True</auto-register> <allow-password-change>False</allow-password-change> <server>ldap://ldap.ceta-ciemat.es</server> <login-use-username>True</login-use-username> <continue-on-failure>False</continue-on-failure> <search-filter>(|(mail={email})(uid={username}))</search-filter> <search-fields>uid,mail,dn</search-fields> <search-base>ou=xxxxxx,dc=xxxxx,dc=xxxxx</search-base> <bind-user>{dn}</bind-user> <bind-password>{password}</bind-password> <auto-register-username>{uid}</auto-register-username> <auto-register-email>{mail}</auto-register-email> <login-use-username>True</login-use-username> </options> </authenticator> <authenticator> <type>localdb</type> <options>  <allow-password-change>true</allow-password-change> </options> </authenticator> </auth> And this is my galaxy.ini: [server:main] port = 8080 host = 0.0.0.0 use_threadpool = True threadpool_kill_thread_limit = 10800 [filter:gzip] [filter:proxy-prefix] prefix = /galaxy [app:main] paste.app_factory = galaxy.web.buildapp:app_factory database_connection = postgres://xxxxxxxx:xxxxxx@xxxxx/galaxy_project database_engine_option_server_side_cursors = True database_engine_option_strategy = threadlocal new_file_path = database/tmp tool_config_file = config/tool_conf.xml,config/shed_tool_conf.xml tool_dependency_dir = dependency_dir cluster_files_directory = database/pbs smtp_server = localhost use_nglims = False nglims_config_file = tool-data/nglims.yaml debug = true use_interactive = True require_login = True allow_user_creation = False allow_user_deletion = True allow_user_impersonation = True allow_user_dataset_purge = True new_user_dataset_access_role_default_private = True auth_config_file = config/auth_conf.xml enable_quotas = True expose_dataset_path = False job_config_file = config/job_conf.xml enable_job_recovery = True outputs_to_working_directory = True drmaa_external_runjob_script = scripts/drmaa_external_runner.py drmaa_external_killjob_script = scripts/drmaa_external_killer.py external_chown_script = scripts/external_chown_script.py ---------------------------- Confidencialidad: Este mensaje y sus ficheros adjuntos se dirige exclusivamente a su destinatario y puede contener informaci�n privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilizaci�n, divulgaci�n y/o copia sin autorizaci�n est� prohibida en virtud de la legislaci�n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente respondiendo al mensaje y proceda a su destrucci�n. Disclaimer: This message and its attached files is intended exclusively for its recipients and may contain confidential information. If you received this e-mail in error you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited and may be unlawful. In this case, please notify us by a reply and delete this email and its contents immediately. ----------------------------

1 0

Mapping users to slurm
by Pardo Diaz, Alfonso 14 Mar '16

14 Mar '16

Hello, I have connected my galaxy to a Slurm cluster via DRMAA. Galaxy can send jobs to the cluster without problems. But then I configure galaxy to use “real users” I got this error: "User myuser(a)mydomain.es is not mapped to any real user, and not permitted to start jobs” Could you help me? Tanks!! This is my job_con.xml: <?xml version="1.0"?> <job_conf> <plugins workers="6"> <plugin id="drmaa" type="runner" load="galaxy.jobs.runners.drmaa:DRMAAJobRunner" workers="2"> <param id="drmaa_library_path">/opt/slurm-drmaa/lib/libdrmaa.so</param> </plugin> </plugins> <handlers default="handlers"> <handler id="main" tags="handlers"/> </handlers> <destinations default="drmaa"> <destination id="drmaa" runner="drmaa"> <param id="galaxy_external_runjob_script">/opt/galaxy/scripts/drmaa_external_runner.py</param> <param id="galaxy_external_killjob_script">/opt/galaxy/scripts/drmaa_external_killer.py</param> <param id="galaxy_external_chown_script">/opt/galaxy/scripts/external_chown_script.py</param> </destination> </destinations> </job_conf> this is my auth_conf.xml: <?xml version="1.0"?> <auth> <authenticator> <type>ldap</type> <options> <auto-register>True</auto-register> <allow-password-change>False</allow-password-change> <server>ldap://ldap.ceta-ciemat.es</server> <login-use-username>True</login-use-username> <continue-on-failure>False</continue-on-failure> <search-filter>(|(mail={email})(uid={username}))</search-filter> <search-fields>uid,mail,dn</search-fields> <search-base>ou=xxxxxx,dc=xxxxx,dc=xxxxx</search-base> <bind-user>{dn}</bind-user> <bind-password>{password}</bind-password> <auto-register-username>{uid}</auto-register-username> <auto-register-email>{mail}</auto-register-email> <login-use-username>True</login-use-username> </options> </authenticator> <authenticator> <type>localdb</type> <options>  <allow-password-change>true</allow-password-change> </options> </authenticator> </auth> And this is my galaxy.ini: [server:main] port = 8080 host = 0.0.0.0 use_threadpool = True threadpool_kill_thread_limit = 10800 [filter:gzip] [filter:proxy-prefix] prefix = /galaxy [app:main] paste.app_factory = galaxy.web.buildapp:app_factory database_connection = postgres://xxxxxxxx:xxxxxx@xxxxx/galaxy_project database_engine_option_server_side_cursors = True database_engine_option_strategy = threadlocal new_file_path = database/tmp tool_config_file = config/tool_conf.xml,config/shed_tool_conf.xml tool_dependency_dir = dependency_dir cluster_files_directory = database/pbs smtp_server = localhost use_nglims = False nglims_config_file = tool-data/nglims.yaml debug = true use_interactive = True require_login = True allow_user_creation = False allow_user_deletion = True allow_user_impersonation = True allow_user_dataset_purge = True new_user_dataset_access_role_default_private = True auth_config_file = config/auth_conf.xml enable_quotas = True expose_dataset_path = False job_config_file = config/job_conf.xml enable_job_recovery = True outputs_to_working_directory = True drmaa_external_runjob_script = scripts/drmaa_external_runner.py drmaa_external_killjob_script = scripts/drmaa_external_killer.py external_chown_script = scripts/external_chown_script.py ---------------------------- Confidencialidad: Este mensaje y sus ficheros adjuntos se dirige exclusivamente a su destinatario y puede contener informaci�n privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilizaci�n, divulgaci�n y/o copia sin autorizaci�n est� prohibida en virtud de la legislaci�n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente respondiendo al mensaje y proceda a su destrucci�n. Disclaimer: This message and its attached files is intended exclusively for its recipients and may contain confidential information. If you received this e-mail in error you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited and may be unlawful. In this case, please notify us by a reply and delete this email and its contents immediately. ----------------------------

1 0

Scaling tools: data available?
by Peter van Heusden 14 Mar '16

14 Mar '16

Hi there We're researching the resource (CPU time and memory) requirements for RNA STAR at the moment. Specifically, we'd like to build up a database of input size to resource usage so that we can use this to feed a dynamic destination mapper (currently our STAR configuration uses a thumbsuck for RAM and CPU requirements that is not optimal but works in many cases). Has anyone collected these metrics before? And more generally, is anyone collecting metrics for a range of bioinformatics tools? A database like this could be very useful! Thanks! Peter

2 3

RV: Error attempting to display contents of library (New data library)
by Juan Vladimir de la Rosa Medina 11 Mar '16

11 Mar '16

Hi Dannon, Thank you for your help, surprisingly now I can upload datasets to the data library without any change. I wanted to take a snapshot of the screen in a previous step to adding the datasets to the data library, before to make the changes in the files you explained in the link, when I realize that all works fine. I can't understand what happened. Anyway here I attached the screen snapshot prior to the datasets were added to the Data library, and other snapshot showing that inexplicably everything is working fine now. [cid:image002.png@01D17BD3.6BCDA450] [cid:image006.png@01D17BD3.6BCDA450] Juan Vladimir Enviado desde Correo<https://go.microsoft.com/fwlink/?LinkId=550986> para Windows 10 De: Dannon Baker<mailto:dannon.baker@gmail.com> Enviado: viernes, 11 de marzo de 2016 1:23 Para: Juan Vladimir de la Rosa Medina<mailto:jvdelarosa@hotmail.com> CC: galaxy-dev(a)lists.galaxyproject.org<mailto:galaxy-dev@lists.galaxyproject.org> Asunto: Re: [galaxy-dev] Error attempting to display contents of library (New data library) Hi Juan, I'm working on a few errors I've uncovered trying to track down your issue here, but my hunch is you're hitting a different one. The branch is here if you want to try it: https://github.com/dannon/galaxy/commits/library_errors Do you have any non-ascii characters in a particular field that you've noticed? Perhaps in a dataset name, or filepath? Barring that, can you send me a screenshot of exactly what you're seeing prior to running into the error? -Dannon On Sat, Mar 5, 2016 at 1:43 PM, Juan Vladimir de la Rosa Medina < jvdelarosa(a)hotmail.com> wrote: > Hello to everybody, > > > > I’m trying to Access to my data files into a local instance of galaxy, > installed in a virtual machine with Debian Jessie 8.2.0 (with Python 2.7.9 > installed), using the data libraries as administrator (I’m handling big > data files). To do this task I have changed the option library_import_path > into the config/galaxy.ini file to the path > (“/home/jvdelarosa/Bioinformatica/BioDatos/”) where my files are located, > as is explained in the Galaxy wiki section (“Uploading Files to a Data > Library”). > > > > As administrator I can create a new data library, but when I’m trying to > add datasets following the instructions explained in the section mentioned > above, an error message is showed on the web browser. > > > > *“Error attempting to display contents of library (New data library): > 'ascii' codec can't decode byte 0xc3 in position 1: ordinal not in > range(128).”* > > > > I have to mention that I haven’t had any problem with other local galaxy > instances I have installed in the past with the same O.S. > > > > I have been searching on the web about the same problem in galaxy with no > success. > > > > Can anyone explain what’s happening with my local instance of galaxy and > if there is any solution? > > > > A lot of thanks in advance. > > > > ___________________________________________________________ > 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: > https://lists.galaxyproject.org/ > > To search Galaxy mailing lists use the unified search at: > http://galaxyproject.org/search/mailinglists/ >

1 0

Missing dependency issue
by Scott Szakonyi 11 Mar '16

11 Mar '16

Hello all, I'm having an issue with a missing dependency for readline 6.2. When I try to install or repair, I get the following error message: configure: error: in `/vectorbase/web/Galaxy/galaxy/data/galaxy/tmp/tmp-toolshed-mtd3fhemK/readline-6.2': configure: error: cannot compute suffix of object files: cannot compile See `config.log' for more details. I've tried to locate the config.log file without success, so this is all I have to go on. Has anyone else encountered this sort of issue, and if so, how did you solve it? Thanks! -- Scott B. Szakonyi Research Programmer *Center for Research Computing* 107 Information Technology Center Notre Dame, IN 46556 http://crc.nd.edu

3 4

backslash in string for galaxy tool
by Jasper Koehorst 11 Mar '16

11 Mar '16

I am creating a tool which allows you to query RDF files. However when performing a \n in the query it is replaced by Xn. Other special characters such as > are replaced by an __gt__ . How can I either allow galaxy to accept \n entries or that the backslash is replaced by something like __bs__ ? As Xn is not replaceable.

2 2

Error attempting to display contents of library (New data library)
by Juan Vladimir de la Rosa Medina 11 Mar '16

11 Mar '16

Hello to everybody, I’m trying to Access to my data files into a local instance of galaxy, installed in a virtual machine with Debian Jessie 8.2.0 (with Python 2.7.9 installed), using the data libraries as administrator (I’m handling big data files). To do this task I have changed the option library_import_path into the config/galaxy.ini file to the path (“/home/jvdelarosa/Bioinformatica/BioDatos/”) where my files are located, as is explained in the Galaxy wiki section (“Uploading Files to a Data Library”). As administrator I can create a new data library, but when I’m trying to add datasets following the instructions explained in the section mentioned above, an error message is showed on the web browser. “Error attempting to display contents of library (New data library): 'ascii' codec can't decode byte 0xc3 in position 1: ordinal not in range(128).” I have to mention that I haven’t had any problem with other local galaxy instances I have installed in the past with the same O.S. I have been searching on the web about the same problem in galaxy with no success. Can anyone explain what’s happening with my local instance of galaxy and if there is any solution? A lot of thanks in advance.

2 1