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
  • #43

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

Remote methods

Some notes on what methods to implement on a remote server.

This is excluding bulk transfer of data which is to be handled separately (ie a remote ClipBoard).

I believe the core are following:

Setup pipeline

For instance histogramming, this would set up which actions to run some set of data. A description of an input and output for this data is provided and any listeners required for this data is set up before the method completes. No data will arrive before the end of this method.

This can additionally describe connections to be made for feedback.

Run pipeline

Process data in the pipeline. This continues until processing of all data is complete. The finish signal arrives on the data input (ie the scan has finished).

Pipeline status

Eg How many data items have been processed or queued. Connection status of data in/out

Run scan

This runs a scan, including setup of LoopActions and HwControllers. Setting up of pipelines is done before this so that processors are alrready ready to receive data.

Scan status

Report current location in scan hierarchy.

FE Configuration

TBD which process is responsible for loading FrontEnd configuration.

Assignee
Assign to
Time tracking