$ hg clone http://www.bx.psu.edu/hg/galaxy galaxy-dist
$ hg pull -u -r 36ad8aa7b922
Required Metadata Reset
When a tool shed repository is installed into your local Galaxy instance, metadata is generated for the repository as a part of the installation process and stored in the tool_shed_repository.metadatatable column in the Galaxy database. This automatic process inspects the contents of the specific revision of the installed repository and generates and stores important information about it. This metadata information is used by certain Galaxy features. As new features are added to Galaxy or the tool shed, the process that generates this installed tool shed repository metadata within the Galaxy instance may be enhanced to accommodate information about the new features. Read more…
Galaxy Enhancement related to installed tool shed repositories
Tools installed from the Galaxy Tool Shed can now have handlers and runners assigned in universe_wsgi.ini based on their "short id" as opposed to their full "tool shed id".
For example, the following lines could be placed in [galaxy:tool_runners] :
toolshed.g2.bx.psu.edu/repos/devteam/bwa_wrappers/bwa_wrapper/1.2.3 = foo:// toolshed.g2.bx.psu.edu/repos/devteam/bwa_wrappers/bwa_wrapper = bar:// bwa_wrapper = baz://
And will be interpreted as:
version 1.2.3 of the bwa_wrapper installed from the toolshed would use runner foo://
all other versions installed from the toolshed would use runner bar://
any tool with <tool id="bwa_wrapper"> , regardless of how it's installed (from the toolshed or directly added to tool_conf.xml) would use runner baz://
It is important to note that only the most specific match will be used if there are multiple matches (as in the given example).
Tool Shed Enhancement
The functional test framework for the tool shed has been significantly enhanced. For details about how to run functional tests for your local tool shed, read more here…
Tool Shed Fixes
The tool shed now displays informative error messages when invalid XML .sample files are included in a repository.
Fixes for the functional test framework for testing tools contained in tool shed repositories installed into Galaxy instances, thanks to Lance Parsons.
The tool shed's HgWebConfigManager is now thread-safe.
Tools contained in tool shed repositories installed into a local Galaxy instance will now be automatically reloaded into the Galaxy tool panel if the tool config was changed in the update, but the tool versions did not change (e.g., if the help text or something else not requiring a new tool version changed).
- All information related to installed tool dependencies has been filtered to ensure it is renderable on a browser page ( escape characters, illegal characters, etc are filtered out ).
This release includes a fix for reinstalling tool dependencies defined for an uninstalled tool shed repository if the tool_dependency_dir config setting is not defined in the Galaxy configuration file ( universe_wsgi.ini ).
Fix output definition for GTF filter by attribute values list.
Allow spaces in Cuffdiff group names.
- Add simple read group options.
- Remove deprecated parameters.
- Add simple read group options.
RNA-Seq Tool Suite with updated tools highlighted
Galaxy Track Browser (Trackster)
Add BAM to BigWig converter for read coverage data.
- When creating a new track browser for a dataset:
default to dataset's dbkey
- default the view to the first chromosome
UI, Libraries, Histories
User Interface (UI): Tabular Display: For extremely wide datasets (50 columns or more), revert to the old (non-table) display behavior. Rational: the incremental renderer sometimes has issues with these types of files.
Libraries: Include custom genomes in dbkey field when uploading library datasets.
Histories: Create .bai indexes when importing BAM (.bam) datasets while importing/exporting histories.
note: a specific .bai index is associated with every .bam dataset, and is required, but the index file is not displayed in a history as a distinct dataset. Index files can be downloaded/accessed using the 'save' function in the BAM dataset's history item. When loading BAM datasets into Galaxy, or when they are created by tools, the .bai index is created automatically by those processes.
Pull Requests Accepted
Trello Issue Tracking
Want to review what we're working on, vote, or submit a new idea to the Galaxy team? Our new wiki has all the details! Using the Galaxy Issue Board
Although there are no specific known security fixes in this distribution, all Galaxy instance maintainers are strongly encouraged to run the latest release to take advantage of other improvements and fixes.
- Fix for text area tool parameters (form builder) when a size isn't provided.
- Fix for error reporting link throwing server errors.
Fix for SelectToolParameter in rerun and workflows when multiple="true"
- Fix IE console errors.
- Fix unhandled 'new' state for datasets in the history panel.
- Handle adding datasets to history panel without refresh.
Fix Trackster links when dbkey is empty.
- Fix text selection of dataset names in the history panel.
- Fixes to history-related functional tests.
- Fix rendering of 'save' pop-up menu downloadable composite files
example: BAM datasets have two download components, .bam (primary dataset) and .bam.bai (the index)
GCC2013 Training Day Topic Nominations are now open through January 11th.
Get a word in now.