On Jul 27, 2011, at 10:26 AM, Jelle Scholtalbers wrote:
Wouldn't it be better to at least validate e-mail addresses of new
users on the main instance? This would probably resolve most issues
related to unwanted content on the server?
Not in our experience, valid email addresses are trivial
n your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
http://lists.bx.psu.edu/
--
__
Paul Gordon
Bioinformatics Support Specialist
Alberta Children's Hospital Research I
seen adoption beyond
PacBio, but I have seen some things popping up in Galaxy.
FWIW, the XSQ format files created by the 5500 Series ABI SOLiD are
HDF5, but not BioHDF:
http://solidsoftwaretools.com/gf/download/docmanfileversion/309/1079/XSQ_Webinar_20110215.pdf
--
__
Paul G
Excellent idea, and the BibTeX comment makes sense too...
Dear all,
It has become a convention that each tool/wrapper in
Galaxy includes citation instructions in their help text
(although not all the tools do this - I think they should).
It occurred to me this could be formalised, with explicit
+1 votes :-)
> This would also give graph generating tools a fighting chance to present
> something useful in any graphs generated.
> E.g. GC Bias Plot of Solid 24A could have a title of Solid 24A instead of
> dataset_234.dat
>
> What do you think of this first-last model?
_
Hi all,
Is there a way, or better yet a coded example, of how to list the options
for an input parameter using the contents of a shared data library? Up
until now I've use Python scripts to get the input file options from a
directory listing for a hardcoded path on the server, but it'd be much n
Hi all,
I have noticed that when I run a workflow with output to a new history, the
data sets used as input to the workflow do not become part of the new
history. Unfortunately, if a job fails in the workflow, the "rerun"
interface for the job can't access the original dataŠit needs to be manuall
+1. This is especially useful for us, with hardware-accelerated
algorithms having limits on input size.
On 12-05-03 9:51 AM, "Peter Cock" wrote:
>Hello all,
>
>Currently the Galaxy experimental task splitting code allows splitting
>into
>N chunks, e.g. 8 parts, with:
>
>..." />
>
>Or, into c
IANAAG, but the following should be secure and effective as well (at least
it works for me), setting REMOTE_USER with an Apache authentication module
in conjunction with ProxyPass
RequestHeader set REMOTE_USER %{REMOTE_USER}s
RequestHeader edit REMOTE_USER ^.*(.+?) $1
Cheers,
Paul
On 12-0
Somewhat related, can I make a feature request that in the job attribute
editor screen (i.e. what you get when you click the pencil icon in the top
right corner of a history item), you can manually change the state of a
job from failed (which means you can't use the output in any subsequent
analyse
10 matches
Mail list logo
