Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • finam-mhm finam-mhm
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • FINAMFINAM
  • finam-mhmfinam-mhm
  • Issues
  • #2

LAI adapter - multiple LAI curves by ID map

Currently as of !3, we can use a single LAI curve provided via code.

However, we will need to use multiple curves for different forest types, as a lookup table by ID per map cell. Table as well as the map will be privided via files.

Possible solutions

Adapter reads files directly

Simplest solution in terms of implementation. However, restricts file types and could be error-prone.

Use a component, with curves and map as additional inputs

Could be realized via a component without timestep, and callback inputs and outputs. Would, however, introduce "adapters that look like components". Might be ok, and "real" adapters are just seen as a shortcut for simple use cases.

Consider adapter rework

Allow multiple inputs for adapters? Could make writing simple adapters more complicated. Also, it is not trivial how to handle multiple inputs with non-synchronous time step. This is, however, the same for the above component solution.

Assignee
Assign to
Time tracking