Originally posted by: Rich Howard

Sounds like you are trying to find all the cruises with field called logs as opposed to cruises with only total heights called. The Logs table should have everything you need since it stores all the field called logs and grades. If there is a record in the Logs table, then there was a log called in the field.

Run a query like the following:

SELECT Stand

FROM Logs

WHERE NOT Grade IS NULL

GROUP BY Stand

Rich

Originally posted by: david.hann

1) The only version of ORGANON that allows pure hardwood stands is the red alder plantation version (RAP-ORGANON) because this is the only hardwood species with site index and dominant height equations and the only species that had data sets from pure hardwood stands. The remaining hardwood species in ORGANON came mostly from stands that were predominately conifer in composition.

2) The ORGANON board foot volume estimates are calculated using taper equations and when the model was developed there were no taper equations available for hardwood species. Therefore, there are no ORGANON board foot equations for hardwood species. Perhaps there are other equations that could be incorporated into the ASSISI software.

Originally posted by: Rich Howard

Hey Ryan,

You can exclude any trees on Regen type sub plots by setting “Compile Regen Sub Plots to Summaries?” to false. This will exclude TPA, BA etc from the summary tables from which reports are made. Note that if you view the individual trees in the Inventory Editor you will still see processed regen trees. They just won’t be included on the “rollup” type summaries (by species, by stand, by DBH class, etc) from which the reports are made.

The Compile Regen... option is set on the Volume view in Calibration Editor.

Rich

Originally posted by: Rich Howard

Added a Plots table view to Cruise. This shows all the plots and their data when you click on a cruise.Rich

Originally posted by: Rich Howard

HI Ryan,

You can really use whatever GIS format you want since it’s the GIS program rather than Assisi that determines how easy it is to link to Assisi’s database. Although ESRI does recommend the File Geodatabase over the Personal Geodatabase. See these links for more:

http://webhelp.esri.com/arcgisdeskt...odatabases

www.esri.com/news/arcuser/0309/files/9reasons.pdf

The one exception is if you want to use Assisi itself to display maps within the Assisi Interface. Then your maps have to be in shape file format. Shape files are old technology but you can use Assisi itself to browse stands, plots and trees by clicking on features in the shape file viewer in Assisi. In the future we will add direct geodatabase support but we haven’t heard all that much call for adding more mapping ability to Assisi as of yet. I suspect external tools are what everyone is already comfortably with. However, moving to a more visual interface is where we want to go in the future, and that means more mapping.

Maybe we should move that up on our todo list?

Rich

Originally posted by: Rich Howard

Hi Ryan,

I think you are on the right track. There is a Trees.Defect field that is meant to hold a defect that is applied to the whole tree. If you enter a value (direct database stores it as a fraction: .2 = 20%) then that defect will be applied in addition to any log level defects to get net volumes from gross volumes. But this applies to the whole tree, not just a broken top.

It’s tempting to use the IsBrokenTop flag to single that the defect be assumed from a broken top. But the IsBrokenTop flag is currently used to trigger estimation of the missing heights for volume of non broken sections. It’s probably better to add a defect type field to store a user defined type of defect as I think you are saying. It wouldn’t trigger any special processing but could be used to export to FORSEE better. Assisi however will still apply the defect to the whole tree as it does now unless a broken top height is entered explicitly.

Rich

Originally posted by: Rich Howard

Hi Jeff,I'm working on this as we speak It should be ready in the next setup later this week.In the meantime attached is a screen shot of the latest Thinning Rule Editor. Rich

Originally posted by: Rich Howard

Hi Eric,

There are a few ways to create reports in Assisi.The main Reports menu creates reports for all selected stands across any units. For example, clicking Reports|Butt Diameter will create Butt Diameter reports for every stand: a potentially many page report depending on the number of stands selected. If you want a report for a single stand, open Inventory, select a stand then click Inventory's Butt Diameter report. If you're after a Unit level report where many stands are averaged and sampling errors combined, then also use the Inventory editor, but this time select a Unit rather than a Stand, then click Inventory's Butt Diameter report. Hope this helps!

Rich

Originally posted by: Rich Howard

Hi Eric.The best place to go is the ORGANON web site itself: http://www.cof.orst.edu/cof/fr/research/organon

