This PR updates the code in the feature/new_abiotic_model branch to the current develop including the new BaseModel architecture.
@vgro - because this brings in develop there are a lot of changes, but this PR seemed the easiest way to make changes to your branch. You can see what changes in the individual models and tests you're working on. I don't think there is anything controversial (apart from that the components all have long names).
The end result of merging this PR will be that the new_abiotic_branch is up to date with develop and all the tests run.
Fixes #381
Type of change
[ ] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[x] Bug fix (non-breaking change which fixes an issue)
Key checklist
[x] Make sure you've run the pre-commit checks: $ pre-commit run -a
[x] All tests pass: $ poetry run pytest
Further checks
[-] Code is commented, particularly in hard-to-understand areas
[-] Tests added that prove fix is effective or that feature works
Description
This PR updates the code in the
feature/new_abiotic_modelbranch to the currentdevelopincluding the new BaseModel architecture.@vgro - because this brings in
developthere are a lot of changes, but this PR seemed the easiest way to make changes to your branch. You can see what changes in the individual models and tests you're working on. I don't think there is anything controversial (apart from that the components all have long names).The end result of merging this PR will be that the
new_abiotic_branchis up to date withdevelopand all the tests run.Fixes #381
Type of change
Key checklist
pre-commitchecks:$ pre-commit run -a$ poetry run pytestFurther checks