Hi,
I recently needed to generate the dataset's hashed-id from a reporting script
outside galaxy (a script that reads Galaxy database directly).
Here's how to generate the hashed-id from perl and postgres, hope it would save
you some time if you ever need it.
(The python code to do the same is
Joe,
Sorry for the confusing back-and-forth on this. Galaxy is not currently able
to fill in the form field values for sample forms using the contents of a csv
file. However, this additional feature shouldn't be too difficult to add, so
I'll look into it as soon as possible.
Greg
On Jun 10,
Hey Greg,
Sorry for not being clear. I'm trying to create a sample information form
where users can import csv files which would contain DIFFERENT values for
each field. So, while one sample may have value 'agctac' for the last
field, another sample will have a different value, say '123. So, t
Committed on trunk.
On Thu, Jun 2, 2011 at 2:25 AM, Florent Angly wrote:
> Hi Kanwei,
> I think we'll get more feedback once it when it is added to Galaxy. I have
> run small tests (included in the functional tests) and real large datasets
> and have had no issues with the scripts and wrappers.
Thanks for reporting this. I've attempted to reproduce the workflow related
error you're seeing, but have been unable to do so. Do you know what revision
your galaxy instance is running?
You should not have to avoid special characters in dataset names. If you do
run into this issue again, pl
Hi again,
Commenting out the following if-then-else as Nate recommended works in
remoteuser.py works to achieve this goal:
#if not environ[ 'HTTP_REMOTE_USER' ].count( '@' ):
#if self.maildomain is not None:
#environ[ 'HTTP_REMOTE_USER' ] += '@' + s
