Difference between revisions of "EJFAT EPSCI Meeting Jan. 18, 2023"

From epsciwiki
Jump to navigation Jump to search
(Created page with "The meeting time is 2:30pm. === Connection Info: === <div class="toccolours mw-collapsible mw-collapsed"> You can connect using [https://teams.microsoft.com/l/meetup-join/19%...")
 
Line 35: Line 35:
 
# New Test set-up: GAP
 
# New Test set-up: GAP
 
## CP [https://itnext.io/streaming-data-with-grpc-2eb983fdee11 gRPC] i/f to RE PID:
 
## CP [https://itnext.io/streaming-data-with-grpc-2eb983fdee11 gRPC] i/f to RE PID:
### Polling: Implies RE Server, CP Client
+
### '''Asynchronous Peer Coupled'''
 
### Server-side streaming: Implies RE Server, CP Client
 
### Server-side streaming: Implies RE Server, CP Client
 
### Client-side streaming: Implies CP Server, RE Client
 
### Client-side streaming: Implies CP Server, RE Client

Revision as of 17:36, 18 January 2023

The meeting time is 2:30pm.

Connection Info:


Agenda:

  1. Previous meeting
  2. Announcements:
  3. Starting IRIAD / EJFAT-II
  4. Current Test set-up:
    1. CLAS12 files -> Carl C++ Packetizer -> LB -> Carls's C++ Reassembler -> ERSAP
  5. New Test set-up (pending):
    1. CLAS12 files -> Carl C++ Packetizer -> new LB (delivered) / dynamic CP (in progress) -> Carls's C++ Reassembler -> PID controller (completed) -> ERSAP
    2. RE input fifo 50% full as PID set-point for Schedule Density
  6. New Test set-up: GAP
    1. CP gRPC i/f to RE PID:
      1. Asynchronous Peer Coupled
      2. Server-side streaming: Implies RE Server, CP Client
      3. Client-side streaming: Implies CP Server, RE Client
      4. Bidirectional streaming: Peer Coupled
      5. Publish/Subscribe:
    2. CP PID signal -> LB Schedule Density transform (Draft C++ algorithm completed)
    3. CP gRPC i/f to LB (pending)
  7. Status
  8. AOT