Hi Carrie,
I've had the same problem. I wanted to get Galaxy to submit to a cluster which
was running Torque 4.x. Torque clients need to be 4.x to work with the that
version of the server. I spent a bit of time looking into this and determined
that pbs_python used by Galaxy is not
On Thu, Apr 4, 2013 at 7:19 PM, Daniel Blankenberg d...@bx.psu.edu wrote:
Hi Peter,
What is the test error given when you do have a value defined for name in
output?
Can you try using 'empty_file.dat'?
e.g.
output name=out_file file=empty_file.dat
or
output
Hello Galaxy Buddies,
I am having a problem with run.sh core dumping. It happens when I try to view
data (click on the eye) for a large text file of results. It doesn't happen
when viewing data of a smaller size and it executes jobs fine.
Here is the server's output.
Starting server in PID
Hello,
Based on my observations and interactions during the past few meet-ups and as
an administrator of Galaxy, the current goals of the group [1] remain relevant
and are being met through the meet-ups. An additional benefit to these
meet-ups that has evolved is an update from a member of
Hi Steve,
Apologies, I didn't check the Galaxy list before sending you an email.
I came to mostly the same conclusion. I installed the Torque 4.x client on the
submit node and I can submit jobs that way through the command line without
issue.
I can't get pbs_submit to work from pbs_python,
Hello,
I have a question about running two Galaxy instances on separate hosts on
the same Torque cluster. For various reasons, including some recent changes
and/or removal of certain features (I am told BLAST was affected) in the
newer versions of Galaxy, I would like to keep our current older
