the estimation entirely.
-Dannon
On Jul 31, 2011, at 11:11 AM, Chaolin Zhang wrote:
Hi,
I noticed that the current version of galaxy shows approximate number of
lines for history items, when it is relatively big. I guess this is due to
a consideration of performance, but it is quite
don't vary dramatically throughout the file. It
would slow down the metadata setting, but for a personal galaxy instance you
could certainly increase that number, or disable the estimation entirely.
-Dannon
On Jul 31, 2011, at 11:11 AM, Chaolin Zhang wrote:
Hi,
I noticed
Hi Shantanu,
Thanks for the information! This did the trick.
Chaolin
On Jul 30, 2011, at 1:28 AM, Shantanu Pavgi wrote:
On Jul 29, 2011, at 11:28 PM, Chaolin Zhang wrote:
Hi,
I am setting up SGE in our galaxy mirror. One problem I have is that I
cannot export environment variables
Hi,
I am setting up SGE in our galaxy mirror. One problem I have is that I cannot
export environment variables of the specific users running the galaxy service.
On command line, I did this by qsub -V script.sh. or add a line
#$ -V
in script.sh
I tried to change
Hi,
Is there a way to organize related histories together into a project or
folder?
I realize in a lot of cases, a pipeline is designed for processing of a single
sample, while a study typically consists of multiple samples that go through
the same processing. They are then put together for
Hi,
We have a local mirror of the galaxy system and the disk is occupied really
quickly. Is there a way to purge histories/datasets not accessed/updated for
a certain period of time, no matter if they are deleted by the user? It looks
like the current scripts for clean up only purges
