Abstract

The Visual Physics Analysis (VISPA) project defines a toolbox for accessing software via the web. It is based on latest web technologies and provides a powerful extension mechanism that enables to interface a wide range of applications. Beyond basic applications such as a code editor, a file browser, or a terminal, it meets the demands of sophisticated experiment-specific use cases that focus on physics data analyses and typically require a high degree of interactivity. As an example, we developed a data inspector that is capable of browsing interactively through event content of several data formats, e.g., MiniAOD which is utilized by the CMS collaboration. The VISPA extension mechanism can also be used to embed external web-based applications that benefit from dynamic allocation of user-defined computing resources via SSH. For example, by wrapping the JSROOT project, ROOT files located on any remote machine can be inspected directly through a VISPA server instance. We introduced domains that combine groups of users and role-based permissions. Thereby, tailored projects are enabled, e.g. for teaching where access to student’s homework is restricted to a team of tutors, or for experiment-specific data that may only be accessible for members of the collaboration. We present the extension mechanism including corresponding applications and give an outlook onto the new permission system.

Highlights

  • Scientific workflows can strongly benefit from the advantages of web applications

  • The Visual Physics Analysis (VISPA) project provides an ecosystem for experiment-specific software

  • The event content of high-energy physics (HEP) data files can be interactively visualized with the Data Browser

Read more

Summary

Introduction

Scientific workflows can strongly benefit from the advantages of web applications. Especially location-independent access via web browsers and centralized software installation on dedicated servers are convincing arguments. Extensions are installed on the host running the VISPA server instance and are typically available for every user who has access to the server They are composed of three parts: code and graphics components that extend the client (JavaScript/HTML/CSS), code that handles the communication on the server (Python), and, optionally, code that is transferred to and executed on workspaces (Python). The purpose of the latter part is to outsource and encapsulate actual extension logic causing the server to take on the role of a mediator between requests and resources. Based on the nonrestrictive design of PXL objects as outlined above, event content stored in other data formats is convertible to pxlio and visualizable by the extension

Embedding External Functionality
Conclusions
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call