Hi Ido
Over the last few years, we have moved our production server to
different hardware twice. And we also made copies of our production
server in order to have the right development environment.
It always work without much hassle, once we have taken care of the
'obvious', which usually
Hi Neil,
sorry, this is not an answer to your post, I hope you won t mind me stepping in
your thread this way.
Your message kept my attention because of your note: I am surprised by the
error message you report when trying to use an admin API key.
How does galaxy know the user who is making
Peter,
We will definitely give them a try. I never understood why the tabular outputs
did have an option to include the defline/hit decription. Just for that we
needed to use the cloggy XML output and parse that into a table again.
Conserved header names are more useful to us than having column
Il 2014-01-17 06:45 neil.burd...@csiro.au ha scritto:
Hi,
I execute workflows via the API. However, if I want another user to
use my workflows, I can publish my workflows, but the new user then
has to go on to the web browser and import this workflow.
Is there a method/script which I can call
Hi Charles,
not a problem. In my previous post I specified the command line:
/home/galaxy/milxcloud/scripts/api/display.py api_key
http://barium-rbh:9100/extras/api/histories/ebfb8f50c6abde6d/contents/4a56addbcc836c23
The api_key in your question refers to the api_key of an admin
Hi,
since a few days there are frequent error messages popping up in my
Galaxy log files.
galaxy.jobs.runners ERROR 2014-01-17 13:11:17,094 Unhandled exception
checking active jobs
Traceback (most recent call last):
File
/usr/local/galaxy/galaxy-dist/lib/galaxy/jobs/runners/__init__.py,
line
Just to follow up on this - you will want to explicitly check
dataset.external_filename in your database for any hard coded paths that
may have changed.
Also - all tool shed installed tools including migrated tools are creating
tool dependency files (env.sh) in tool_dependency_dir that contain
Hi Niel,
Galaxy does not expose filepaths to non-admin users intentionally. For
executing a workflow with that particular script, the 'file_id' in question
in that example should be an hda, which is what api/history/contents will
display for your users as the 'id' for each history item.
-Dannon
Greg Von Kuster greg@... writes:
On Nov 9, 2012, at 12:56 AM, Derrick Lin wrote:
Also how does this change affect the existing shed tools like BWA that
is using tool_data_table_conf.xml?
The existing shed tools will contiue to function as usual, but entries for
them will be in the
It is hard to test error states... but I assume you have the setup for
it :). Any chance you can apply these patches and let me know if they
fix the problem? I assume they will.
https://bitbucket.org/galaxy/galaxy-central/pull-request/300/potential-drmaa-fixes
-John
On Fri, Jan 17, 2014 at 6:15
Hello,
First..I love the Galaxy Reports tool...thanks so much for this.
I did however come across an error when trying to few the Registered Users
per month link. It would be really nice to have this working :)
Thanks in advance,
Liisa
URL: http://domain:9001/users/registered_users_per_month
Hi Liisa
This rings a bell
I assume you use a MYSQL database? and I guess other pages are broken as
well?
We are also using MySQL and I had to fix several lines in several files
in order to get all report pages to work.
To do the fixes, have a look at this old (but still valid)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well! This is the first I've heard of a Galaxy Reports page. Too bad I
already re-invented the wheel because I hadn't ever heard of this tool...
Anyway, since run_reports.sh was only mentioned once anywhere in the
wiki (according to search, in a
Hello all,
*We are pleased to announce the 1st Galaxy Australasia Workshop 2014 (GAW
2014) https://wiki.galaxyproject.org/Events/GAW2014 will be held in
Melbourne, Australia on 24 and 25th March 2014.*
The Galaxy Australasia
Workshophttps://wiki.galaxyproject.org/Events/GAW2014 is
a great
Thank you Eric for the wiki page.
I agree that Galaxy Reports are not visible enough and this might help.
Martin, Galaxy Team
On Fri, Jan 17, 2014 at 12:29 PM, Eric Rasche rasche.e...@yandex.ru wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well! This is the first I've heard of a
Thanks John,
that fixed it for me!
Have a nice weekend,
Bjoern
It is hard to test error states... but I assume you have the setup for
it :). Any chance you can apply these patches and let me know if they
fix the problem? I assume they will.
16 matches
Mail list logo
