Skip to content

Keep track of input format difference between GemsPy and Gems C++ interpreter #126

Description

@tbittar
  • expec not handled in C++, optional with GemsPy
  • Unified parameters.yml and optim-config.yml -> everything in optim-config.yml in GemsPy
  • model-decomposition field seems mandatory in C++, optional in C++

Ask AI to spot and keep track of differences in a dedicated .md file updated at each of the two interpreter release ?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions