Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
PRRT
PRRT
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • LARN
  • PRRTPRRT
  • Issues
  • #13

Closed
Open
Opened Jun 05, 2018 by Andreas Schmidt@asMaintainer

Gapfilling Mode

There should be a receive_gapfilling(..., fill_value) mode with the following traits:

  • If an expiry date approaches and the data is not there, a "zero" packet is delivered.
  • The filling pattern (e.g. "zero" should be configurable on the receive call).

ToDo:

  • Think about how to predict an "expiry" of a packet that has not been sent or recovered.
Edited Jun 05, 2018 by Andreas Schmidt
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: LARN/PRRT#13