You can also get just about any forest modeling paper that's been published at the USFS site here: http://www.treesearch.fs.fed.us/ I'm thinking you are interested in the taper equations for SMC or NWO regions. The ORGANON taper models were developed for the SWO region first and then calibrated for other regions later. Only the SWO results were published: http://www.cof.orst.edu/cof/fr/research/organon/pubs/FRL_RB56.pdf (Walters & Hann 1986). The coefficients for other regions have to be obtained from the ORGANON source code directly. Going to the code is the best way to ensure you have the latest models and coefficients because publications don't always occur. In this case, there actually was another taper re-calibration, with SWO published in 2011. I would assume the taper models and coefficients for NWO and SMC regions were updated as well, but would have to look at code to see.

Rich

Originally posted by: Rich Howard

Hi Loren,Yes. Just add a column to the Cruise Entry sheet. The Validation and Export VBA code will have to be changed, but that’s what’s supposed to happen: you change the Cruise Entry sheet to what you want and I or someone else change the Validation and Export code to match.So go ahead and add a radial growth field when you are back from the field, send me the sheet and I will update the code to match your changes.Rich

Originally posted by: Rich Howard

Loren,If you change the BAF in the middle of a cruise, then you are changing the survey intensity in the middle of a cruise and plot to plot statistics will no longer be valid. I know Atterbury allows changing the BAF mid cruise and even a per tree basis, but if there is not consistent BAF usage between all plots, then plot to plot stats will not be valid. Volume and other measures can still be calculated, but the sample stats can't.Now, changing the BAF during a cruise is not the same as doing a Big BAF or Count Plot sample. Big BAF and Count Plots are examples of what is called Double Sampling. Double Sampling is statistically correct, and has been shown to be more efficient for a cruiser's time while in the field. Everyone should consider using it. The important difference from changing BAFs mid cruise is that in Double Sampling you are consistently using your BAFs throughout the cruise so plot to plot stat's are OK.Another way of putting it is changing BAFs change the likelihood of selecting trees to measure. If the likelihood is changing from plot to plot, then the trees on each plot are really not comparable to each other.So for Assisi, the real answer is unfortunately no. But, Double Sample IS a huge part of Assisi's features. You can set the measure and count BAFs as you need at the start of each cruise and they can be different for each cruise. Just be sure to not change them during a cruise. Ie, make the plots you want to compile together have the same sample intensities.Rich

Originally posted by: Rich Howard

New Update. Assisi Cruiser is now being built in Xamarin. I hit too many roadblocks with PowerApps. Perhaps in the future PowerApps will be offline and programmable, but not now. So I switched to Xamarin and haven't looked back.The prototype is working great. It stores data in a mobile database which you email to the office with a couple clicks. At the office, you import from the database just as you do with all the other formats Assisi imports.The mobile app is robust, reliable and I will be able to expand without limits in the future to add in field compiling and more. I am expecting a release 1Q 2018 with a beta before that.Right now I am building an Export from Assisi Forest that fills Assisi Cruiser Cruise Designs, Calibrations, Markets and everything else one needs in the field. Selected Field Data is also exported.The plan is be able to fully design a cruise project in Assisi with plot locations, species settings survey design, then export to Assisi Cruiser and off you go!Rich

Originally posted by: Rich Howard

😁

Originally posted by: Rich Howard

Hi Eli,QMDS is from stand level BA and TPA. QMD is the average of plot QMDs.I was curious to see the difference when plot to plot variability is large. QMD is larger than QMDS in these cases. I think due to the plot avg version weighting each plot QMD equally while stand level in effect weights QMD by tree TPA.Stand 010302 in the sample database is a good example. 3 plots with ~.1" DBH trees. 3 plots with ~20" DBH trees. 1 empty plot. What is the best estimate of the "tree with average BA"? The plot average: 15" or the stand "avg": 4"? Does it matter?It's custom to use stand level BA and TPA for QMD so refer to QMDS. I am probably going to rename QMDS to QMD and plot level QMD to QMDP or remove it entirely.Rich

Originally posted by: Rich Howard

It's likely that new species need to be added. Depending on the error wording, species may need adding to the Master list, Calibrations, Markets or Growth Model mappings.Missing Master SpeciesThe first place a species needs to be defined is in the "Master Species List". The list is accessed using the Calibration Editor as shown below. To add a species, make a new entry in the table by hand. Species, ID and Code are required and must be unique across all species. This is how each species is uniquely identified throughout Assisi.Once a species is defined in the Master list, it can be added to other places within Assisi.Missing Market SpeciesFor example, If the error says grade "G" can not be found for species "S", then grades for species S must be added to the grades for the Market you are processing with. This can be the case for grades or sorts or products. Note that if your sorts or products use grades or sorts as min criteria, then those grades or sorts must be defined as well. IE, even though you haven't called a certain grade or sort in the field, the products may need to refer to them anyway.So for Market errors, go through and add every combination of species and grade or sort or product you might use now or in the future. There are SQL queries int he Query Tool that will copy existing grades to new species. Give it a try. Edit the species and market values first.Missing Calibration SpeciesIf a species is missing in a calibration, you will see and error at compilation that species "S" is not found in calibration "C". This is easier to fix than adding species to markets: just copy and paste an existing species in the Calibration Editor. Choose a species that is closest to the new species in terms of growth, taper and other models. OK, not so easy after all, but its easy to add a new species from an existing species as a starting point.Here I am selecting Bitter Cherry as my existing species:I do ctrl C then ctrl V and a copy of Bitter Cherry is added to the ORGANON calibration. The species name defaults to the 1st species not already in ORGANON: Acadia in this case:Lastly, I choose Black Cherry as the new Species name:This adds a new species to a Calibration, but it will be modeled exactly like the species it was copied from. However, now you can change model settings as needed. What those model settings should be is a combination of what is available which is a mini research project of its own.Missing Growth Model SpeciesAnother place that missing species errors pop up is when they are in a calibration, but don't have a growth model mapping to a species a growth model understands. Growth model mappings are set in the Growth tab of a calibration.Below is the Growth tab for the ORGANON calibration. All growth models have different sets of default species they can process. Species other than these must be mapped to the growth model's defaults. In Assisi, this is done by adding a "SpeciesMapping" line to the list as seen below:The mapping line added must map to species through species code and the source species must be one that ORGANON inherently understands.SummaryThere are a number of places new species must be added and the places depend on what models and procedures in Assisi are being used. But, the errors that show up for missing species should point the way to where they need to be added.Rich

Originally posted by: Rich Howard

It sounds like you are calling logs in the field on softwood, but only occasionally on hardwoods and what you want is to get board volume from only the logs called in the field? If that's correct, then I think the answer is to use Assisi's Market grading process to map field called logs to board, but anything other logs Assisi creates during compilation to cubic.This can be done by calling both a Grade and a Quality on logs in the field. Call the Grade as usual, but also assign a Quality of say "Sawlog" as well. Then in the Assisi Market, set Min Quality to "Sawlog" for all grades you are mapping to board volume. For grades being mapped to cubic, such as Pulp, leave the Min Quality setting blank.When Assisi compiles your cruise, the "Sawlog" Quality requirement will restrict those grades to only the logs you called in the field. Other logs that Assisi calculated and grades during compile will not have the "Sawlog" quality and therefore wont be mapped to "Sawlog" grades.

For example, here I've selected "S" Min Quality on DF grades in the Market Editor. "S" is the code for the "Sawlog" Quality

Rich

Originally posted by: Rich Howard

Hi Eli,Yes, the History table is where details about planting, thinning or other action are recorded. Assisi will simulate the details as stands are grown forward.You can get to Stand History through the Field Data Editor. Click a stand, then click the History view:Once a History record's Action is set, a little "+" box will show. click that and a table shows up where you can enter the planting stock details.

Originally posted by: Rich Howard

Hi Alannah,The greying of stands is to show the stands are not “locked” by you yet. Locking is a feature of the Enterprise version of Assisi, but sometimes when I edit data using an Enterprise version, I forget to unlock the stands when I am done. Sorry, I forgot to unlock them when I was done.The way it works is this: If stand backgrounds are grey, they are not locked by anyone. Lock them by right clicking with ctrl key down. To lock all stands, select all units, then ctrl right click to lock.If stands are grey and dimmed, then they are already locked by someone else. Since you run in Desktop and not Enterprise mode, you should unlock all stands using the "Reset Locks" query in the Query Editor. This will unlock all stands so that you can lock them using ctrl right lick.Note that Plans and Operations work the same way. work the same way: they lock and unlock.Hope this helps!Rich

Originally posted by: Rich Howard

MaxLocksPerFile is a registry entry that limits the number of file system locks on the Access database file. It has been set at 9500 since its debut 2 decades ago but today it needs and can be set much higher. I routinely set it at 100,000 by running reg edit and searching for "MaxLocksPerFile". The Assisi setup wont do this for you because security and best practice is to not fool with other registry entries than the ones the setup creates.So, just run regedit, search for "MaxLocksPerFile" and change its value to 100,000. Regedit will show values in hex so us 100,000 in hex. Continue to search and change until all "MaxLocksPerFile" are set to 100,000. There can be many, like over 5 or so.

Originally posted by: joshjulien

I didn't get any handled error. it was the standard VS unhandled window. If I can reproduce the error I'll send you the log.Thanks