[Task] getting outputs from Engine
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 25
- Forks
- 6
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 1
Description
When running crop models for different crop types with one Engine instance, we have to track all state variables. We need to fix get output functionality of the Engine, relates #124
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #124 and locating the Engine output functionality mentioned here. Reproduce running crop models for different crop types with one Engine instance, then determine the expected output behavior from the related issue. Done means outputs can be retrieved without manually tracking all state variables.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100