Hi.
What to tell Galaxy to have user login web page with login frame and
welcome frame? I try to modify login.js in galaxy/client/galaxy/scripts to
comment part of code as suggested there:
// TODO: remove iframe for user login (at least) and render login page
from here
// then remove this
Hi Ryan,
On Sat, Jul 9, 2016 at 12:40 AM, Ryan G wrote:
> Hi Martin - I was actually thinking to let the tool itself tell Galaxy about
> the progress instead of Galaxy estimating that.
>
> If instance, if the tool know it has 5 stages, it can report back to Galaxy
> 20,40,60,80,and 100 % complet
Dear experts,
I've a strange behaviour with uWSGI and supervisor.
This is my settings in galaxy.ini file:
[uwsgi]
processes = 3
socket = 127.0.0.1:4001
stats = 127.0.0.1:9191
#socket = /var/log/galaxy/uwgi.sock
pythonpath = /home/galaxy/galaxy/lib
pythonhome = /home/galaxy/galaxy/.venv
threads = 4
Hi Ryan,
multiple tool stages do not necessarily equally split runtime so you
wouldn't have 'time progress bar' but 'unscaled progress bar'. The
usefulness of such I would put somewhere in between a loading animation and
stats estimate. This would also require every tool to be enhanced as well
as
Hi Martin - I was actually thinking to let the tool itself tell Galaxy about
the progress instead of Galaxy estimating that.
If instance, if the tool know it has 5 stages, it can report back to Galaxy
20,40,60,80,and 100 % complete.
I know this is complex but could be a nice feature.
Please
Hi Ryan,
This is a fairly complex problem because the length of the run depends most
often on input size, job algorithms, and computational capacity all of
which are quite difficult to estimate.
We have discussed it before and one of the ways to approach this is to
gather statistics from as many j
Hi all - I know this isn't currently a feature, but wanted to find out
about what it would take to implement
We developed some custom tools that are long runningmultiple hours.
The tools run through various steps of an analysis.
Is there a way to display progress of a task in the history?
Hi Katherine,
Probably about the only way to get the job start time is job.create_time (a
close estimate to the actual start time) and the end time is job.update_time
(again, a close estimate), so you can calculate the job’s estimated execution
time using something like this:
import datetime
e
Actually just figured out the history content api id, just needing the
extra stuff about the job like runtime and start and end times.
On Fri, Jul 8, 2016 at 8:55 AM, Katherine Beaulieu <
katherine.beaulieu...@gmail.com> wrote:
> Hi Greg,
> Thanks for the link to your github repo, some of the inf
Hi Greg,
Thanks for the link to your github repo, some of the information there was
very useful. Do you have any idea on how to access some of the stuff you
don't yourself pass to your python script such as the history content api
id, or the job runtime? For example for the job runtime I feel like
Hi Marco,
The tag has been deprecated,
what you should use is just
Note the $*tool_directory*, this is required for finding the path to the
script.
(And that has been “magically” done for you by the tag).
Hope that works for you,
Marius
On 8 July 2016 at 11:43, Marco Tangaro wrote:
Dear Marius and all,
thanks a lot for your answer, it is indeed very interesting.
I'm following this one
https://github.com/galaxyproject/galaxy/blob/dev/test/functional/tools/collection_two_paired.xml
to create an output list, starting from an input list.
The command section of my script_wrapp
12 matches
Mail list logo
