Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Flatland Flatland
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 96
    • Issues 96
    • 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
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Flatland
  • FlatlandFlatland
  • Issues
  • #266

Closed
Open
Created Oct 30, 2019 by Erik Nygren@mlerik🚅Owner

Malfunction Generators

In the same manner as we use Rail and Schedule generators we should introduce a Malfunction Generator.

This will be help to easily test different malfunction models in the future. Here we can add more complex malfunction models then the currently implemented.

I suggest using the same setup as with the rail and schedule generators. This would also help resolve the problem with saving and loading different parameters from pickle files as we could also write generators for this.

Edited Oct 30, 2019 by Erik Nygren
Assignee
Assign to
Time tracking