Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.web beat.web
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beat
  • beat.webbeat.web
  • Issues
  • #297
Closed
Open
Created Sep 08, 2015 by André Anjos@andre.anjos💬Owner

[experiments] Configurator gets confused if the user selects a new algorithm for block

If I fork the experiment: https://www.beat-eu.org/platform/experiments/tutorial/tutorial/full_lbphs/1/atnt-lbphs-para/, and then replace the algorithm in a block with a decollapsed parameter set, the platform tells me that the parameters are undefined. I'm not sure this problem is related to the fact there are two blocks with similar version lurking around or it is just the swap that confuses the configurator, when it a set of parameters preset.

Anyways, the expected behaviour would be, to preserve all possible parameters that make sense in the new settings, from the old one.

Screen_Shot_2015-09-08_at_03.56.42

Assignee
Assign to
Time tracking