Difference between revisions of "ERSAP"

From epsciwiki
Jump to navigation Jump to search
Line 31: Line 31:
 
</table>
 
</table>
 
<br><hr><br>
 
<br><hr><br>
<div class="orbitron"><font size="+1">Presentations/Papers</font></div>Presentations/Papers
+
<div class="orbitron"><font size="+1">Presentations/Papers</font></div>
  
 
{| class="wikitable"
 
{| class="wikitable"

Revision as of 14:33, 6 December 2021

Welcome to the ERSAP Wiki

(Environment for Real-time Streaming, Acquisition and Processing)



System Overview:

ERSAP is a reactive actor/micro-service based data-stream processing framework, a hardware/software system that is capable of processing unbounded streams of continuous data at scale over distributed heterogeneous resources in real-time. The goal of ERSAP is to design a framework that will provide a flexible environment to design and, most importantly, allow future evolution of the data processing applications. An environment that will encourage implementation of new ideas and new technologies while preserving integrity of existing data processing pipelines. ERSAP encourages to perform functional decomposition of the overall data processing application into small, mono-functional artifacts/actors. Artifacts that are easy to understand, develop, deploy and debug. The fact that these artifacts/actors are programmatically independent, they can be scaled and optimized independently, which is impossible to do for components of the monolithic application. One of the important advantages is the ERSAP fault tolerance, where independent actors can come and go on the stream without forcing entire application to crash, and it is easy to locate the faulty actor in the chain. Due the fact that the actors are loosely coupled, and that the message (the only coupling between actors) carries the context, they can run on heterogenous environments with different memory and/or processing power requirements. The active actors can be physically separated from each other, so the deployment of a new set of actors does not put the whole system on hold, and the updates are less intrusive. The development of the actors and actor engines handling specific areas of the system can be performed by independent development teams, with their own release cycles and with it's own pace. The ERSAP is not a ground up design. It is based on our experience of micro-service based, off-line data processing applications that are running more than a decade in CLAS12, and CODA distributed, triggered based DAQ that is running more than quarter of a century at the JLAB. Also, it will be utilizing JANA framework to develop high performance data processing engines.

Projects Meetings




Presentations/Papers
date presenter Event links
2021-12-01 T. Jeske ACAT2021 (PDF PPTX)
2021-11-30 D. Lawrence DOE Nuclear Physics PI Exchange Meeting (slides)
2021-11-17 N. Jarvis GlueX Production & Analysis Meeting (slides)
2021-11-05 T. Britton Canisius College Seminar (slides, PDF)
2021-10-07 N. Jarvis IOP NPG Colloquium (slides)
2021-09-09 T. Jeske AI4EIC Workshop (slides)
2021-07-26 T. Jeske JLab A.I. Town Hall (slides)
2021-06-30 T. Jeske GlueX Production & Analysis Meeting (slides)