Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • F FEDOT
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 87
    • Issues 87
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ITMO-NSS-team
  • FEDOT
  • Issues
  • #207

Closed
Open
Created Dec 10, 2020 by Rosneft rosneft@rosneft_userDeveloper

Minor flaws in model export

IMO there are several minor issues in the JSON export of the model:

  1. "total_chain_types" field is quite confusing image

"total_chain_models" can be better

  1. trained_model_path contains the absolute path. Is it have a reason fronm the reproducibility point of view (since that path becomes non-actual if the folder is moved)? Maybe the relative path is better?

image

  1. The "nodes_from" indices are duplicated if there is only one parent for node

image

  1. The FileExistsError occurs if the model exports twice with the same file name. The warning and additional index in the file name look comfortable behavior for the user (now the results of the long optimization run can be lost in such case).
Assignee
Assign to
Time tracking