Posted: Tue Feb 14, 2012 11:51 pm
Matt,
I notice your Redwood Creek Giant mesh is a bit concave at the top ?
My volume solution for RCG is now about 1% from your RapidForm XOR now using a "best fit" strategy for the missing points (that always arrive in cloud maps). I used a conservative linear interpolation between closest surface edge points. In my experience I have found that spline interpolation over-estimates tree surfaces so that was not used here.
Here is my output for the latest code revision using your input numbers. I get 3108 cubic feet and 1212 square feet respectively. Darn close. I am satisfied with these results.
Also, you are measuring the volume and area of the mesh from RapidFormXOR, correct ? In that case, your surface area should be a little greater because your mesh has 1/2 the points of the cloud set I am processing which has triangular facets too but more of them. I'll run the RapidForm mesh cloud through my custom code and see what happens.
here are the latest results:
Range Filters # of Points = 6318 347 = # of Slice Points
Xmin -9.000 Xmax 9.000
Ymin -10.000 Ymax 11.000 Contol-V Control-C
Zmin -1.000 Zmax 30.000 To Calculate To Extract
Pole XYZ 0.000 0.00 0.000 Volume Cookie
Zcookie 0.000 Thickness 1.000
Ht Start Pt 0.000 Ht End Pt 20.000 Current Height Int. 20.000
Slice Thickness 1.000 Ray Incº 1.00 Typical Ranges = 1º - 2º - 3º
Forest Form ID: Redwood Creek Giant
Polygon Area Upper 125.429 Slice Volume 126.543 Total Weight 82682.435
Polygon Area Lower 127.661 Total Volume 3108.362 Surface Area 1212.572
Took an hour + to solve. I added weight too
The attached is the ForestForm1.6 volume and area calculator for RCG with 30k points in the default table. I truncated the last 35k points of this table to speed the program up a little, but it is still SLOW. The RCG cloud set also has a few parasitic outlier points as well which can add a litle error to the volume solution if not removed. You may want to decimate it or transform into a Mesh again before playing with it. I just want to make sure we are comparing apple to apples here. I think the attached volume solver has a slightly different embedded RCG cloud set than the one you worked with last time.
At some point I should re-write this code in Visual C+ and compile into machine language.
How much does RapidForm XOR cost ? I get the feeling it's expensive.
Lastly, this "ForestForm1.6" Solver will work all the way up the trunk to nearly the top, unless the tree has a severe lean or multiple iterations. In that case, boundary issues will occur. To overcome this in the spreadsheet you would need to solve volumes in parts and re-center the origin of the cloud set higher up before it touches a surface edge.
There is also another solution which would be for me to completely redo the existing code so that it can handle any multiple pair of surface boundaries that arrive when structures have severe leans, negative taper and/or side iterations and multiple trunks. The difficulty level to find these volumes is much great than the current code I have written so far. I am writing this version now and it's slow going. I would prefer to invest my time writing a visual C+ version for commercial use. All ENTS members will get 50% discount on this software"Forest Form" if I should ever bring it to market. I am not sure if it is worth my time yet. We'll see.
Michael Taylor
WNTS VP
http://www.landmarktrees.net
I notice your Redwood Creek Giant mesh is a bit concave at the top ?
My volume solution for RCG is now about 1% from your RapidForm XOR now using a "best fit" strategy for the missing points (that always arrive in cloud maps). I used a conservative linear interpolation between closest surface edge points. In my experience I have found that spline interpolation over-estimates tree surfaces so that was not used here.
Here is my output for the latest code revision using your input numbers. I get 3108 cubic feet and 1212 square feet respectively. Darn close. I am satisfied with these results.
Also, you are measuring the volume and area of the mesh from RapidFormXOR, correct ? In that case, your surface area should be a little greater because your mesh has 1/2 the points of the cloud set I am processing which has triangular facets too but more of them. I'll run the RapidForm mesh cloud through my custom code and see what happens.
here are the latest results:
Range Filters # of Points = 6318 347 = # of Slice Points
Xmin -9.000 Xmax 9.000
Ymin -10.000 Ymax 11.000 Contol-V Control-C
Zmin -1.000 Zmax 30.000 To Calculate To Extract
Pole XYZ 0.000 0.00 0.000 Volume Cookie
Zcookie 0.000 Thickness 1.000
Ht Start Pt 0.000 Ht End Pt 20.000 Current Height Int. 20.000
Slice Thickness 1.000 Ray Incº 1.00 Typical Ranges = 1º - 2º - 3º
Forest Form ID: Redwood Creek Giant
Polygon Area Upper 125.429 Slice Volume 126.543 Total Weight 82682.435
Polygon Area Lower 127.661 Total Volume 3108.362 Surface Area 1212.572
Took an hour + to solve. I added weight too
The attached is the ForestForm1.6 volume and area calculator for RCG with 30k points in the default table. I truncated the last 35k points of this table to speed the program up a little, but it is still SLOW. The RCG cloud set also has a few parasitic outlier points as well which can add a litle error to the volume solution if not removed. You may want to decimate it or transform into a Mesh again before playing with it. I just want to make sure we are comparing apple to apples here. I think the attached volume solver has a slightly different embedded RCG cloud set than the one you worked with last time.
At some point I should re-write this code in Visual C+ and compile into machine language.
How much does RapidForm XOR cost ? I get the feeling it's expensive.
Lastly, this "ForestForm1.6" Solver will work all the way up the trunk to nearly the top, unless the tree has a severe lean or multiple iterations. In that case, boundary issues will occur. To overcome this in the spreadsheet you would need to solve volumes in parts and re-center the origin of the cloud set higher up before it touches a surface edge.
There is also another solution which would be for me to completely redo the existing code so that it can handle any multiple pair of surface boundaries that arrive when structures have severe leans, negative taper and/or side iterations and multiple trunks. The difficulty level to find these volumes is much great than the current code I have written so far. I am writing this version now and it's slow going. I would prefer to invest my time writing a visual C+ version for commercial use. All ENTS members will get 50% discount on this software"Forest Form" if I should ever bring it to market. I am not sure if it is worth my time yet. We'll see.
Michael Taylor
WNTS VP
http://www.landmarktrees.net