Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • YARR YARR
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 67
    • Issues 67
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 47
    • Merge requests 47
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • YARR
  • YARRYARR
  • Issues
  • #41

Closed
Open
Created Mar 27, 2020 by Bruce Joseph Gallop@bgallopMaintainer

DataProcessor generalisation

A DataProcessor takes a stream of data items from a ClipBoard, processes them and sends them to another ClipBoard (possibly a map).

Currently the chain of types is as follows:

graph LR
RxCore -- RawDataContainer --> FEDataProcessor
FEDataProcessor -- EventDataBase --> Histogrammer
Histogrammer -- HistogramBase --> Analysis
Analysis -- HistogramBase --> DATA
DATA[(Results)]

This is "hard-coded" in the types stored in the BookKeeper and the methods used to connect a pair of ClipBoard's to a DataProcessor.

From a distributed point of view the question is how rigidly these connect to each other. For instance, if a processor advertises (in some way) that it can produce histograms, does that make it a Histogrammer, or an Analyser?

As a first pass, a rigid connection should be OK.

Edited Mar 27, 2020 by Bruce Joseph Gallop
Assignee
Assign to
Time tracking