Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Submit feedback
  • Sign in
S
src
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 75
    • Issues 75
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 7
    • Merge Requests 7
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • OPAL
  • src
  • Issues
  • #239

Closed
Open
Opened Jul 24, 2018 by adelmann@adelmann🎗2 of 2 tasks completed2/2 tasks
  • Report abuse
  • New issue
Report abuse New issue

Remove requirement of data file for SAMPLER and OPTIMIZER

We still use the runOPAL.py scheme with template / data file. However the design variables could be easily looked up in the dictionary or we invent new types: DvarReal etc.

[Edit: this has been moved to a separate issue, see #249 (closed)! If we could define quantities of interest (a la optimizer) and write them to the json file lengthly post processing would be avoided.]

Edit:

  • remove the need for a data file (!288 (merged))
  • write a json file containing the values of the DVARs and objectives (#249 (closed))
Edited Feb 24, 2020 by frey_m
To upload designs, you'll need to enable LFS. More information

Linked issues

Assignee
Assign to
OPAL 2.4.0
Milestone
OPAL 2.4.0
Assign milestone
Time tracking
None
Due date
None
4
Labels
Enhancement Feature request Optimiser Sampler
Assign labels
  • View project labels
Reference: OPAL/src#239