Hi Ross,
I agree, normally I use the label="" xml tag when possible, but the reason I
ask this question is because I have a tool where the number of output
datasets cannot be determined until the tool is run (a la
https://bitbucket.org/galaxy/galaxy-central/wiki/ToolsMultipleOutput) and I
really would like to change the dataset labels/names of what is produced.
Could you provide some insight as to how you get it to work with one of the
hooks? You might have seen in another post I made yesterday, when I try even
just a simple example using exec_before_job() I get some strange error :-/
thanks again,
leandro
On Fri, Jun 24, 2011 at 10:09 AM, Ross <ross.laza...@gmail.com> wrote:
> I used to use the post job hook but I think it's a lot cleaner to use
> the label option - eg where I want the output name based on a user
> supplied text string "out_prefix", something like:
>
> <outputs>
> <data format="html" name="html_file" label="${out_prefix}.html"/>
> </outputs>
>
> works for me and avoids the need to have a post execution hook code file.
>
> On Fri, Jun 24, 2011 at 6:02 PM, Leandro Hermida
> <soft...@leandrohermida.com> wrote:
> > Hi again,
> >
> > Sorry that I didn't know before, it seems like the label is the the
> object
> > attribute 'name' programmatically, but even if I set this in
> > exec_before_job(), exec_before_process(), exec_after_process() it doesn't
> > change the dataset name even after refreshing my history.
> >
> > Has anyone had success setting dataset label/name and other attributes
> using
> > one of the custom code hook functions??
> >
>
>
> --
> Ross Lazarus MBBS MPH;
> Associate Professor, Harvard Medical School;
> Director of Bioinformatics, Channing Lab; Tel: +1 617 505 4850;
> Head, Medical Bioinformatics, BakerIDI; Tel: +61 385321444;
>
___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
http://lists.bx.psu.edu/
