Hmm, actually the version is the version of the tool wrapper. Unless the wrapper version reflects the actual tool version, we're not keeping track of the tool version as we're simply running the command. Perhaps history annotation is the solution here.
-Kanwei On Thu, Jan 27, 2011 at 6:17 PM, Kanwei Li <kan...@gmail.com> wrote: > Hi Yury, > > Yes, the "jobs" table keeps track of the tool version run. I am > implementing a new "view details" feature (already on trunk) and I > will add the tool version to the information displayed. > > Thanks, > > Kanwei > > On Thu, Jan 27, 2011 at 5:57 PM, Yury Bukhman <ybukh...@glbrc.wisc.edu> wrote: >> Hi, >> >> in order to reproduce an analysis, it's good to know not only what tools >> were used, but also their versions. Is there a way to figure that out from >> a Galaxy history? I would like to be able to answer questions like "what >> version of bowtie have I run in an analysis performed 6 months ago?" >> >> Thanks. >> >> Yury >> >> >> -- >> Yury V. Bukhman, Ph.D. >> Associate Scientist, Bioinformatics >> Great Lakes Bioenergy Research Center >> University of Wisconsin - Madison >> 445 Henry Mall, Rm. 513 >> Madison, WI 53706, USA >> Phone: 608-890-2680 Fax: 608-890-2427 >> Email: ybukh...@glbrc.wisc.edu >> >> _______________________________________________ >> galaxy-user mailing list >> galaxy-user@lists.bx.psu.edu >> http://lists.bx.psu.edu/listinfo/galaxy-user >> > _______________________________________________ galaxy-user mailing list galaxy-user@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-user
