Hi all,
A client wanted AGS4 for a recent job. I exported the data from our AGS4 data structure and all went well, checked the file with the gINT AGS Checker, no errors or warnings. However, we got an email back from them saying that when they ran it through the KEY AGS checker, it came up with a number of warnings. I dutifully ran it through my copy of the Key checker and there were indeed a number of warnings, all related to the Moisture Content fields in 2 of the Rock tables (RDEN and RPLT if I remember correctly) The warnings were concerning the fact that the MC result in both tables should be to 2 significant figures as per BS1377(?) I looked this up in the publication and sure enough, if the result is below 10 the result should be reported to 2 significant figures. The only results the checker had problems with were the ones that were below 1 i.e. 0.2, 0.7, 0.5 etc These were reported as 0.2 etc in the AGS file. Not being in any way mathmatically inclined I went to a number of web sites to check how 0.2 should be shown to 2 sig figs and they all said it should be shown as 0.20. I don't understand this, as the trailing zero has no use at all that I can see, but once I had changed the results to 0.20, 0.70, 0.50 etc in the AGS file the checker was quite happy with it and showed no more warnings.
My questions are these, firstly, as the data type is "MC" , shouldn't gINT be exporting the results to 2 significant figures? (as an aside to this, I tried formatting the field in the correspondence file <<Format[RPLT.RPLT_MC,0.00]>>, which gINT promptly ignored, not adding the trailing zero. I also tried the sig figs version of that, which gINT also ignored. I also tried the FieldUnits[MC] thing, which gINT also ignored!)
Secondly, how come the gINT AGS checker didn't pick up the lack of sig figs as warnings?
Thirdly, why won't gINT let me export the result with a trailing zero?
I may be being rather stupid, (it wouldn't be the first time :-) ) If so, please ignore this post.
Miles