Hi Andreas,

Assuming you have executed the migration process for the tools so they are now 
installed into your Galaxy instance from the tool shed, you can check the 
entries in the migrated_tools_conf.xml file and get the ids.  Entries will look 
something like the following where you can get the id from the <id> tag.

    <tool 
file="toolshed.g2.bx.psu.edu/repos/devteam/picard/e0232cbac965/picard/rgPicardMarkDups.xml"
 guid="toolshed.g2.
bx.psu.edu/repos/devteam/picard/rgPicardMarkDups/1.56.0">
            <tool_shed>toolshed.g2.bx.psu.edu</tool_shed>
            <repository_name>picard</repository_name>
            <repository_owner>devteam</repository_owner>
            
<installed_changeset_revision>e0232cbac965</installed_changeset_revision>
            
<id>toolshed.g2.bx.psu.edu/repos/devteam/picard/rgPicardMarkDups/1.56.0</id>
            <version>1.56.0</version>
            </tool>

Greg Von Kuster


On Nov 15, 2012, at 9:10 AM, Andreas Kuntzagk wrote:

> Hi,
> 
> I upgraded to the latest version and again some tools moved to tool_shed. I 
> now need to set job runners for these tools. Is there an easy way to get the 
> tool_ids other then hovering the mouse over the tool name and write down the 
> id?
> 
> regards, Andreas
> 
> -- 
> Andreas Kuntzagk
> 
> SystemAdministrator
> 
> Berlin Institute for Medical Systems Biology at the
> Max-Delbrueck-Center for Molecular Medicine
> Robert-Roessle-Str. 10, 13125 Berlin, Germany
> 
> http://www.mdc-berlin.de/en/bimsb/BIMSB_groups/Dieterich
> ___________________________________________________________
> 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/


___________________________________________________________
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/

Reply via email to