Skip to content

Improve protocol format #25

@kernfel

Description

@kernfel

Having encountered a very large protocol file recently (180k lines, mostly due to SpikeGenerator data), I noticed:

  1. Loading, and thus startup, is very slow under such circumstances
  2. The protocol format is extremely redundant and would likely benefit from a better (read: standard & tree-based, e.g. yaml) format both in human readability and loading speed
  3. SpikeGenerator data should perhaps live in a separate file... or at least on the horizontal axis rather than the vertical one, to ease scrolling to relevant sections if offline troubleshooting is required.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions