standOff. When we have changed our mind. Some entries in the table begin with a word in capitals and the reason for it. EVIDENCE CORRECTED — the finding still stands, but we had quoted the wrong sentence from the paper, and the quotation has been replaced with the right one. RETRACTED — the entry itself was wrong; it stays on the page, marked, with the reason, rather than being deleted. WITHDRAWN AND REPLACED — the entry was wrong, and a corrected version of it appears in the entries below. Each mark carries its own reason, in brackets, because the reasons differ from one entry to the next. An entry we have WITHDRAWN is removed from this page and kept in the record, with its reason. A line reading Audit and a date is a later re-reading of the entry against its whole sentence: DOUBTFUL means it was kept, and the reason says what is loose about it. Quotation marks inside the tagger's sentence. Where a tag is the tagger's own sentence, a phrase in quotation marks inside it is borrowed from the paper — the tagger's wording around it is not. The paper's own sentence is the evidence quote shown on the same row, so the borrowing can be checked against the thing borrowed from without leaving this page. Nothing inside quotation marks anywhere on this page is ours: if it is quoted, it is the paper's. Whose words a concept carries. A concept entry records a term the paper itself uses, so the term, the sense given for it, and its evidence are the paper's own words, quoted where the paper fixes them. This is the opposite of a sense entry in the tag table, which is the tagger's sentence about how the paper uses a term. Where a concept entry could not be grounded in the paper's words, the entry says so on its own row.| relation to other work | claim_relations | how this paper stands to another: agrees, contradicts, extends, qualifies |
| claim type | claim_type | the shape of the claim: existence, mechanism, method, critique, prediction, null |
| concept edge | concept_edges | an asserted relation between two concepts, with the sentence asserting it |
| concept | concepts | an idea the paper works with, quoted where the paper uses it |
| contribution | contribution | what the paper claims to add |
| limitation | limitations | what the paper says its evidence cannot support |
| mechanism | mechanisms | how the reported effect is said to come about |
| method | method | how the paper produced its evidence |
| object of study | object_of_study | what the paper is about — the thing it investigates |
| phenomenon | phenomenon | the effect or regularity under study |
| research question | research_question | the question the paper sets itself |
| sense | senses | a distinct use of a term, quoted where the paper fixes it |
| unrecordable relation | unhoused_relations | a relation the paper asserts that this vocabulary cannot express, with the reason |
The Galaxy platform for accessible, reproducible and collaborative biomedical analyses: 2018 update
Abstract
object_of_studycontributionclaim_typeconcepts↗concepts↗concepts↗sensesclaim_relationsconcept_edgesGalaxy (homepage: https://galaxyproject.org , main public server: https://usegalaxy.org ) is a web-based scientific analysis platform used by tens of thousands of scientists across the world to analyze large biomedical datasets such as those found in genomics, proteomics, metabolomics and imaging. Started in 2005, Galaxy continues to focus on three key challenges of data-driven biomedical science: making analyses accessible to all researchers, ensuring analyses are completely reproducible , and making it simple to communicate analyses so that they can be reused and extended. During the last two years, the Galaxy team and the open-source community around Galaxy have made substantial improvements to Galaxy's core framework, user interface, tools, and training materials. Framework and user interface improvements now enable Galaxy to be used for analyzing tens of thousands of datasets, and >5500 tools are now available from the Galaxy ToolShed. The Galaxy community has led an effort to create numerous high-quality tutorials focused on common types of genomic analyses. The Galaxy developer and user communities continue to grow and be integral to Galaxy's development. The number of Galaxy public servers, developers contributing to the Galaxy framework and its tools, and users of the main Galaxy server have all increased substantially.
INTRODUCTION
research_questionmechanisms↗concepts↗concepts↗concepts↗concepts↗concepts↗concepts↗unhoused_relationsunhoused_relationssensesclaim_relationsconcept_edgesAdvances in biomedicine and biology increasingly rely on analysis of large datasets. Started in 2005, the Galaxy Project ( https://galaxyproject.org ) ( 1–3 ) maintains a focus on enabling data-driven biomedical science by pursuing three goals: (a) accessible data analysis serving all scientists regardless of their informatics expertise and tool developers seeking a wider audience and broad integration of their tools; (b) reproducible analyses regardless of the particular platform and (c) transparent communication of analyses, which in turn enables reuse and extension of analyses across communities of practice. The Galaxy Project consists of four complementary components:
concepts↗The main public Galaxy server ( https://usegalaxy.org )—this server is the subject of this article and has been online since 2007. It features a rich toolset for large-scale genomics analyses, terabytes of public data for use, and hundreds of shared analysis histories, workflows, and interactive publication supplements. This server has more than 124,000 registered users whom run ∼245,000 analysis jobs each month.
concepts↗concepts↗concepts↗unhoused_relationsThe Galaxy framework and software ecosystem ( https://github.com/galaxyproject )—an open-source software package that anyone can use to run a Galaxy server on any Unix-based operating system. The Galaxy ecosystem includes a software development kit (SDK) for Galaxy tool development, API language bindings for multiple programming languages, software for scripting Galaxy interactions, and tools for automating setup and deployment of Galaxy and its plugins such as tools and visualizations.
concepts↗The Galaxy ToolShed ( https://toolshed.g2.bx.psu.edu/ )—a community-driven resource for the dissemination of Galaxy tools, workflows, and visualizations. This server functions as an ‘AppStore’ for Galaxy servers where developers and Galaxy admins can host, share, and install Galaxy tools, workflows and visualizations.
concepts↗The Galaxy Community ( https://galaxyproject.org/community/ )—distinct and complementary subcommunities make key contributions to all aspects of the Project. These subcommunities address the needs and desires of every category of stakeholder including users, administrators, developers, resource providers and educators.
Galaxy has served hundreds of thousands of users, been used in >5700 scientific publications, and provided 500+ developers with a framework provisioning accessible, transparent, and reproducible data analysis ( https://galaxyproject.org/galaxy-project/statistics/ ). Many instances of the framework have been installed, including Galaxy Main ( https://usegalaxy.org ) and over 99 publicly accessible servers ( https://galaxyproject.org/public-galaxy-servers/ ), serving biomedical and other domain-specific research. Significant growth has occurred across all sectors of the Galaxy Project within the past two years (Figure 1 ).
Circular barplot illustrating recent growth of the Galaxy Project across several independent facets. In the past two years, usage of the main public Galaxy server has increased 60%, the number of tools and supported versions has increased 53%, and the amount of data analyzed on the main server has increased 72%. A growing number of public instances (18% increase) and cloud-based Galaxy instances (38% increase) provide researchers with a wider range of options for scalability and application domains. Additionally, more developers (45% increase with 63% more commits to the codebase) contributed to the Galaxy framework and software ecosystem. Question and answer activity on the Galaxy Biostars forum increased 68%.
NEW FEATURES
Scalability
phenomenonlimitationsconcepts↗unhoused_relationsScalability is amongst the most significant challenges that Galaxy faces as the size and number of biomedical and especially genomics datasets continues to grow. For instance, single-cell RNA-seq experiments routinely generate hundreds or thousands of primary datasets. As a web-based application, Galaxy must scale both in its web-based interface and on its backend server and do so in a multiuser environment.
mechanisms↗limitationsconcepts↗concepts↗unhoused_relationssensesclaim_relationsconcept_edgesUser interface scalability enables scientists to use the Galaxy web interface to analyze many datasets, apply (collective) operations on them, and design pipelines to analyze them. Galaxy implements a variety of features to facilitate analyzing large numbers of datasets, including workflows and collections . Our recent optimizations of the user interface (UI) yielded a significant improvement to frontend scalability. We benchmarked the optimizations by replicating an experiment conducted on single Hematopoietic stem cells and multipotent progenitors ( 4 ) to quantify the expression of 64 000 transcripts, which generates 11 872 history items. Galaxy ran this proof of concept experiment seamlessly using existing standard tools, whereas earlier versions of Galaxy would not have been able to support this analysis.
method↗mechanisms↗concepts↗concepts↗concepts↗concepts↗concepts↗concepts↗concepts↗concepts↗unhoused_relationssensesServer scalability refers to the Galaxy's ability to execute many data analysis/manipulation tasks for many users. This is achieved by advantageously utilizing a range of available computing resources. The Galaxy framework runs on various platforms, from a standard laptop to institutional clusters and cloud-based platforms. Galaxy is highly versatile in its ability to deploy jobs (atomic units of work), as it can leverage a multitude of workload managers including Slurm ( 5 ), HTCondor ( 6 ), Apache Mesos ( 7 ) and Kubernetes ( https://kubernetes.io ), among others, in addition to a built-in lightweight job running system. Recent enhancements to Galaxy's job management include dynamic job destination assignment (which facilitate automatic job parameter-specific resource selection), delay in job queuing (e.g. for workflows), automatic job re-submission (e.g., on job failure due to a temporary cluster error), and means of implementing fair-share prioritization schemes. These features are being used on Galaxy Main (Figure 2 ) to leverage cloud computing resources for better job throughput. Specifically, Galaxy Main is now configured to take advantage of the XSEDE infrastructure ( 8 ) that includes Bridges and Stampede resources as well as the Jetstream cloud ( 9 ). The benefits of using these resources include the ability to run larger jobs, as shown in Figure 3 . Additionally, use of these resources has enabled new types of analysis to be enabled on Main. Notably, this includes Galaxy Interactive Environments through the ability to use containerization technologies and provide sufficient isolation of individual jobs from other processes running on the same underlying compute infrastructure.
Schematic of servers and services in use at Galaxy Main. ( A ) A global overview of Galaxy Main resources. When users interact with usegalaxy.org, their browser connects to one of two frontends (shown as web-01/02) with file uploads being handled by web-03/04; each of these web servers connects to a database server and mounts a set of shared distributed file systems. Web-03/04 also prepares and schedules jobs using Slurm directly to manage compute tasks on fifteen dedicated compute nodes, which also directly mount the shared distributed file systems. A combination of Slurm and Pulsar ( https://github.com/galaxyproject/pulsar ) are used to manage tasks and for dataset file staging, respectively, on the Jetstream cloud at Indiana University (IU) and the Texas Advanced Computing Center (TACC). Communication between Galaxy and Pulsar is handled using the RabbitMQ ( https://www.rabbitmq.com/ ) message broker. Additional jobs are sent to the supercomputer systems Bridges at Pittsburgh Supercomputing Center (PSC) and Stampede at TACC using Pulsar. These various compute resources are chosen based upon tool and job characteristics. See, e.g. https://github.com/galaxyproject/usegalaxy-playbook/wiki/Infrastructure for specific and up-to-date information. ( B ) Multiple frontend servers provide Galaxy content to users by utilizing round-robin load balancing. Nginx ( https://nginx.org/ ) is used to serve HTTP content from the Galaxy uWSGI web application. Individual software processes are monitored and controlled using Supervisor ( http://supervisord.org/ ). Each of these frontend servers connects to a PostgreSQL ( https://www.postgresql.org/ ) database server. ( C ) Layout of data schemes used by Galaxy Main is optimized for application speed, concurrent access, and versioned content. Each Galaxy frontend server utilizes a combination of shared distributed file systems, CVMFS for versioned semi-static content and TACC’s Corral filesystem via NFS for mutable content, along with server-specific local file systems. (D) CernVM File System (CVMFS) infrastructure hosted by the Galaxy Project that is used at Main and available for access to any other Galaxy instance. Stratum 0 contains the single-source modifiable data repositories. File content is served using the Apache HTTP server ( https://httpd.apache.org/ ). To enable redundancy and scaling to a large number of clients, Stratum 1 replica servers are hosted at multiple locations and utilize Squid ( http://www.squid-cache.org/ ) for data caching. Additional replica servers can also be hosted by community members. Individual clients (Galaxy instances and compute nodes) access data content from Stratum 1 servers using a Filesystem in Userspace (FUSE) mount.
limitationsunhoused_relationsunhoused_relationsclaim_relationsEnabling automated selection and use of specialized national cyberinfrastructure compute resources from Galaxy Main enhances user-experience. It is now possible to run jobs that are up to an order of magnitude larger than before by using Bridges and Stampede. New types of jobs, such as interactive environments (see Advances in tools section), that require execution isolation due to security concerns are enabled by utilizing virtualization facilitated by the Jetstream cloud. Consequently, it is possible to concurrently run more jobs due to the increase in processing capacity.
mechanisms↗limitationsconcepts↗concepts↗unhoused_relationsA complete Galaxy server with a full repertoire of tools and reference data can be run on major cloud platforms. These servers are launched independently by users, and come pre-configured with hundreds of tools and reasonable default settings typical of a production server. Notably, launched instances do not have usage quotas and can be customized to install any desired tool. We have designed a cloud-agnostic approach for leveraging these resources by developing the abstraction library CloudBridge ( 10 ) and a new CloudLaunch application. These two solutions make it possible to launch Galaxy instances across a variety of cloud providers while reducing the requirement to build and maintain cloud-specific resources (e.g. machine images, file systems). There are now 10 different flavors of Galaxy available for launching on major clouds including Amazon Web Services, Jetstream and Microsoft Azure ( https://launch.usegalaxy.org ).
Advances in tools
concepts↗unhoused_relationssensesThe Galaxy ToolShed ( 11 ) assumes the role of an AppStore for Galaxy instances by hosting thousands of tools. The ToolShed improves tool availability, deployment, and portability across Galaxy servers and computing environments.
Updated tool suite
Over the last two years, we have expanded both the quantity and quality of the tools available on the Galaxy ToolShed. As of April 2018, the ToolShed hosts 5628 tools, which shows 53% growth since 2016, and ∼2000 repositories had at least one new update. Examples of new tools include: GEMINI for exploring genetic variation ( 12 ); mothur for analyzing rRNA gene sequences ( 13 ); QIIME for quantitative microbiome analysis from raw DNA sequencing data ( 14 ); deepTools for explorative analysis of deeply sequence data ( 15 , 16 ); HiCexplorer ( 17 ) for analysis and visualization of Hi-C data; ChemicalToolBox for comprehensive access to cheminformatics libraries and drug discovery tools ( 18 ); minimap2 ( https://arxiv.org/abs/1708.01492 ) and poretools for long read sequencing analysis ( 19 ); MultiQC ( 20 ) to aggregate multiple results into a single report; a new RNA-seq analysis tool suite with modern analysis tools such as Kallisto ( 21 ), Salmon ( 22 ), Deseq2 ( 23 ) and STAR-Fusion ( 24 ), and GenomeSpace ( 25 ), a cloud-based interoperability tool.
Tool environment and interface
mechanisms↗concepts↗unhoused_relationsThe portability and backward-compatibility of the Galaxy tools environment is improved significantly. Accordingly, a tool configuration now includes a tool profile version , which is used to ensure compatibility between a version of a tool and its targeted Galaxy version. In addition, tool profile versions allow for the evolution of new and better tool defaults and behaviors while maintaining backwards compatibility. We also improved the ToolShed API and its interface to facilitate installing tools missing from an imported workflow. We improved the installation process so that restarting Galaxy is not required to use a newly installed tool.
Interactive analysis and visualization
mechanisms↗limitationsconcepts↗concepts↗concepts↗unhoused_relationssensesclaim_relationsGalaxy's UI makes it possible for anyone to run complex analyses. However, a complete analysis of genomic data often requires custom scripts or visualizations, especially at the beginning (data preparation) or end (data summarization) of analyses. To meet these customized needs, we recently introduced Galaxy Interactive Environments ( 26 ), an integration of Galaxy with Jupyter (RStudio is in development)—a commonly used interactive scripting platform. With Interactive Environments, Galaxy users benefit from existing computational infrastructure via both graphical UI and ad hoc scripting, or any combination of these.
concepts↗Galaxy's visualization framework ( 27 ) makes it possible to integrate a wide variety of Web-based and server-side visualizations. Through this framework, many new visualizations have been added to Galaxy, including Cytoscape ( 28 ), and the WebGL enabled 3D Protein viewer NGL ( 29 ), molecular interaction networks and macromolecular structures visualizations, and the 100+ visualizations available through BioJS ( 30 ), a rich set of community-driven JavaScript components for agile and interactive visualization of biological data.
User interface and experience enhancements
concepts↗concepts↗concepts↗unhoused_relationsThere are two common modes of data analysis: exploratory and pipeline execution. Galaxy enables simultaneous access to both of these. Users are able to interactively analyze their data by making use of individual tools in a trial-and-error manner. They are then able to automatically generate reusable and generalizable workflows from an ad hoc analysis. An interactive workflow editor is also available to modify or generate workflows from scratch. At any point in time, a user can seamlessly switch modes between interactively analyzing datasets and executing a workflow on these datasets. There is no analysis lock-in, and users can exercise full control, or make use of pre-existing pipelines. Importantly, these analysis artefacts, such as datasets, analysis histories, workflows, and visualizations can all be shared and copied by collaborators at the discretion of the analyst.
Client-side infrastructure
concepts↗concepts↗concepts↗unhoused_relationsconcept_edgesThe client-side of Galaxy, which is the user-interface most people associate with Galaxy, has seen significant changes under the hood. The usage of server-side mako templates, for example to create forms, has been further reduced and replaced by client-side only code that communicates via the RESTful Galaxy API with the backend. This minimizes the number of full-page refreshes and improves response time by enabling partial page updates. The interface has been further enhanced to allow for drag-and-drop of files and datasets, presents a fuzzy search on dataset and tool metadata, and implements a modal scratchbook for visualizations and comparison of multiple datasets.
concepts↗Furthermore, the community has selected the Vue.js framework ( https://vuejs.org/ ) as the base for future improvements allowing all UI elements to converge into a more reactive and future-proof interface. With the integration of Vue.js, the entire client-side build system was updated to utilize the latest web-technologies, to make routing and loading times faster, and to encourage rapid future interface improvements. While mostly transparent to users, these changes are the fundamental groundwork of a much more flexible UI framework that will enable visual enhancements and an improved user experience for years to come.
Tags
mechanisms↗limitationsconcepts↗concepts↗concepts↗unhoused_relationsunhoused_relationssensesconcept_edgesAlthough tags have been supported in Galaxy for several years, they have only recently become advantageous for large many-sample analyses. We have enhanced tags to allow propagation through dataset analysis steps. This facilitates tracking individual datasets through the entire analysis life-cycle and becomes part of the provenance system and ease-of-use of Galaxy. To enable automatic tag propagation, a hash-sign (#) is placed at the beginning of the tag, which is colloquially referred to as a named-tag. While standard Galaxy output dataset naming is suitable for many interactive analyses, the connection between inputs and outputs through large workflows becomes increasingly less obvious; by utilizing named-tags, users can label datasets with an identifier that is maintained throughout the analysis.
Webhooks
concepts↗concepts↗unhoused_relationsInspired by user feedback and the need to quickly modify and adapt Galaxy's interface, we integrated a pluggable system to extend Galaxy's frontend. Webhooks provide an entry-point into the Galaxy UI, in which it is possible to add buttons, menu entries, or entire iframes. At these entry-points a developer can dynamically add client-side code (JavaScript, HTML, CSS) and interact with the rest of the Galaxy user-interface. By integrating Webhooks with the Galaxy API, it is also possible to trigger server-side functions from within a Webhook. Webhooks can be thoroughly customized and are enabled at the discretion of the Galaxy administrator.
Interactive tours
concepts↗concepts↗unhoused_relationsWe have developed self-paced, interactive tours that users can step through to learn about Galaxy. These tours guide users step by step through using the interface including tools, workflows, and other features available in Galaxy. To simplify tour creation, a Tour Builder ( https://github.com/TailorDev/galaxy-tourbuilder ) has been created for recording, replaying, updating and exporting tours.
Improved workflows
limitationsconcepts↗claim_relationsGalaxy workflows have been extended in several ways. Switching between tool versions and upgrading workflows with new tool versions is now supported. A workflow can now be embedded in another, making it easier to create and edit workflows that have many common steps repeated. Many of these features have existed in in standalone workflow systems, such as Taverna ( 31 ), for sometime, but have been widely requested by Galaxy users. Workflows are now scheduled by a Galaxy server more efficiently and in the background, making it possible to execute larger workflows, generating tens of thousands of jobs, while providing instant feedback and a snappier user-experience. We have also enhanced Galaxy with initial support for running workflows defined in the Common Workflow Language ( 32 ) format.
Dataset collections
mechanisms↗concepts↗concepts↗unhoused_relationssensesGalaxy Dataset Collections combine datasets to enable simultaneous analysis. They organize sets of datasets as potentially nested lists of objects allowing easier data handling and batch execution of tools. In addition to the related frontend improvements, and support of nesting collections together, we recently introduced specialized tools to be executed on collections (e.g. Collapse , which combines a list of datasets into a single dataset, Flatten which takes nested collections and produces a flat list of datasets, and Merge which takes two lists and creates a single unified list), and enabled uploading and downloading dataset collections to and from both user's local disk and Galaxy data libraries.
Infrastructure enhancements
limitationsconcepts↗unhoused_relationsIn order to make Galaxy more robust in a production environment, we adopted technologies to enhance Galaxy's portability, security, reliability, and scalability. Galaxy now utilizes uWSGI ( http://projects.unbit.it/uwsgi ) as its default web application server. This adoption has several advantages, namely the ability to negate Python's limitations regarding concurrent tasks execution, built-in load balancing, scalability, improved fault tolerance and the possibility of restarting Galaxy uninterruptedly.
mechanisms↗limitationsconcepts↗unhoused_relationsMany tools available via Galaxy rely on the availability of reference and index data. To promote ease of use and efficient storage and compute resources, Galaxy is able to share a precomputed set of local reference data for tools to use. Previously, making this data available to the tools was a time intensive process where a Galaxy administrator had to install and properly configure the server, either manually or by using Data Managers ( 33 ). However, this resulted in much redundant effort required for each Galaxy server being configured. To streamline this process, we have made all the reference data we prepared for Galaxy Main available via a CernVM File System (CVMFS; ( 34 )), a scalable and content-addressable file system. This repository currently hosts 5TB of pre-build reference data, which are versioned and shared publicly with read-only access. With minimal configuration, any instance of Galaxy, including Galaxy-Docker images, can attach to this file system and gain access to the same reference data available on Galaxy Main. To improve accessibility and fault-tolerance, this data source is replicated on servers located in Europe and Australia.
mechanisms↗concepts↗concepts↗concepts↗concepts↗concepts↗concepts↗unhoused_relationsunhoused_relationsclaim_relationsGalaxy is powered by various open-source projects which are installed automatically, and used when needed. Galaxy is using the Conda package manager ( https://conda.io ) as its default tool dependency resolver, and offers support for virtualization and containerization technologies (e.g. Docker ( https://www.docker.com ) and Singularity ( 35 )) to ensure a higher level of portability, if needed. By leveraging the Bioconda ( https://doi.org/10.1101/207092 ) and the BioContainer ( 36 ) projects, Galaxy is able to provision and use reproducible tool execution environments (( 37 ); https://doi.org/10.1101/200683 ).
concepts↗unhoused_relationsGalaxy is a generic data analysis framework, which can be configured for various application scenarios using a wide range of configuration parameters. To facilitate configuring these parameters with optimal values for a number of predefined application scenarios, the Galaxy project leverages Ansible ( https://www.ansible.com ), software for automated configuration and management of other software packages. We have developed and shared Ansible configurations for Galaxy Main , the main public Galaxy server, ( https://github.com/galaxyproject/usegalaxy-playbook ) and also a configurable generic playbook for setting up production instances on cloud resources, virtual machines, and bare metal ( https://github.com/ARTbio/GalaxyKickStart ). This playbook can be used as a reference for configuring a Galaxy instance for a production environment.
concepts↗concepts↗unhoused_relationssensesThe Galaxy-Docker project ( https://github.com/bgruening/docker-galaxy-stable ), delivers a production ready Galaxy instance in minutes and can be used as the basis for personalized, self-contained, portable instances of Galaxy, known as Galaxy flavors. Preconfigured by the Galaxy community, a plenitude of flavors already exist covering application scenarios, from BLAST+ ( 38 , 39 ), metagenomics ( https://doi.org/10.1101/183970 ), ChIP-exo analysis, or RNA research ( 40 ). In addition to the facilitated and out-of-box functionality, these images provision isolated environments well-suited for experimenting with tools and Galaxy configurations, and are ideal for training courses, as demonstrated by the Galaxy Training Network.
concepts↗unhoused_relationsServer monitoring and issue management is crucial in production Galaxy instances. Galaxy has integrated a plugin module to submit user bug-reports to configurable endpoints such as mailing lists or GitHub issues. With this, Galaxy can be configured to send error reports to a local ticket system. The recent integration of Sentry ( https://sentry.io/ ) for automated error tracking and reporting makes it easier for administrators to track both client- and server-side errors without requiring manual user bug reports.
COMMUNITY
mechanisms↗concepts↗concepts↗unhoused_relationsclaim_relationsGalaxy serves several distinct communities: researchers, tool developers, resource providers, trainers, and trainees. To centralize resources for all communities, we have developed the Galaxy Community Hub ( https://galaxyproject.org ) for all things Galaxy. The Hub uses a modified wiki approach, with content written in Markdown, a simple formatting language, and then built into a static website. Anyone can update the Markdown documents using GitHub pull requests, a standard approach for collaborating on code and documentation on GitHub projects. Submitted pull requests are reviewed and merged, and the Hub site is automatically regenerated and updated, resulting in high-quality reviewed content that can be updated by any member of the Galaxy community. The Hub includes a full list of public Galaxy servers ( https://galaxyproject.org/public-galaxy-servers ), a large set of tutorials for learning to use Galaxy and perform genomic analyses, extensive documentation on deploying and administering a Galaxy server in the Cloud or on local hardware, and upcoming events. We also maintain an annotated listing of the >5000 publications referencing Galaxy via the free and open-source Zotero service ( https://www.zotero.org/groups/1732893/galaxy ).
concepts↗concepts↗concepts↗unhoused_relationsunhoused_relationsThe Main Galaxy server has over 124 000 registered users and ∼2000 new users register each month. On average, 20 000 unique users execute over 245 000 analysis jobs by accessing 750 different tools every month. With such an active user-base, questions on platform and tool usage, as well as general research questions ( 41 ), are common. To efficiently assist users in performing research, we provide a Biostars ( 42 ) Question and Answers forum ( https://biostar.usegalaxy.org/ ) that leverages the knowledge and strength of community members to provide support. This forum is monitored and moderated by core team members, but the Galaxy user community provides many answers. Help is also available through live chat with the team and community members via Gitter and IRC chat services, which are used most often by developers and administrators. In addition to the online help and documentation, the Galaxy Training Network has developed comprehensive tutorials and workflows for performing common data analysis tasks, providing topic-specific introduction slides, hands-on material, sample data, and even playable Galaxy tours ( https://doi.org/10.1101/225680 ).
Many in-person events that highlight and build the Galaxy community occur each year ( https://galaxyproject.org/events/ ). These include free or low-cost hands-on workshops and training sessions that have been hosted by the community on six continents. The Galaxy Community Conference (GCC) is an annual conference that was first held in 2010. GCC alternates between Europe and the United States, includes two full days of training, two days of coding and data analysis hackathons, and two days of oral and poster presentations. Galaxy conferences have had over two hundred attendees each year since 2012, and over eleven hundred different researchers have attended since 2010. Our 2018 conference will be hosted jointly with the Bioinformatics Open Source Conference (BOSC) in an effort to promote and centralize discussion of open-source software for bioinformatics.
concepts↗concepts↗unhoused_relationssensesAnother core area of community focus is tool development and availability. The Intergalactic Utilities Commission (IUC; https://galaxyproject.org/iuc/ ) is a community-based organization that defines best-practices for tool development that help ensure the availability of high-quality tools in the ToolShed. It is a self-organizing and self-regulating group that has grown by six new members in the last two years and is primarily composed of individuals outside of the core Galaxy development team. The IUC is only one of many tool contributors, with the ToolShed allowing any member of the community to share tools that they have added to Galaxy. To assist community members with tool development and distribution, a command-line tool named Planemo ( https://github.com/galaxyproject/planemo ) has been developed. Planemo provides functionality for verifying best-practice adherence, testing, installation and uploading of tools to the ToolShed.
mechanisms↗limitationsconcepts↗concepts↗concepts↗concepts↗unhoused_relationsclaim_relationsclaim_relationsCommunity contributions have helped the Galaxy framework and its tool suite to grow considerably. One hundred and seventy-four developers, who have collectively produced 13 135 commits within just the past two years (63% increase since January 2016), have improved Galaxy's scalability, functionality, and usability. The project utilizes the Travis and Jenkins continuous integration (CI) services to automatically execute comprehensive test suites on each set of proposed code changes. This strategy helps prevent the introduction of bugs to the codebase and improves review time. By harnessing the open-source community and modern software development practices, we are able to release a new stable version of the Galaxy framework every four months. Current future directions include enabling data and compute federation; tighter coupling of Interactive Environments with provenance and reuse; ToolShed installation and development enhancements; continued work on collections, workflows, analysis interfaces and history views; additional training material; improving statistical usage tracking and instrumentation; and much more. For anyone interested in getting involved with Galaxy development, we invite them to read the project's Contributing and Code of Conduct documents, review open issues, and explore the current roadmap, all which are available from the Galaxy GitHub repository ( https://github.com/galaxyproject/galaxy/ ).
ACKNOWLEDGEMENTS
The Galaxy Project has grown in large part thanks to the contributions of time and effort by numerous individuals over the years. Contributing individuals include members of the Galaxy user, developer and administrative communities and organizers of Galaxy Community Conferences. We are indebted to these helpful people. The Public Galaxy site is located at the Texas Advanced Computing Center (TACC at the University of Texas). We are extremely grateful to both TACC and CyVerse for enabling Galaxy to serve thousands of researchers worldwide.
FUNDING
National Human Genome Research Institute, National Institutes of Health [HG006620, HG005133, HG004909 and HG005542]; NSF [DBI 0543285, 0850103 and 1661497]; Huck Institutes for the Life Sciences at Penn State; and, in part, under a grant with the Pennsylvania Department of Health using Tobacco Settlement Funds, the Department specifically disclaims responsibility for any analyses, interpretations or conclusions. Funding for open access charge: Cleveland Clinic.
Conflict of interest statement . None declared.
REFERENCES
Relations on this page carry a quotation for the claim. Where a relation was separately evidenced — and so tested against the vocabulary for its type — the row says so; 5 of 5 relations here carry that mark. The rest are the tagger’s reading of the sentence quoted beside them.
This record holds no controls. A layer is empty when the tagger recorded nothing in it — which is not the same as the paper having nothing to record.
| facet | tag | field | conf. | whose words |
|---|---|---|---|---|
| object_of_study | the 2018 architecture, scalability, tools, interfaces, workflows, infrastructure, and communities of the Galaxy biomedical-analysis platform | object_of_study | the paper's words | |
| research_question | how Galaxy evolved to make increasingly large biomedical analyses accessible, reproducible, scalable, shareable, and extensible | research_question | the paper's words | |
| contribution | reports and organizes two years of Galaxy improvements across frontend and backend scalability, tools, workflows, interactive environments, deployment, reference data, training, and community development | contribution | the paper's words | |
| claim_type | existence | claim_type | the paper's words | |
| phenomenon | the growth of large biomedical datasets and communities beyond the scale manageable by earlier analysis interfaces and server infrastructure | phenomenon | the paper's words | |
| method | system-or-tool-building also in: system-or-tool-building | method | the paper's words | |
| mechanisms | mechanisms | mechanisms[0] | 0.99 | the tagger's words |
| mechanisms | mechanisms | mechanisms[1] | 0.99 | the tagger's words |
| mechanisms | mechanisms | mechanisms[2] | 0.99 | the tagger's words |
| mechanisms | mechanisms | mechanisms[3] | 0.99 | the tagger's words |
| mechanisms | mechanisms | mechanisms[4] | 0.99 | the tagger's words |
| mechanisms | mechanisms | mechanisms[5] | 0.99 | the tagger's words |
| mechanisms | mechanisms | mechanisms[6] | 0.99 | the tagger's words |
| mechanisms | mechanisms | mechanisms[7] | 0.99 | the tagger's words |
| mechanisms | mechanisms | mechanisms[8] | 0.99 | the tagger's words |
| mechanisms | mechanisms | mechanisms[9] | 0.99 | the tagger's words |
| mechanisms | mechanisms | mechanisms[10] | 0.99 | the tagger's words |
| mechanisms | mechanisms | mechanisms[11] | 0.99 | the tagger's words |
| limitations | Galaxy must scale both its browser interface and backend server under growing dataset size, dataset count, and multiuser demand | limitations[0] | 0.99 | the tagger's words |
| limitations | earlier Galaxy versions could not support the demonstrated 11,872-history-item single-cell analysis | limitations[1] | 0.99 | the tagger's words |
| limitations | interactive environments require execution isolation because arbitrary scripting raises security concerns | limitations[2] | 0.99 | the tagger's words |
| limitations | cloud deployments otherwise require provider-specific machine images and file systems to be built and maintained | limitations[3] | 0.99 | the tagger's words |
| limitations | complete genomic analyses often still require custom scripts or visualizations at preparation or summarization stages | limitations[4] | 0.99 | the tagger's words |
| limitations | input-output connections become less obvious in large workflows without persistent tag propagation | limitations[5] | 0.99 | the tagger's words |
| limitations | workflow versioning, nesting, efficient background scheduling, and external-format support were recent or initial capabilities | limitations[6] | 0.98 | the tagger's words |
| limitations | manually installing and configuring reference data on every Galaxy server created time-intensive redundant effort | limitations[7] | 0.99 | the tagger's words |
| limitations | production instances need explicit portability, security, reliability, scalability, monitoring, and issue-management infrastructure | limitations[8] | 0.99 | the tagger's words |
| limitations | core future work remained in federation, provenance coupling, ToolShed development, collections, workflows, interfaces, training, and instrumentation | limitations[9] | 0.99 | the tagger's words |
| concepts | Galaxy also in: Galaxy | concepts[0] | 0.99 | the paper's words |
| concepts | web-based scientific analysis platform | concepts[1] | 0.99 | the paper's words |
| concepts | large biomedical datasets also in: large biomedical datasets | concepts[2] | 0.99 | the paper's words |
| concepts | data-driven biomedical science also in: data-driven biomedical science | concepts[3] | 0.99 | the paper's words |
| concepts | accessible data analysis also in: accessible data analysis | concepts[4] | 0.99 | the paper's words |
| concepts | reproducible analyses also in: reproducible analyses | concepts[5] | 0.99 | the paper's words |
| concepts | transparent communication also in: transparent communication | concepts[6] | 0.99 | the paper's words |
| concepts | Galaxy Project about this quote: THE QUOTE ENDS ON A COLON: the paper goes on with the four components of the Galaxy Project, one paragraph each, too long to quote here; what this row states is in that list, not in the quoted words. also in: Galaxy Project | concepts[7] | 0.99 | the paper's words |
| concepts | four complementary components about this quote: THE QUOTE ENDS ON A COLON: the paper goes on with the four components of the Galaxy Project, one paragraph each, too long to quote here; what this row states is in that list, not in the quoted words. also in: four complementary components | concepts[8] | 0.99 | the paper's words |
| concepts | main public Galaxy server also in: main public Galaxy server | concepts[9] | 0.99 | the paper's words |
| concepts | Galaxy framework and software ecosystem | concepts[10] | 0.99 | the paper's words |
| concepts | software development kit also in: software development kit | concepts[11] | 0.99 | the paper's words |
| concepts | API language bindings also in: API language bindings | concepts[12] | 0.99 | the paper's words |
| concepts | Galaxy ToolShed also in: Galaxy ToolShed | concepts[13] | 0.99 | the paper's words |
| concepts | AppStore also in: AppStore | concepts[14] | 0.99 | the paper's words |
| concepts | Galaxy Community also in: Galaxy Community | concepts[15] | 0.99 | the paper's words |
| concepts | user community also in: user community | concepts[16] | 0.99 | the paper's words |
| concepts | scalability also in: scalability | concepts[17] | 0.99 | the paper's words |
| concepts | User interface scalability also in: User interface scalability | concepts[18] | 0.99 | the paper's words |
| concepts | Server scalability also in: Server scalability | concepts[19] | 0.99 | the paper's words |
| concepts | earlier versions of Galaxy also in: earlier versions of Galaxy | concepts[20] | 0.99 | the paper's words |
| concepts | workflows also in: workflows | concepts[21] | 0.99 | the paper's words |
| concepts | collections also in: collections | concepts[22] | 0.99 | the paper's words |
| concepts | jobs also in: jobs | concepts[23] | 0.99 | the paper's words |
| concepts | workload managers also in: workload managers | concepts[24] | 0.99 | the paper's words |
| concepts | dynamic job destination assignment also in: dynamic job destination assignment | concepts[25] | 0.99 | the paper's words |
| concepts | Galaxy Main also in: Galaxy Main | concepts[26] | 0.99 | the paper's words |
| concepts | XSEDE infrastructure also in: XSEDE infrastructure | concepts[27] | 0.99 | the paper's words |
| concepts | Jetstream cloud also in: Jetstream cloud | concepts[28] | 0.99 | the paper's words |
| concepts | containerization technologies also in: containerization technologies | concepts[29] | 0.99 | the paper's words |
| concepts | Galaxy Interactive Environments also in: Galaxy Interactive Environments | concepts[30] | 0.99 | the paper's words |
| concepts | CloudBridge also in: CloudBridge | concepts[31] | 0.99 | the paper's words |
| concepts | CloudLaunch also in: CloudLaunch | concepts[32] | 0.99 | the paper's words |
| concepts | tool profile version also in: tool profile version | concepts[33] | 0.99 | the paper's words |
| concepts | Galaxy API also in: Galaxy API | concepts[34] | 0.99 | the paper's words |
| concepts | Jupyter also in: Jupyter | concepts[35] | 0.99 | the paper's words |
| concepts | RStudio also in: RStudio | concepts[36] | 0.99 | the paper's words |
| concepts | visualization framework also in: visualization framework | concepts[37] | 0.99 | the paper's words |
| concepts | exploratory also in: exploratory | concepts[38] | 0.99 | the paper's words |
| concepts | pipeline execution also in: pipeline execution | concepts[39] | 0.99 | the paper's words |
| concepts | RESTful Galaxy API also in: RESTful Galaxy API | concepts[40] | 0.99 | the paper's words |
| concepts | client-side code also in: client-side code | concepts[41] | 0.99 | the paper's words |
| concepts | response time also in: response time | concepts[42] | 0.99 | the paper's words |
| concepts | Vue.js also in: Vue.js | concepts[43] | 0.99 | the paper's words |
| concepts | tags also in: tags | concepts[44] | 0.99 | the paper's words |
| concepts | named-tag also in: named-tag | concepts[45] | 0.99 | the paper's words |
| concepts | provenance system also in: provenance system | concepts[46] | 0.99 | the paper's words |
| concepts | Webhooks also in: Webhooks | concepts[47] | 0.99 | the paper's words |
| concepts | interactive tours also in: interactive tours | concepts[48] | 0.99 | the paper's words |
| concepts | Tour Builder also in: Tour Builder | concepts[49] | 0.99 | the paper's words |
| concepts | Common Workflow Language also in: Common Workflow Language | concepts[50] | 0.99 | the paper's words |
| concepts | Galaxy Dataset Collections also in: Galaxy Dataset Collections | concepts[51] | 0.99 | the paper's words |
| concepts | uWSGI also in: uWSGI | concepts[52] | 0.99 | the paper's words |
| concepts | CernVM File System also in: CernVM File System | concepts[53] | 0.99 | the paper's words |
| concepts | Conda package manager also in: Conda package manager | concepts[54] | 0.99 | the paper's words |
| concepts | Docker also in: Docker | concepts[55] | 0.99 | the paper's words |
| concepts | Singularity also in: Singularity | concepts[56] | 0.99 | the paper's words |
| concepts | Bioconda also in: Bioconda | concepts[57] | 0.99 | the paper's words |
| concepts | BioContainer also in: BioContainer | concepts[58] | 0.99 | the paper's words |
| concepts | reproducible tool execution environments | concepts[59] | 0.99 | the paper's words |
| concepts | Ansible also in: Ansible | concepts[60] | 0.99 | the paper's words |
| concepts | Galaxy-Docker also in: Galaxy-Docker | concepts[61] | 0.99 | the paper's words |
| concepts | Galaxy flavors also in: Galaxy flavors | concepts[62] | 0.99 | the paper's words |
| concepts | Sentry also in: Sentry | concepts[63] | 0.99 | the paper's words |
| concepts | Galaxy Community Hub also in: Galaxy Community Hub | concepts[64] | 0.99 | the paper's words |
| concepts | Markdown also in: Markdown | concepts[65] | 0.99 | the paper's words |
| concepts | Biostars also in: Biostars | concepts[66] | 0.99 | the paper's words |
| concepts | Galaxy Training Network also in: Galaxy Training Network | concepts[67] | 0.99 | the paper's words |
| concepts | Intergalactic Utilities Commission also in: Intergalactic Utilities Commission | concepts[68] | 0.99 | the paper's words |
| concepts | Planemo also in: Planemo | concepts[69] | 0.99 | the paper's words |
| concepts | continuous integration also in: continuous integration | concepts[70] | 0.99 | the paper's words |
| concepts | codebase also in: codebase | concepts[71] | 0.99 | the paper's words |
| concepts | Travis also in: Travis | concepts[72] | 0.99 | the paper's words |
| concepts | Jenkins also in: Jenkins | concepts[73] | 0.99 | the paper's words |
| unhoused_relations | Galaxy Project → four complementary components The Galaxy Project consists of four complementary components. — about this quote: THE QUOTE ENDS ON A COLON: the paper goes on with the four components of the Galaxy Project, one paragraph each, too long to quote here; what this row states is in that list, not in the quoted words. | unhoused_relations[0] | 0.99 | the tagger's words |
| unhoused_relations | named-tag → tags A hash-prefixed tag is referred to as a named-tag. | unhoused_relations[1] | 0.99 | the tagger's words |
| unhoused_relations | Galaxy → data-driven biomedical science Galaxy enables data-driven biomedical science through accessible, reproducible, transparent analysis. | unhoused_relations[2] | 0.99 | the tagger's words |
| unhoused_relations | Galaxy flavors → Galaxy-Docker Galaxy-Docker delivers personalized portable instances known as Galaxy flavors. | unhoused_relations[3] | 0.99 | the tagger's words |
| unhoused_relations | Biostars → Galaxy Community The Galaxy user community provides many answers through the monitored Biostars forum. | unhoused_relations[4] | 0.99 | the tagger's words |
| unhoused_relations | RESTful Galaxy API → Galaxy API The client-side RESTful Galaxy API and the Webhook-facing Galaxy API refer to the platform's programmatic interface. | unhoused_relations[5] | 0.98 | the tagger's words |
| unhoused_relations | Galaxy framework and software ecosystem → software development kit The Galaxy ecosystem includes a software development kit for tool development. | unhoused_relations[6] | 0.99 | the tagger's words |
| unhoused_relations | Galaxy ToolShed → AppStore The Galaxy ToolShed assumes the role of an AppStore for Galaxy instances. | unhoused_relations[7] | 0.99 | the tagger's words |
| unhoused_relations | scalability → large biomedical datasets Growing biomedical dataset size and number create a scalability challenge for Galaxy. | unhoused_relations[8] | 0.99 | the tagger's words |
| unhoused_relations | workflows → User interface scalability Workflows and collections facilitate analysis of large numbers of datasets. | unhoused_relations[9] | 0.99 | the tagger's words |
| unhoused_relations | dynamic job destination assignment → Server scalability Dynamic job destination assignment chooses resources based on job parameters. | unhoused_relations[10] | 0.99 | the tagger's words |
| unhoused_relations | XSEDE infrastructure → jobs Specialized national resources enable Galaxy Main to execute larger jobs. | unhoused_relations[11] | 0.99 | the tagger's words |
| unhoused_relations | Jetstream cloud → Galaxy Interactive Environments Jetstream virtualization enables isolated interactive environments. | unhoused_relations[12] | 0.99 | the tagger's words |
| unhoused_relations | CloudBridge → CloudLaunch CloudBridge and CloudLaunch jointly launch Galaxy across providers while reducing provider-specific maintenance. | unhoused_relations[13] | 0.99 | the tagger's words |
| unhoused_relations | tool profile version → earlier versions of Galaxy Tool profile versions preserve backward compatibility while defaults and behavior evolve. | unhoused_relations[14] | 0.99 | the tagger's words |
| unhoused_relations | Galaxy Interactive Environments → Jupyter Interactive Environments integrate Galaxy with Jupyter. | unhoused_relations[15] | 0.99 | the tagger's words |
| unhoused_relations | exploratory → pipeline execution Users can switch seamlessly between exploratory analysis and workflow execution. | unhoused_relations[16] | 0.99 | the tagger's words |
| unhoused_relations | named-tag → workflows Named-tags maintain dataset identifiers throughout large workflows. | unhoused_relations[17] | 0.99 | the tagger's words |
| unhoused_relations | Webhooks → Galaxy API Webhooks use the Galaxy API to trigger server-side functions from frontend extensions. | unhoused_relations[18] | 0.99 | the tagger's words |
| unhoused_relations | Tour Builder → interactive tours Tour Builder records, replays, updates, and exports interactive tours. | unhoused_relations[19] | 0.99 | the tagger's words |
| unhoused_relations | Galaxy Dataset Collections → collections Galaxy Dataset Collections organize potentially nested sets for simultaneous analysis. | unhoused_relations[20] | 0.99 | the tagger's words |
| unhoused_relations | uWSGI → scalability uWSGI improves production scalability, load balancing, fault tolerance, and uninterrupted restarts. | unhoused_relations[21] | 0.99 | the tagger's words |
| unhoused_relations | CernVM File System → Galaxy Main CVMFS shares versioned reference data from Galaxy Main with other instances. | unhoused_relations[22] | 0.99 | the tagger's words |
| unhoused_relations | Conda package manager → reproducible tool execution environments Conda resolves dependencies used in reproducible Galaxy tool environments. | unhoused_relations[23] | 0.99 | the tagger's words |
| unhoused_relations | Docker → reproducible tool execution environments Docker provides isolated portable tool environments. | unhoused_relations[24] | 0.99 | the tagger's words |
| unhoused_relations | Ansible → Galaxy Main Ansible configurations automate production deployment of Galaxy instances. | unhoused_relations[25] | 0.99 | the tagger's words |
| unhoused_relations | Sentry → continuous integration Sentry tracks runtime errors while continuous integration tests proposed code changes. | unhoused_relations[26] | 0.98 | the tagger's words |
| unhoused_relations | Markdown → Galaxy Community Hub Markdown pull requests are reviewed and regenerate the static Community Hub. | unhoused_relations[27] | 0.99 | the tagger's words |
| unhoused_relations | Biostars → user community The user community supplies many answers on the monitored Biostars forum. | unhoused_relations[28] | 0.99 | the tagger's words |
| unhoused_relations | Planemo → Galaxy ToolShed Planemo tests, installs, and uploads community tools to the ToolShed. | unhoused_relations[29] | 0.99 | the tagger's words |
| unhoused_relations | continuous integration → codebase Continuous integration helps prevent bugs from entering the codebase. | unhoused_relations[30] | 0.99 | the tagger's words |
| senses | Galaxy - a web platform unifying accessible analysis, reproducibility, communication, reuse, and extension | senses[0] | 0.99 | the tagger's words |
| senses | Galaxy Project - four complementary components: public server, open framework, ToolShed, and stakeholder community about this quote: THE QUOTE ENDS ON A COLON: the paper goes on with the four components of the Galaxy Project, one paragraph each, too long to quote here; what this row states is in that list, not in the quoted words. | senses[1] | 0.99 | the tagger's words |
| senses | User interface scalability - many-dataset interaction and pipeline design without overwhelming the web frontend | senses[2] | 0.99 | the tagger's words |
| senses | Server scalability - multiuser job execution across laptops, clusters, clouds, and national infrastructure | senses[3] | 0.99 | the tagger's words |
| senses | Galaxy ToolShed - an AppStore-like community exchange for installable Galaxy tools, workflows, and visualizations | senses[4] | 0.99 | the tagger's words |
| senses | Galaxy Interactive Environments - a combined graphical and ad hoc scripting mode using shared Galaxy infrastructure | senses[5] | 0.99 | the tagger's words |
| senses | named-tag - a hash-prefixed persistent dataset identifier propagated through the analysis lifecycle | senses[6] | 0.99 | the tagger's words |
| senses | Galaxy Dataset Collections - nested dataset containers supporting simultaneous analysis and batch execution | senses[7] | 0.99 | the tagger's words |
| senses | Galaxy flavors - personalized, preconfigured, self-contained, portable deployments built from Galaxy-Docker | senses[8] | 0.99 | the tagger's words |
| senses | Intergalactic Utilities Commission - a self-regulating community body defining and verifying high-quality ToolShed practices | senses[9] | 0.99 | the tagger's words |
| claim_relations | extends → Galaxy's framework, interface, tools, training, scalability, and communities since the prior update note: The paper is explicitly a feature and growth update. | claim_relations[0] | 0.99 | the tagger's words |
| claim_relations | supports → accessible, reproducible, transparent, reusable biomedical analysis note: The three goals are stated directly. | claim_relations[1] | 0.99 | the tagger's words |
| claim_relations | validates → frontend scalability on an 11,872-history-item single-cell workflow note: The authors describe a concrete benchmark against earlier versions. | claim_relations[2] | 0.99 | the tagger's words |
| claim_relations | demonstrates → larger and isolated jobs through national and cloud cyberinfrastructure note: The passage reports both increased job size and new interactive job types. | claim_relations[3] | 0.99 | the tagger's words |
| claim_relations | introduces → Galaxy Interactive Environments integrating graphical analysis and ad hoc scripting note: The article says the environments were recently introduced. | claim_relations[4] | 0.99 | the tagger's words |
| claim_relations | extends → workflows with nesting, background scheduling, version changes, and Common Workflow Language support note: The update enumerates these extensions. | claim_relations[5] | 0.99 | the tagger's words |
| claim_relations | supports → portable reproducible tool execution using Conda and container technologies note: The dependency and container stack is described directly. | claim_relations[6] | 0.99 | the tagger's words |
| claim_relations | builds-on → open-source projects and community-authored tools, documentation, and infrastructure note: The Hub and platform are maintained through reviewable community contributions. | claim_relations[7] | 0.99 | the tagger's words |
| claim_relations | validates → automated test execution as a protection against codebase regressions note: The development process runs comprehensive suites on every proposed change. | claim_relations[8] | 0.99 | the tagger's words |
| claim_relations | qualifies → Galaxy's current platform completeness note: The paper closes with a substantial list of future directions. | claim_relations[9] | 0.99 | the tagger's words |
| concept_edges | Galaxy —is-a→ web-based scientific analysis platform the relation itself is separately evidenced · strength of the relation: 1 · note: Direct categorical statement. · the relation stated: Galaxy is a web-based scientific analysis platform. also in: Galaxy · web-based scientific analysis platform | concept_edges[0] | 0.99 | the tagger's words |
| concept_edges | Galaxy —contrasted-with→ earlier versions of Galaxy the relation itself is separately evidenced · strength of the relation: 0.99 · note: Explicit whereas comparison. · the relation stated: The current Galaxy ran the many-item experiment seamlessly, whereas earlier versions could not support it. also in: Galaxy · earlier versions of Galaxy | concept_edges[1] | 0.99 | the tagger's words |
| concept_edges | named-tag —part-of→ provenance system the relation itself is separately evidenced · strength of the relation: 1 · note: Explicit part-of statement. · the relation stated: Named-tags become part of the Galaxy provenance system. also in: named-tag · provenance system | concept_edges[2] | 0.99 | the tagger's words |
| concept_edges | Galaxy —same-as→ Galaxy Project the relation itself is separately evidenced · strength of the relation: 0.95 · note: The introduction uses the names for the same project context. · the relation stated: Galaxy and the Galaxy Project name the platform and surrounding project discussed in the article. also in: Galaxy · Galaxy Project | concept_edges[3] | 0.98 | the tagger's words |
| concept_edges | client-side code —causes→ response time the relation itself is separately evidenced · strength of the relation: 0.95 · note: Flat positive effect with a stated mechanism. · the relation stated: Client-side code improves response time by enabling partial page updates.
Audit 2026-09-28: DOUBTFUL - read against its span and kept, but client-side code IMPROVES (shortens) response time; the edge lacks its direction. also in: client-side code · response time | concept_edges[5] | 0.99 | the tagger's words |
Tags that could not be placed in the text:
What was deliberately not tagged, and why, is recorded per paper by the tagger. Where a paper has no such record, this page says so rather than implying that nothing was declined.