- galaxy-dev - lists.galaxyproject.org

dynamic loading of tools?
by Kostas Karasavvas 26 Nov '10

26 Nov '10

Hi all! It is my understanding that galaxy does not support dynamic loading of tools, i.e. for every new tool you add you need to manually change the conf file and restart the server. I am working on integrating functionality of another system into galaxy. To do this I am actually generating Galaxy tools automatically with certain scripts. The tools generated depend on certain parameters so there can be an arbitrary number of tools generated. Installing them manually and restarting the server is not ideal in this situation since it would depend on an administrator doing the work (rather than the user). The ideal scenario would be for me to create a tool that can dynamically create and add new tools. However, the latter (adding new tools dynamically) does not seem to be possible right now. I can think of other reasons that people would like that as well (e.g. for administration purposes). I am not sure if that was already discussed in the past but I was wondering if that is that something that you consider implementing in the near future. Thank you in advance, Kostas

7 15

Is there a galaxy-dist release coming soon?
by Ry4an Brase 26 Nov '10

26 Nov '10

The last two galaxy-dist releases came mere hours after we updated our staging instance from our development instance, so I thought this time I'd actually ask. If we do an update today or tomorrow are we going to be instantly out of date again? :) Thanks, -- Ry4an Brase 612-626-6575 Software Developer Application Development University of Minnesota Supercomputing Institute http://www.msi.umn.edu

9 15

November 24, 2010 Galaxy Development News Brief
by Jennifer Jackson 25 Nov '10

25 Nov '10

