Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
S src
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 61
    • Issues 61
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OPAL
  • src
  • Issues
  • #259

Closed
Open
Created Nov 20, 2018 by huber_y@huber_y

Structure of output JSON file

Right now the output JSON file is structured in a way such that when read by python using the json module it is converted to an array of dictionaries where each directionary contains a key "ID" and the corresponding ID is the value, plus additonal key such as dvars containing the design variables.

For finding an ID it would in my eyes be easier if the file was structured such that the resulting array contains only one dictionary, where the keys are something like ID+"dvars" where ID is the actual ID, since this allows to easily access elements.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking