Open lbross opened 2 weeks ago
I've added a new RunScenario_DeleteInaccessibleCondFromWorktable() function to prevent plots with yarding distances < 0 from being included in the harvest_costs table.
When the fix is implemented, you will need to re-run Processor before re-running the Optimization scenarios to have this take affect on the Optimization output.
We screen these plots out and do not send them to OpCost. However, they are in the harvest_costs table for two reasons and thus are included in Optimizer analysis when they should not be.