Hi, I guess a box in the run dialog asking for a run name - made prominant so you see it, but not so prominant so you don't feel obliged to fill it in, in case you are only running something quick.
Or, the ability to click on a button and name a workflow run in the results pane (near the reload workflow button). A right click on the workflow run or the run diagram would also be good :) Paul. On 18/02/2011 13:02, Alan R Williams wrote: > On 18/02/2011 12:42, Paul Fisher wrote: >> Hi, > Hello, > >> Could I also ask for a feature request - I would like to assign names to >> workflow runs. >> At the moment, I have to dig into the results and inputs to see what run >> corresponds to a particular type of data. It becomes even worse when you >> have multiple runs of the same workflow, but with slight parameter tweaks. >> >> I think it would be easier to see what run is from what data if I could >> call each one a name, e.g. Chromosome 2 run; Chromosome 3 run; Ondex >> Concept Mapping....etc > This is more complicated than it sounds. When would you want to specify > the run name? The run dialog currently only pops up if the workflow has > inputs. > > Can you write up what you would expect the user to do? > >> cheers, >> Paul. > Alan > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > taverna-users mailing list > [email protected] > [email protected] > Web site: http://www.taverna.org.uk > Mailing lists: http://www.taverna.org.uk/about/contact-us/ ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ taverna-users mailing list [email protected] [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/about/contact-us/