November 24, 2010 Galaxy Development News Brief Here are the highlights of the following upgrade: hg pull -u -r 8729d2e29b02 http://bitbucket.org/galaxy/galaxy-central/wiki/Features/DevNewsBrief/2010_… ---- What's New ---- Galaxy's FTP Server New Data Upload Option * User how-to: http://bitbucket.org/galaxy/galaxy-central/wiki/UploadViaFTP * Configuration instructions for local installs: http://bitbucket.org/galaxy/galaxy-central/wiki/Config/UploadViaFTP OpenID Login * User how-to and config instructions: http://bitbucket.org/galaxy/galaxy-central/wiki/OpenIDAuthentication NGS Simulation Tool * Allows user to simulate multiple Illumina runs with several parameters that can be set. o On each run, one position is randomly chosen to be polymorphic and sequencing errors are also simulated. o The primary output is a png with two different plots. o The other output shows summary statistics about the simulation. * NGS simulation tool location: tools/ngs_simulation/ngs_simulation.xml Tophat and Cufflinks RNA-seq Tools * Addition of RNA-seq analysis tools Tophat and Cufflinks. o Together, these tools can be used to analyze RNA-seq data to understand alternative splicing and isoforms, gene and isoform expression, and perform statistical tests for differential expression. o Galaxy supports Tophat version 1.1.1 and later and Cufflinks version 0.9.1 and later. (These are the versions included this distribution). Import or Export Workflows & Histories * Workflows can now be downloaded/exported to a file and uploaded/imported into Galaxy, making it easy to move workflows between Galaxy instances. * Beta feature: Histories can also be downloaded or moved from one Galaxy instance to another, subject to these limitations: o history archives can be uploaded/imported only via URL, not file o histories must be shared in order for them to be importable via archive o tags are not currently imported o reproducibility is limited as parameters for imported jobs are not always recovered and set Even Better Data Visualization with Trackster * Trackster now supports interactive filtering for VCF quality values and BED score values. * For example, a user can drag a slider to filter a file of splice junctions to view junctions supported by different numbers of reads. trackster splice example * Improved CIGAR support to BAM display. Properly displays matches, deletions, skipped bases, and clipping. Padding for insertions are currently not represented in the display. * GFF feature blocks are now displayed correctly, along with name, strand, and score information. * General enhancements o Removed right-hand pane, allow inline re-ordering and configuration of elements o Moved navigational controls to the top o Histogram display for LineTracks and overview o New navigational slider and new overview settings under the dropdown corresponding to the track name o Summary view now shows maximum y-axis value o Can change draw color of LineTrack o When editing track config, "Enter" and "Esc" keys submit and cancel the changes, respectively o Don't index bottom level for summary_tree, greatly reducing computation time (>5x speedup) while not sacrificing usability Refactored to pass JSLint * Tuning o Fix ReferenceTrack issue. o Don't re-add new datasets when refreshing after using "Add into current viz" link. o To prevent browser lockup, only display up to 50 lines of features by default (user-editable in future). Coming soon: add warning message when this occurs. o Fix LineTrack rendering bug when more than one tile on screen. Native Data set Re-organization * Galaxy now uses a set of data tables instead of simple loc files to organize, document, and store native genome data sets. * Why Data tables? Better data management for long term stability! o Allows the information in the loc file, including the path, to be changed. o By using a unique ID as the parameter value, data links in existing workflows are preserved. * Most tools (PerM, Bowtie, BWA, Lastz, Megablast, SRMA, Tophat) that previously used loc files now have the new data tables organization implemented. * Better data tracking has allowed for more informative genome name display in tool dropdown boxes. * For local installations: o See the new wiki describing how to use data tables: https://bitbucket.org/galaxy/galaxy-central/wiki/DataTables o More help for NGS tool setup (update pending): https://bitbucket.org/galaxy/galaxy-central/wiki/NGSLocalSetup ---- Updated & Improved ---- Sample Tracking * Complete re-write of the Framework and User interface (database schema unchanged). * New interactive interface to select files to transfer from the sequencer to Galaxy data libraries. * The data transfer feature now uses Galaxy RESTful API. * Full documentation detailing the new functionality and how to use it will be available within a few weeks through the home Galaxy Wiki. Instantiating Galaxy * New checkouts will now perform all necessary setup directly in run.sh, there is no longer a need to run setup.sh prior to run.sh. (setup.sh will be removed in a future distribution). Analysis Tools * Enable 'FASTX-Toolkit for FASTQ data' as a subsection under 'NGS: QC and manipulation' in tool_conf.xml.sample/main. Includes special handling for when the shell only allows for strict Bourne syntax. * Add descriptive labels to output dataset names for MACS peakcalling tool. * Taxonomy tools updated for better error reporting. Includes special handling for when the shell only allows for strict Bourne syntax. * Refactor sam_bitwise_flag_filter tool, simplifying it and making it fastet when there are multiple flag criteria Tool Dependency Enhancements * Addition of the 'package' type to <requirement> tags in the tool config. 1 Syntax for tool configs is: <requirements> <requirement type='package' version='X.Y.Z'>NAME</requirement> </requirements> 2 Next, a directory should be created, and the path to that directory should be set in universe_wsgi.ini as 'tool_dependency_dir'. 3 Galaxy will then source the following file prior to executing the tool's <command>: <tool_dependency_dir>/<NAME>/<X.Y.Z>/env.sh 4 The 'version' attribute of the 'requirement' tag is optional and if left off, Galaxy will look for the following instead: <tool_dependency_dir>/<NAME>/default/env.sh Data Libraries * UI: new style for dropdown menus. * Now uses jStore to save folder expansion state. * Pre-generate and cache variables so that expensive functions like jQuery.siblings, jQuery.filter and jQuery.find only have to be called a minimum amount of times. Provides significant speedup to loading of large data libraries. Genome Indexes * Add basic support for Bowtie indexes as a datatype (bowtie_base_index, bowtie_color_index), available via datatype conversion. Currently, the indexes need to be converted manually from the FASTA file before use in Bowtie, but they can be reused. * A new sample loc file (tool-data/all_fasta.loc.sample) was added which lists fasta files. A script (scripts/loc_files/create_all_fasta_loc.py) was created that can be used to generate this loc file for local installations. Data Formats * New gff2bed tool to convert GFF3 files to BED. * Modified Filter and Sort -> Filter tool to operate correctly on files with a variable number of columns, such as in SAM files. * New datatype added: VCF (variant call format). Histories * Add descriptive labels to output dataset names for MACS peakcalling tool. * Add name/designation to HDA name for new datasets created in collect_primary_datasets. Workflow Tuning * Shift management of the interaction between workflow outputs and HideDatasetActions to the front end editor. * No usability changes, but this resolves the issue with multiple HideDatasetActions being created. * Existing workflows displaying multiple HideDatasetActions per step on the Run Workflow screen will persist. These extra HideDatasetActions are harmless, but a simple edit workflow -> save will remove them. * Workflow Inputs change: o Workflow inputs that aren't a subtype of text, were previously not an option. o Added 'data' datatype to registry, which will allow both text and binary inputs (and their subtypes) to workflow input steps. o Note that this will allow a user to change the datatype of something to 'data'. User Interface (UI) * New function for downloading metadata files associated with datasets (such as bai indices for bam files). See the Save icon drop-down menu. * Enable display of unicode characters in history and workflow annotations and when listing and running workflows. * Dynamicically generated popup-style menus. Greatly improves load time, especially for data libraries having potentially large menu. * Labels next to checkboxes can now be clicked to check the corresponding box. * Radio boxes in tool forms now also have clickable labels as well. * New style for search boxes in grids. Grid items will no longer show outline when hovered upon if there are no actions to be performed. * Refactored refresh_on_change javascript code to run in galaxy.base when the page is loaded. * Remove the creation of a background element that closes the active menu clicked. Instead, bind an event to close active menus to the document object of current and all other framesets. Tested in IE. * Make links in split menu buttons "go through" instead of popping up the menu options. General * Functional Test Framework: new nose plugin that shows a diff between tests failed this time and last time. * Documentation update to add more options added to the sample config file. Bug Fixes! * Fix for TextToolParameter.get_html_field when provided value is an empty string but default value specified in tool is non-empty string. Fixes issue with rerun button where if a user had input an empty string, the form displayed when rerun would have the default value from the tool and not the actual previously specified value. * Fix for Integer/FloatToolParameter.get_html_field() when 'value' is provided as an integer/float. Fixes an issue seen when saving workflows: If an integer or float tool parameter is changed to a value of 0 or 0.0 and saved, the form field would be redisplayed using the default tool value; and not the value that is now saved in the database. * Fix for setting columns in workflow builder for ColumnListParameter. e.g. allows splitting lists of columns by newlines and commas and strips leading 'c's. * Fixes for rerun action to recurse grouping options when checking unvalidated values and cloned HDAs. Better selection of corresponding HDAs from cloned histories, when multiple copies exist. * Have rerun action make use of tool.check_and_update_param_values(). Fixes Server Error issue when trying to rerun updated tools. * Fix for display framework to work with workflows that contain tools that have been updated. Previously, this would cause a server error when trying to view a workflow or a page with an embedded workflow that contained an updated tool. * Fix bug that was causing Page item selection grids to be initialized twice and hence causing grid paging to fail. * Add some space between adjacent embedded items on Pages. * Fix path to closebox.png image so screencast close button is shown correctly. * Fix the Admin -> Manage Jobs interface when using multiple Galaxy processes * When possible (e.g. Python >= 2.6), don't use tons of memory to handle zipped uploads. * Fix cluster stdout/stderr handling that could cause excessive memory usage if stdout/stderr were very large. * Make the PBS runner actually stop jobs when a user deletes output. This would only work before if the Galaxy user was a PBS "operator" and only using a single process setup. * Cause waiting jobs to fail if any of their inputs fail to set metadata correctly. * Fix 'import from current history' for Data Libraries that was showing metadata files that are not visible. Fix this same issue for 'Copy history items' feature. * DRMAA runner now uses get_id_tag() in Wrapper instead of job_id directly for creation of .sh .o and .e files, as well as some debugging. * Prevent Rename Dataset Action from allowing a blank input. Get Galaxy! http://bitbucket.org/galaxy/galaxy-central/wiki/GetGalaxy hg clone http://www.bx.psu.edu/hg/galaxy galaxy-dist Galaxy is supported in part by NSF, NHGRI, the Huck Institutes of the Life Sciences, and The Institute for CyberScience at Penn State. -- Galaxy Team

1 0

Sample tracking data transfer and proxy prefix
by Sarah Diehl 25 Nov '10

25 Nov '10

Hi, it seems like I have another issue with the combination of the sample tracking data transfer feature and using a proxy prefix. I get a 403 Forbidden error in the data_transfer.log, because it tries to access http://host.de/api/requests/ instead of http://host.de/galaxy/api/requests/. Is there an option somewhere that I missed? I would be very grateful for any ideas how to solve this problem. Best regards, Sarah

2 1

Re: [galaxy-dev] Existing efforts to convert the QIIME pipeline to Galaxy?
by Jim Johnson 24 Nov '10

24 Nov '10

Tim, I hope to also look at incorporating QIIME into our local Galaxy instance at the University of Minnesota, but probably won't be able to start for a couple weeks. It would be good to develop that in coordination with others. I just finished incorporating "Mothur" metagenomics suite http://www.mothur.org/ (Dr. Patrick Schloss, Department of Microbiology & Immunology at The University of Michigan) into our Galaxy server at the University of Minnesota. I hope to contribute that to http://community.g2.bx.psu.edu/ after some testing by our researchers. If the Galaxy wrappings for Mothur are of any interest to you, I can send you a copy any time. Thanks, JJ James E Johnson Minnesota Supercomputing Institute University of Minnesota On Nov 23, 2010 at 07:22 AM, Tim te Beek wrote: > Hello all, > > Is anyone aware of any existing efforts to port the QIIME sequencing > pipeline (http://qiime.sourceforge.net/) to Galaxy? I would like to run > QIIME analyses through Galaxy to get better control of > intermediate processing steps, but before I start to convert (a subset of) > some 90 scripts, I'd first like to make sure this has not been done before > by anyone willing to share their work. > > So: has anyone converted the QIIME pipeline to Galaxy before, and would they > be willing to share their scripts? > > Best regards, > Tim

