15 research outputs found
Demographics registered usersā research area (A), occupation (B), and genders (C).
Demographics registered usersā research area (A), occupation (B), and genders (C).</p
Version control.
Public and private version control organizations on GitHub and GitLab for CyVerse Software, Public Container Registry, and Education. (PDF)</p
University of Arizona hardware.
On-premises resources maintained by CyVerse at the University of Arizona. DE = Discovery Environment, VICE = Virtual Interactive Compute Environment. (PDF)</p
Publications.
Peer-reviewed research citing the use of resources from the iPlant Collaborative (2008ā2017) and CyVerse (2017-Present). Also see https://cyverse.org/publications for the latest update. (PDF)</p
Workshop and webinar participants.
In-person and Virtual Workshops and total enrollees, Virtual Webinars given and participants who RSVPād.</p
Description of CyVerse core & cloud services.
Additional details about CyVerse featured platforms, core services, and cloud native services. Basemaps from Carto and OpenStreetMap CC-BY 4.0 license, (https://github.com/CartoDB/basemap-styles). (PDF)</p
Multiplier effects.
Only 25% of NSF awards which requested Letters of Collaboration (LOCs) mention āCyVerseā or āiPlant Collaborativeā in their public abstract. Of the total awards that mention āCyVerseā or āiPlant Collaborativeā 73% did not request LOCs.</p
Resources designed for scientists.
CyVerse offers researchers diverse compute, storage, and event-based workflow options. Data and associated metadata are uploaded and managed in an iRODS Data Store, accessible through various transfer protocols. CyVerse delivers moderate computing power for analytical research via its Discovery Environment data science workbench and connects to public and commercial cloud through the Cloud Automation and Continuous Analysis Orchestration (CACAO) platform. Researchers can register and activate workflows in CyVerse using event-based triggers through the Data Watch API.</p