We tested the approach with a case study that simulated the productivity of continuous wheat cropping system during 20 years period along the Australian cereal-growing regions under management practices of 5 levels nitrogen application and 3 stubble management practices. We parallelized the batched running method in a shared-memory multiprocessor system using Python's Multiprocessing module. In this approach, an APSIM simulation template with replaceable parameters was firstly designed, and new simulations based on the template was then constructed by dynamically replacing parameters of climate, soil and management options.
APSIM PARALLEL SIMULATOR
Here, we developed a high performance approach which concurrently executed the Agricultural Production Systems sIMulator (APSIM) simulations using parallel programming techniques. The graphic interface based model dose not suit for modelling practices requiring a large number of simulations. Traditionally, the process-based agricultural models are designed for field scale studies that obtain inputs, run the simulations and provide outputs through the graphic interface. I have very little time to help support this unfortunately.Increasing concerns about food security have stimulated integrated assessment of the sustainability of agricultural systems at regional, national and global scales with high-resolution.
APSIM PARALLEL CODE
On the Python side, code will need to be written to open a socket connection, wait for APSIM to call it and respond by sending a 'set of instructions' down the socket 'pipe'. On the APSIM side the code will need to be written in C# and some understanding of APSIM will be required.
APSIM PARALLEL SOFTWARE
It will require a software developer who is familiar with socket connections.
Are you able to provide some support in case we want to pursue this way? We could write codes for computer science courses and machine learning projects but we may not have extensive software development experiences. Instead, if you use sockets then yes it is 2-way communications - possibly harder to implement but much more flexible.įor the second way, do you think we can build the connection by ourselves? Our group is in the mechanical engineering department. If APSIM runs another process then some sort of file will need to be written by APSIM, read by the other process which then writes another file to send information back to APSIM - cumbersome.
Are you able to provide some support in case we want to pursue this way? Thank you very much.ĭo both of the two ways you mentioned allow bi-directional communication between APSIM and the other process (e.g., written in python) during the simulation? By bi-directional, I meant that APSIM receives the management decision from the other process and also sends the current crop and soil state to it. Do both of the two ways you mentioned allow bi-directional communication between APSIM and the other process (e.g., written in python) during the simulation? By bi-directional, I meant that APSIM receives the management decision from the other process and also sends the current crop and soil state to it.įor the second way, do you think we can build the connection by ourselves? Our group is in the mechanical engineering department. This would require some low level programming though - not trivial. More sophisticated would be to use an inter-process mechanism like sockets to do the connection between APSIM and Python/R - same idea as above but will run quicker and is more flexible. That other process could be an R or python script. exe) during a simulation run to get management for the day. You would have to write a manager2 script that calls another process (e.g.
0 kommentar(er)