1 0

Re: [galaxy-dev] Existing efforts to convert the QIIME pipeline to Galaxy?
by Jim Johnson 24 Nov '10

24 Nov '10

Tim, I hope to also look at incorporating QIIME into our local Galaxy instance at the University of Minnesota, but probably won't be able to start for a couple weeks. It would be good to develop that in coordination with others. I just finished incorporating "Mothur" metagenomics suite http://www.mothur.org/ (Dr. Patrick Schloss, Department of Microbiology & Immunology at The University of Michigan) into our Galaxy server at the University of Minnesota. I hope to contribute that to http://community.g2.bx.psu.edu/ after some testing by our researchers. If the Galaxy wrappings for Mothur are of any interest to you, I can send you a copy any time. Thanks, JJ James E Johnson Minnesota Supercomputing Institute University of Minnesota On Nov 23, 2010 at 07:22 AM, Tim te Beek wrote: > Hello all, > > Is anyone aware of any existing efforts to port the QIIME sequencing > pipeline (http://qiime.sourceforge.net/) to Galaxy? I would like to run > QIIME analyses through Galaxy to get better control of > intermediate processing steps, but before I start to convert (a subset of) > some 90 scripts, I'd first like to make sure this has not been done before > by anyone willing to share their work. > > So: has anyone converted the QIIME pipeline to Galaxy before, and would they > be willing to share their scripts? > > Best regards, > Tim

1 0

pbs_submit failed, PBS error 15024: Max hop count exceeded
by Grainne Kerr 23 Nov '10

23 Nov '10

Dear all, I'm not sure if its a galaxy issue, but perhaps someone could give me some advice on where to look or some configuration to set or... I am trying to set up a local installation of Galaxy in for a multi-uer environment. I've installed it on a compute cluster, running centos 5.5, python2.4, a TORQUE scheduler with Maui. Server name: b110-sc-hdn Compute cluster has three nodes. These are called: headnode, computenode1, computenode2 The default queue on the cluster is called "galaxy_queue". I've set jobs to run on this queue in the universe_wsgi.ini file However, when I try to run a job, I get the following error: "galaxy.jobs.runners.pbs DEBUG 2010-11-14 16:48:56,410 (59) pbs_submit failed, PBS error 15024: Max hop count exceeded" >From the research I have done, seemingly this occurs when there are issues resolving the domain name. But, I don't know how to check this or fix this. I've ran the attached python test script which imports pbs python package. And it works fine. In the script, if I change the server name to "b110-sc-hdn", I recreate the error. Is there something obvious I am not getting? Any help would be very much appreciated and thanks alot for an exceptional tool! Grainne.

2 2

ABySS genome assembler integration into Galaxy
by Richard Bruskiewich 23 Nov '10

23 Nov '10

Colleagues, Rumor has it that some developer in the Galaxy community is already integrating the ABySS genome assembler ( http://www.bcgsc.ca/platform/bioinfo/software/abyss/) into Galaxy. Does anyone have any details about this? Cheers -- *Richard Bruskiewich, PhD* Senior Scientist, Computational and Systems Biology Applications Team for Computational Genomics T.T. Chang Genetic Resources Center International Rice Research Institute

2 1

Existing efforts to convert the QIIME pipeline to Galaxy?
by Tim te Beek 23 Nov '10

23 Nov '10

Hello all, Is anyone aware of any existing efforts to port the QIIME sequencing pipeline (http://qiime.sourceforge.net/) to Galaxy? I would like to run QIIME analyses through Galaxy to get better control of intermediate processing steps, but before I start to convert (a subset of) some 90 scripts, I'd first like to make sure this has not been done before by anyone willing to share their work. So: has anyone converted the QIIME pipeline to Galaxy before, and would they be willing to share their scripts? Best regards, Tim

1 0

empty_field validator for multi-select column parameter
by Peter 23 Nov '10

23 Nov '10

Hi all, I have a tool where for one parameter I want the user to pick one or more columns from a tabular file. Other tools do this too, e.g. filters/uniq.xml (the Statistics "Count" tool) uses: <inputs> <param name="input" type="data" format="tabular" label="from query" help="Query missing? See TIP below"/> <param name="column" type="data_column" data_ref="input" multiple="True" numerical="False" label="Count occurrences of values in column(s)" help="Multi-select list - hold the appropriate key while clicking to select multiple columns" /> ... </inputs> I would like extend this by adding a validator to prevent the user trying to run my tool with no columns (in fact, I think this would be a good idea for filters/uniq.xml as well - currently the error is only spotted when the tool is run). There is a list of validators given on the wiki page, http://bitbucket.org/galaxy/galaxy-central/wiki/ToolConfigSyntax I expected to be able to use the empty_field validator, but that doesn't work - is this a bug?: <param name="column" type="data_column" data_ref="input" multiple="True" numerical="False" label="Count occurrences of values in column(s)" help="Multi-select list - hold the appropriate key while clicking to select multiple columns"> <validator type="empty_field" message="Pick at least one column"/> </param> I found a workaround, based on the fact that no columns is passed to the command line tools as the string 'None', using the expression validator: <param name="column" type="data_column" data_ref="input" multiple="True" numerical="False" label="Count occurrences of values in column(s)" help="Multi-select list - hold the appropriate key while clicking to select multiple columns"> <validator type="expression" message="Pick at least one column">str(value)!='None'</validator> </param> Peter

1 1