Skip to content

Konfiguration and separation of essential and nice-to-have requirements #17

@philipp-meister25

Description

@philipp-meister25

Konfiguration

  • The user can directly define requirements in the config.toml file
  • Requirements like metric, number of folds, etc. should be evaluated in code, not by the LLM
  • Default "best practice" requirements in the config

Separation

  • Separate between essential and nice-to-have requirements
  • Essential requirements are prioritized in debugging and improving
  • Scored separately, the essential requirements are necessary for a satisfactory node
    => we introduce a config parameter that determines how many nice-to-have requirements need to be fulfilled

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions