From your descriptions, it seems that your tree cutting procedures do not involved precut of the tree's branches before cutting the tree down.
I've got the feeling that this cutting tree problem can be solved by constraint programming techniques [1],[2]. Alternatively generic tools for constraint programming, for example OR-Tools and MiniZinc can probably do the same if not better [3],[4].
[1] Logic, Optimization, and Constraint Programming: A Fruitful Collaboration - John Hooker - CMU (2023) [video]:
https://www.youtube.com/live/TknN8fCQvRk
[2] "We Really Don't Know How to Compute!" - Gerald Sussman - MIT (2011) [video]:
https://youtube.com/watch?v=HB5TrK7A4pI
[3] Google OR-Tools:
https://developers.google.com/optimization
[4] MiniZinc:
It's turning into various DIY rabbit holes, actually, with the next one (outside of various related landscaping stuff) being to gut a basement.
It is a very simple three-pass plan: "Deadwood, Crossovers, Aesthetics".
So, first pass, go through the tree cutting out only and all the dead branches. Cut back to live stock, and as always make good clean angle cuts at a proper angle (many horticulture books will provide far better instructions on this).
Second pass, look only for branches that cross-over other branches and especially those that show rubbing or friction marks against other branches. Cut the ones that are either least healthy or grow in the craziest direction (i.e., crazy away from the normal more-or-less not radially away from the trunk).
Then, and only after the other two passes are complete, start pruning for the desired look and/or size & shape for planned growth or bearing fruit.
This method is simple and saves a LOT of ruined trees from trying to first cut to size and appearance, then by the time the deadwood and crossovers are taken later, it is a scraggly mess that takes years to grow back. And it even works well for novices, as long as they pay attention.
I'd suspect entering the state and direction of every branch to an app would take longer than just pruning with the above method, although for trees that haven't fully leafed out, perhaps a 360° angle set of drone pics could make an adequate 3D model to use for planning?
In any case, good luck with your fruit trees — may they grow healthy and provide you with great bounty for many years!
Does an insane amount of fine print really save you? Even if you say the model is only an aide to be used by licensed or certified professional arborists or whatever, I fear some Joe blow whose tree lands on his house will be suing you.
- https://www.youtube.com/watch?v=XTeGbunc_Sk
My need/idea was to post that some where (r/backyardorchard probably) to get help in determining which limbs to prune. However, there didn't seem to be an easy way to share that sort of thing and time was of the essence, so I just forged ahead on my own.
Happy to help!
its surprising to me how little work is done to make the tools which do this accessible considering how much money and open data there is.
it gets less open and more complicated is when you consider certain mills only can make certain cuts, produce certain products, and accept certain logs. then factor in distance between mills and the products they can make, and also log lengths accepted by the trucks which can travel those routes.
its all solvable and should be, but its so niche and that i still think there isnt an accessible solution
I have a couple products I make that require 12" widths, which means I pay a whole lot more per bf than < 10" widths at my hardwood supplier.
My methods are all over the place. Tree is taken as-is on the day, and cuts calculated on the fly, no future growth-modelling if that is what you're asking
This became convoluted and I just opted for a far easier method of solving vector intersections.
Its also not perfect since I haven't factored in rotation origin very well, and I'm now pursuing a far simpler physics-based approach