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 4
    • Merge requests 4
  • 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
  • #218

Closed
Open
Created Apr 06, 2018 by ext-neveu_n@ext-neveu_nMaintainer

Optimizer not saving expected data

When running a 100 generation optimization, we see some behavior we aren't sure of (maybe the two are related):

  1. The number of feasible solutions does not match the total number of simulations saved in the json files.
    Total number of individuals saved in json files = 65288
    Number of accepted individuals is about half:
    "Statistics: individuals accepted = 33135"

  2. We use the following population numbers:
    INITIALPOPULATION=656,
    NUM_IND_GEN=328,
    We thought the later attribute would reduce the number of individuals in later generations.
    The majority of generations (90%) still have 656 individuals.

Any help understanding this behavior would be appreciated.
Input files are attached:
ga-model.in
ga-model.data
fieldmaps.tar.gz
ga-model.tmpl

Edited Apr 06, 2018 by ext-neveu_n
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking