Development News Brief
The tools NGS: Mapping → Map with BWA for Illumina and Map with BWA for SOLiD have moved from the Galaxy distribution to the Galaxy Main Tool Shed.
Migration scripts will run upon Galaxy's first launch (after updating to this release) that will automatically handle installing these BWA tool wrappers from the Tool Shed. BWA itself and target reference genomes should still be installed as described in the Galaxy wiki - start in the Tool Dependencies section.
BWA is a fast light-weighted tool that aligns relatively short sequences (queries) to a sequence database (large), such as the human reference genome. It is developed by Heng Li at the Sanger Insitute. Li H. and Durbin R. (2009) Fast and accurate short read alignment with Burrows-Wheeler transform. Bioinformatics, 25, 1754-60.
As reported in the September 20th News Brief, the Tool Factory is already available in the tool shed. At that time, the manuscript was accepted, but pending publication. The E publication is now available.
Creating re-usable tools from scripts: The Galaxy Tool Factory. Lazarus R, Kaspi A, Ziemann M; The Galaxy Team. Bioinformatics. 2012 Sep 28. (Epub ahead of print) PMID: 23024011 (PubMed - as supplied by publisher)
Short re-cap → Read more…
The Tool Factory is a pure Galaxy scripting environment that makes running simple quick and dirty tasks really easy, and can also generate new Galaxy tools with functional tests!
The Tool Factory ia available for private clone installations from the main Galaxy Tool Shed as the toolfactory - see your local Galaxy admin menu.
Before you install - THIS IS IMPORTANT!! The Tool Factory allows unrestricted scripting - NO SANDBOX!! so is far too dangerous for production sites. It can only be run by local Galaxy site administrators. Please, do NOT install on public Galaxy instances. Generated tools are safe if the script they wrap is safe.
PostgreSQL users with extremely large databases can now use a more efficient database-driven cleanup script. The lifecycle is similar to the old script, but the syntax is different. The new script can be found at:
If called with the
--help option, it will output usage information. The dataset cleanup documentation will be updated to refer to this script.
The following sections of the tool shed wiki provide information about features introduced in this Galaxy release.
In some cases installing a repository into a Galaxy instance may result in errors. When this happens the repository's status attribute will be set to an error state, and the repository will be displayed similar to the example shown in the following page. Read more…
This document provides the details for a simple feature of the tool shed that enables displaying the license information (or possibly other kinds of information) for tools included in a repository. Read more…
In most cases changing the version of a tool dependency requires a change to the dependent tool's version as well. This ensures reproducible behavior for Galaxy instances in which the tool is installed. However, in some cases the owner of a repository may change the version or type attribute of a tool dependency in it's definition in the repository without changing the version of the dependent tool. Again, this should not often occur! Read more…
The following sections of the tool shed wiki have been updated to more thoroughly describe features.
If you want to clone a repository from the tool shed using mercurial from a terminal session, you have to install the Mercurial Distributed SCM (the tool shed requires Mercurial version 2.2.3 or newer). Read more…
If you want to push a changeset to a repository in the tool shed using mercurial from a terminal session, you have to install the Mercurial Distributed SCM (the tool shed requires Mercurial version 2.2.3 or newer). Read more…
With each change set committed and pushed to a repository, whether using hg from the command line or by uploading or deleting files using the tool shed UI features, metadata about the contents of the change set is generated. This document provides the details about this process. Read more…
Display warning or error message if attempting to install tool dependencies defined in a tool shed repository when the
tool_dependency_dirconfig setting is not set in the Galaxy config.
Apply styles when displaying the long description when viewing a tool shed repository.
Handle the case where the main Galaxy tool shed is unavailable when checking for migrated tools or updates to installed tool shed repositories when starting the Galaxy server.
Allow the Galaxy admin to reset metadata on installed tool shed repositories.
A Galaxy tool migration stage is defined as the stage level (e.g., 0002, 0003, 0004, etc.) at which a specific set of tools was migrated out of the Galaxy code distribution and added to the main Galaxy tool shed.
Executing the process for a specific tool migration stage can be done at any time, not just at the time you are starting your Galaxy server as discussed in the previous sections of this document. Read more…
Tool changes that enable clearer experimental tracking and ease reproducibility
Tool versions and exit codes
Display tool version in workflow tool form editor.
- Display tool version when running a workflow.
- Always allow selecting different (e.g. 'older') versions of a tool when selected from the tools menu.
Exit codes are now included in the database and displayed on a tool's output dataset history box in the user interface (UI).
Always load the tool version with the highest lineage (newest version) into the tool panel/menu so that the newest version is always used for a new tool run (e.g. but not for a rerun/previously existing workflow unless modified by user).
- Refactor tool version selection during rerun; previously, the currently selected version displayed in the dropdown box might not have been the version of the tool actually being displayed/run.
- Better handling of determining tool/version in workflow tool module.
- Fix for writing the
integrated_tool_panel.xmlwhen a section has been removed from
- Better handling of trying to access a tool when it is no longer loaded, but the item is still listed in the tol panel (due to not refreshing the page after remove the tool).
Cufflinks, Cuffcompare, Cuffmerge, and Cuffdiff: Add support for v2.0+.
Fix Cuffdiff parameter group naming.
- More about Bowtie2
- More about Tophat/Tophat2
- More about Cufflinks, Cuffcompare, Cuffmerge, & Cuffdiff
Add requireJS support for data, visualization, tools and update dependencies.
DataProviderRegistryobject to simplify provider creation.
Circster performance improvement: render quantitative data as a single path rather than many small paths.
- Fix embedded visualizations and bookmarking which were broken during refactoring.
- Fix issues with Genomes API: handle periods in keys, fix typo, and list genomes when querying.
Fix to correctly display error message when attempting to run a workflow missing tools.
Viewing and Downloading of workflows with missing tools now handled gracefully.
Prevent potential login XSS, sanitize all reflected parameters.
Remove pre-filled password/confirm/current fields from edit user info.
Computetool to only allow for execution of a limited set of expressions.
- Set the correct job name when submitting jobs as system users.
- Upcoming Events and Deadlines
- 35 new papers
- CBIIT's new public Galaxy Server
- Open Positions at three different institutions
- Tool Shed Contributions
- Other News