You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the AGS standard there are two particle size percentages that are used for oversize correction, but in the ASTM Standards there are 3 particle sizes used for oversize correction. I am trying to find where they would be stored in a compaction test. Potentially they go into a specimen but that is not truly correct because then you would be replicating this for each specimen (proctor point/trial) used in the test when in fact they always have the same oversize correction % because that is part of the specimen preparation process. What ASTM requires is that you have the following particle sizes for the oversize correction. 19mm (3/4"), 9.5mm (3/8"), and 4.75 mm (No. 4). This is not a "grading" test so you would not have a gradation associated with this test. It is technically part of the preparation of the bulk sample to separate the oversize material and determine the % of the material for these sizes.
If we put them in the specimen, we would have something like this, but it isn't valid as you are only allowed one sizeFraction object.
4.75
45.5
9.5
90.9
19
100
Accordingly, I suggest that we need 3 new elements in the LabCompactionTest object.
percentPassing4p75mmSieve, percentPassing9p5mmSieve, percentPassing19mmSieve
Another question I have related to the compaction test is where is the Stabilization Type and Amount of Stabilizer (these are AGS fields CMPG_STYP, CMPG_STAB). This is used for scenarios where you are doing cement stabilization/lime stabilization and testing the properties of the soil/stabilizer mix.
The text was updated successfully, but these errors were encountered:
2.6-dev has developed a series of objects to describe grout and soil-grout mixes along with aggregate specifications that include a grading property to describe the grain size distribution of grout aggregate.
We could add a similar property to the specimen that would allow reporting of percent passing any screens used, and be more flexible than the specific properties you identify for ASTM.
As for the stabilzation information in AGS, the grout sample (GroutBatch) specifies amount of admixture, binder, cement, chemicals and fillers in the grout (or soil grout mix (soil is the filler), so these properties would carry over to the specimen being tested.
In the AGS standard there are two particle size percentages that are used for oversize correction, but in the ASTM Standards there are 3 particle sizes used for oversize correction. I am trying to find where they would be stored in a compaction test. Potentially they go into a specimen but that is not truly correct because then you would be replicating this for each specimen (proctor point/trial) used in the test when in fact they always have the same oversize correction % because that is part of the specimen preparation process. What ASTM requires is that you have the following particle sizes for the oversize correction. 19mm (3/4"), 9.5mm (3/8"), and 4.75 mm (No. 4). This is not a "grading" test so you would not have a gradation associated with this test. It is technically part of the preparation of the bulk sample to separate the oversize material and determine the % of the material for these sizes.
If we put them in the specimen, we would have something like this, but it isn't valid as you are only allowed one sizeFraction object.
4.75
45.5
9.5
90.9
19
100
Accordingly, I suggest that we need 3 new elements in the LabCompactionTest object.
percentPassing4p75mmSieve, percentPassing9p5mmSieve, percentPassing19mmSieve
Another question I have related to the compaction test is where is the Stabilization Type and Amount of Stabilizer (these are AGS fields CMPG_STYP, CMPG_STAB). This is used for scenarios where you are doing cement stabilization/lime stabilization and testing the properties of the soil/stabilizer mix.
The text was updated successfully, but these errors were encountered: