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 62
    • Issues 62
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 5
    • Merge requests 5
  • 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
  • #255

Closed
Open
Created Nov 05, 2018 by ext-edelen_a@ext-edelen_a

OPAL GA interface does not raise error when design variable is not actually in tmpl file, and it writes spurious data to json

The GA input file writes to the json file which values it sent to the simulation even if those variables cannot be found in the tmpl file.(Example: in our case, LRAD was set in the GA input file, but in the tmpl file the value that actually needs to be changed is Rc, so, Rc was constant, but our data from the json file shows a spurious change in LRAD)

The same issue likely applies to the random sample interface.

--> OPAL should raise an error when a variable from the GA input file cannot be found in the tmpl file.

Edited Nov 05, 2018 by kraus
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking