gINT Lab - Sieve Analysis Report Form

Question

Does anyone have a report form which shows the sieve output in AASHTO rather than ASTM?

Kirk Johnson · Answer

Hi Janet, The easiest way is to use the built in AASHTO functions on you graph report. There are many ways to implement. Assuming you are using the standard gINT US lab database and library you can use this. goto report design and pick your grainsize report in the yellow dropdown at the top. Then goto file ..copy page create a new report called Grain size AASHTO (or whatever you feel is appropriate). In the new report double click on the classification entity and open up the text expression box .. Remove what is there and replace it with the following <><<#>>,_ <>,_ <>,_ <>,_ <>_ )>>_ )>>_ <><<#>>,_ <>,_ <>,_ <>,_ <>_ )>>_ )>>_ <>,_ <>)>>_ )>>,_ <>,")"<>)>>_ )>> This is just one way! IE you could make another user system data item reference both the ASTM and ASSHTO code in the same expression and trigger it from an input field to pick what classification to use etc... There are some Agency reports that use AASHTO, IL dot , USDA, OH DOT classification function etc..... They can be found here AGENCY REPORTS These templates have been designed to support the production of reports for the indicated agencies. While we have worked to ensure these templates are current and produce correct results, we make no warranty… Last edited over 2 years ago in OpenGround | gINT | Keynetix > gINT | Keynetix Wiki For a complete list of classification systems gINT has functions for in gINT goto Help menu Search Classification of soils Classification of Soils (lab testing) --> Currently gINT supports the following classifications of soils: AASHTO BSI ILDOH MNDOT OHDOT ASTM USDA All the classification functions require expressions for extracting the gradation and Atterberg Limits data. Generically the function syntax is: <>,_ <>,_ <>,_ <>_ )>> The gradation size and percent passing parameters can only be field references: usually <> and <> or Union functions if used: usually <>,<>)>> and <>,<>)>> The remaining parameters are usually <> such as: <> and <> but can be expressions. When the classification function is in a repeating text entity on a graph, the syntax is: <><<#>>,_ <>,_ <>,_ <>,_ <>_ )>> Note the "<<#>>" after the size parameter. The repeating text entity converts this to 1, 2, etc. This tells the program to use the data for the first, second, etc. records associated with the current graph. When using just <> for the parameters after the size and % passing fields, there is nothing more you need to do. If you have expressions in these positions, you must tell the function to use the appropriate data for the fields. For example, you can use one of the following functions for ASTM classifications : ASTM_Name Returns Group Name as "ORGANIC CLAY", "GRAVELLY ELASTIC SILT with SAND" ASTM_Symbol Returns Group Symbol as "CL", "CL-ML", "GC" ASTM_Desc Returns description of components, as "low plasticity clay, fine gravel." ASTM_Full_Desc Returns Group Name (Symbol) Description, as "SILTY SAND with GRAVEL (SM), non-plastic silt, fine sand, coarse gravel" The function syntax for all the above is: <>,_ <>,_ <>,_ <>[,_ <>]_ )>> The Organic True/False expression is optional (indicated by the surrounding [...]). If included and the expression evaluates to True, the soil will be classified as organic, if appropriate according to ASTM D2487. If the standard Lab Testing tables and fields are used: <>,_ <>,_ <>,_ <>,_ <>_ )>> Copyright (c) 2016 Bentley Systems, Incorporated. All rights reserved.

Kirk Johnson · Answer

Hi Steve, This would apply to the gINT Std US Lab file set If you are using a repeating text entity on a report that is outputting multiple tests then the syntax is <><<#>>,_ <>,_ <>,_ <>,_ <>_ )>> If you want the symbol and the class then there is a built in User system data <> This only applies to some of the standard file sets we ship in particular the gINT std US Lab file set.