Using history annotation will only work well if it could be automatically
populated with tool versions. Leaving it up to the user to insert them
manually won't work because people would forget to do this, especially if they
are working under time pressures. In my ideal world, the tool version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Kanwei,
I'm very much interested in this feature, i.e "to keep track of tool
versions that ran automatically".
What do you mean by "history annotation" ? Is it some custom editable
field by the user or are you planning to set this automatically wh
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, Kan
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 wrote:
> Hi,
>
> in order to reproduc
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?"
5 matches
Mail list logo
