Point load test results in both direction for rock coring logs.

Hi, How can I add D and A for diametral and axial point load test results for rock coring logs. As in this photo, IS(50)=0.16MPa and 0.21 Mpa for diametral and axial. How to describe which one i diametral and which one in axial direction. Please help

Parents
  • I solved this problem as follows.

    My point load data is stored in a table called LAB_TEST with a key set of Point_ID, depth.  The field name is Point_Load. Your data is likely different and this may not apply depending on how your data is stored and the expression used to print results on the log. I did not want to add a separate field for axial or diametral  results or a field that would allow you to enter A or D as this would require a change in data structure and modification of all applicable logs to accommodate the new field. I simply made all my lab test fields text fields which allows me to enter something like "0.16 (D)"  into the data field. This is then printed on the log verbatim.  Note that this also allows me to enter things like "<0.005" or ">4.0" when the range of the test equipment is exceeded or "ND" for not detected (an important result but not a number).  It also allows me to maintain appropriate significant figures in reported results (ie 0.5 is not the same as 0. 5000)You have to be careful with this approach if the results are used in a mathematical equation or plotted on a graph on other log forms but this is easily handled by adding a <<LeftNum()>> function to return the numeric portion of the text or other appropriate function.  While it does change the data structure by changing the field type, it does not add any fields that then have to be incorporated into other log forms it also allows users to abuse the the field by allowing non numeric input. If you enter "Who cares" in the point load field  it will be allowed and will print on the log.  If you have reasonableness checks built into your data structure (for example value must be greater than 0 and less than 100) this will defeat them.

Reply
  • I solved this problem as follows.

    My point load data is stored in a table called LAB_TEST with a key set of Point_ID, depth.  The field name is Point_Load. Your data is likely different and this may not apply depending on how your data is stored and the expression used to print results on the log. I did not want to add a separate field for axial or diametral  results or a field that would allow you to enter A or D as this would require a change in data structure and modification of all applicable logs to accommodate the new field. I simply made all my lab test fields text fields which allows me to enter something like "0.16 (D)"  into the data field. This is then printed on the log verbatim.  Note that this also allows me to enter things like "<0.005" or ">4.0" when the range of the test equipment is exceeded or "ND" for not detected (an important result but not a number).  It also allows me to maintain appropriate significant figures in reported results (ie 0.5 is not the same as 0. 5000)You have to be careful with this approach if the results are used in a mathematical equation or plotted on a graph on other log forms but this is easily handled by adding a <<LeftNum()>> function to return the numeric portion of the text or other appropriate function.  While it does change the data structure by changing the field type, it does not add any fields that then have to be incorporated into other log forms it also allows users to abuse the the field by allowing non numeric input. If you enter "Who cares" in the point load field  it will be allowed and will print on the log.  If you have reasonableness checks built into your data structure (for example value must be greater than 0 and less than 100) this will defeat them.

Children
No Data