u/SaswatRath

I’ve been working with agricultural physicists and agronomists here at ICAR, and we were discussing about how visualisation or simulation is being handled in today's research scenario. I would say all standard tools we use are great for data output and backend math, but they suck it when it comes to intuitive, 3D visual simulation of growth progress, disease spread, or soil-water flux over time.

For those of you running these kinds of simulations, how do you handle the visualization component? Do you rely on static charts, or have you ever felt the need for a live, 3D 'digital twin' environment where you could scrub through time-series data to see how physiological factors are affecting the canopy and field in real-time?

I am currently working on a way to integrate this into the Python data science stack, and I’m curious if this level of visual interactivity would actually change your research workflow, or if you prefer sticking to the traditional table/graph-based analysis. I strongly think that such a tool which allows for full freedom and visualisation impacting every crop would genuinely revolutionize Agricultural Research.

Hey everyone,

I have recently studied and discussed a lot regarding how 'simulations' are being handled in agriculture. And today none of the tools quite provide flexibility or more importantly freedom and visualisation.

I wanted something different, something like a code-first virtual farm where I could actually see the physiology and environmental effects in 3D, without it feeling like a black box.

So, I built CropForge.

It’s an open-source, code-first virtual farm runtime. Instead of creating something which works with averages and considers means, I took a different approach and made it sensitive to the environment and allowed full flexibility over all maths and equations that are fed in, basically one can simply input anything they want.

I’ve just hit v1.0.0, which is the stable release and like I said it's fully flexible.

I’m looking for feedback from you all, regarding if you want to actually incorporate it into your research work. Does the API structure actually fit your workflows? I’d love for you to break it and tell me what’s missing.

TL;DR: I built CropForge which is a local, Python-based virtual farm runtime that visualizes crop physiology in 3D. It’s open-source, v1.0.0 is live, and I’m looking for technical feedback on the API.

GitHub: CropForge

Agricultural researchers, what do you do for visualisation?

I built an open-source, 3D virtual farm runtime in Python for agricultural research.