Hi,
There have been a few comments about how general we could make the system for
Galaxy use or just as a stand-alone command line driven tool. So some notes
below about what I could see it taking on. Given the scale of the sequencing
data problem, I'm sure the Galaxy community has important
About the datatype. So you are thinking of a new datatype that applies to
files that hold the versioned database contents (in this case a structured
key-value fasta identifier/sequence pairs, right?) Then the fasta archive
versioning tool would take only files of that datatype for input. That
Hi Graeme,
It looks like your integrated_tool_panel.xml file has been corrupted. You can
move/remove this file and it will be recreated the next time Galaxy is started
up.
Thanks for using Galaxy,
Dan
On Sep 3, 2014, at 3:54 AM, Graeme Grimes wrote:
> I have tried to restart Galaxy after
Collection are one potential answer for how users can specify the set
of stuff that belongs in the directory. For explicitly dealing with
applications that consume directories - I think it is best to just
create the directory and link in files (if possible) before the tool
runs.
mkdir input_dir;
#
I have tried to restart Galaxy after restoring my database from a backup.
Here is the error message I get in the log file. Any idea what is wrong
and how to fix this problem?
--
galaxy.jobs DEBUG 2014-09-03 08:33:46,367 Loading job configuration from
/export/users/
Hi Melissa,
Just commenting on point 1 of your email: did you try the “Reset metadata “
option? See screenshot below:
[cid:image001.jpg@01CFC756.F193E4B0]
For points 2 and 3: I normally look at the status (Installed/Green) and test
whether the correct version appear in the menu for the users.
