Skip to content
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.

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

Develop a white clover model (PMF) #2069

Closed
rcichota opened this issue Oct 15, 2017 · 4 comments
Closed

Develop a white clover model (PMF) #2069

rcichota opened this issue Oct 15, 2017 · 4 comments

Comments

@rcichota
Copy link
Contributor

rcichota commented Oct 15, 2017

White clover (Trifolium repens) is herbaceous perennial plant of the Fabaceae family. It is native of Europe and central Asia, but now is spread worldwide, being recognised as the most important forage legume in temperate zones. White clover provides high quality feed for animals and is tolerant of grazing and trampling. It is typically used in mixed swards, alongside grasses, in which it improves feed quality and it can supply N to the system through biological N fixation. The plants are short, with stems functioning as stolons from which petioles with three leaves and flower stalks grow. Roots are generally shallow and also grow from the stolon nodes.
The objective here is to develop a basic white clover model using the plant modelling framework (PMF). In this project the focus in on describing the general growth pattern of monoculture, as well as the re-growth after cut/grazing and including N balance. As PMF uses MicroClimate and SoilArbitrator to manage resource access, it should be readily possible to develop simulations with multiple species. While developing the White Clover model, the need for it to be used in mixed swards simulations will be taken in consideration as much as possible. However for fully testing this, a grass model is needed (none is currently available in PMF, although AgPasture may be an alternative).

@rcichota
Copy link
Contributor Author

@sarahcleary
I am finally ready to cal the review of WhiteClover to a finish. I have finally got around to re-trace some to the steps taken during the review, eliminate some of the junk and align the simulation with new json format. All this was completed this week and Dean has merged into the main branch.
A lot of small modifications where done along the way to comply with the reviewers comments, which centred mostly on the documentation itself. Several of the changes are/will be useful for other models too. The flow of the text, the ranking of items, the exposure of information about organs and parameters have been all improved, some of the graphs are still too cluttered, but this is something Dean at al, are looking into. I have also added a few more comments about the outcomes of the validation, but kept this to minimum, as the amount of data was fairly limited it is difficult to point out why some of the results are not that good or more definite directions in which the model could be improved. There is some work on going for red clover and diverse pastures that may help improving some of the biomass/N allocation which I think is not quite right in the white clover model. This will include some sensitivity analyses too.
I hope this is sufficient an answer to the review, but let me know if I need to expand further on any point.

@sarahcleary
Copy link
Contributor

sarahcleary commented May 10, 2019

thanks @rcichota
@APSIMInitiative/reference-panel - please note @rcichota's comments above. Please review and provide any feedback prior to the RP meeting on the 21/5,
Please note that Matt Harrison's review stated "Overall I think it should be accepted with minor amendments.” If you would like another copy of this - please let me know.
thanks
Sarah.

@sarahcleary
Copy link
Contributor

@APSIMInitiative/reference-panel - confirmed for merging in RP meeting. @rcichota - please release and work with Dean

@sarahcleary
Copy link
Contributor

Closing issue, released 28/5/19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Release
Development

No branches or pull requests

3 participants