Skip to content

Small addendum to the list of PlantSimEngine Julia errors, also used … #172

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Samuel-amap merged 1 commit into from
Dec 10, 2025
Merged

Small addendum to the list of PlantSimEngine Julia errors, also used … #172

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions docs/src/troubleshooting_and_testing/plantsimengine_and_julia_troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,6 +99,21 @@ The syntax for an empty NamedTuple is `NamedTuple()`. If instead one types `()`

Most of the following errors occur exclusively in multi-scale simulations, which has a slightly more complex API, but some are common to both single- and multi-scale simulations.

### ModelList/Mapping : providing a type name instead of an constructed instance

```julia
m = ModelList(day=MyToyModel, week=MyToyModel2)
```
This line is incorrect and will return
```julia
MethodError: no method matching inputs_(::Type{MyToyDayModel})
```

The correct syntax is (assuming the corresponding constructor exists) :
```julia
m = ModelList(day=MyToyModel(), week=MyToyModel2())
```

### Implementing a model: forgetting to import or prefix functions

When implementing a model, you need to make sure that your implementation is correctly recognised as extending `PlantSimEngine` methods and types, and not writing new independent ones.
Expand Down
Loading