Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.core beat.core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.corebeat.core
  • Issues
  • #33
Closed
Open
Issue created May 05, 2015 by André Anjos@andre.anjos💬Owner

Thorough testing and API support for plotters and plotter parameters

As of today, the concept of a plotter is implemented in beat.core. It would be good to extend its implementation in the core so that:

  1. Plotters can be downloaded/uploaded/edited using the web API and via the command-line tool
  2. A command-line utility is made available to plot a given experiment output
  3. Plotter parameters are instantiated in the core, so that we can also apply them while locally plotting

This should be done after the FG tutorial.

Assignee
Assign to
Time tracking