Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
VILLASweb-backend-go
VILLASweb-backend-go
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ACS
    • P
      Public
  • VILLASframework
  • VILLASweb-backend-goVILLASweb-backend-go
  • Issues
  • #38

Closed
Open
Opened Jul 01, 2020 by Sonja Happ@skolenMaintainer

Add "Result" element to data model

The VILLASweb datamodel and API requires an extension to manage simulation result data. Two options for result saving shall be available:

  • Saving a result file to the PostgreSQL DB
  • Saving time series results to a TS DB (e.g. Influx, Cassandra, ...) and link the set of results to the PostgreSQL DB

A Scenario gets a new associated table "Results".

The model of Result:

type Result struct {
Model
// UUID of result (used to link result to time series TB entries)
UUID string
// JSON Snapshots of the component configurations used to obtain the results
ConfigSnapshots postgres.Jsonb
// A short (optional) description of the simulation executed to obtain the results
Description string
// Array of FileIDs of result files in the DB (files must belong to scenario)
ResultFileIDs []uint
// ID of scenario to which result belongs
ScenarioID uint

// ...
}

CC @markus.mirz @stvogel

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: acs/public/villas/web-backend-go#38