I have multiple boreholes (20) in one gINT file. I want to combine non-core log, core log, well log, and core photos for each individual boreholes. How can I do this by writing a script ?
Hi Aruna, this webinar recording will give you some insight into how gINT Scripts can be used to do this.
Thanks Jesse. I watched your video. I was wondering how we can merge core photos to same log using script ? Also, is there any way to change EOH remarks within script ?
Hi Aruna,
If you are asking how to generate the core photo report from the script... you would need to add a section into the overall script to output the core photo - ie after the section of the script to output the logs.
If you are wondering how to import the core photos into gINT... as you are probably aware, you would typically only include a path to the photo file location in gINT (rather than importing the actual files). If you wanted to automate the import of a batch of photos, you could do so with gINT Rules using some logic based off file naming or folder organization to link them to the correct records in your gINT database. I'm not sure you could do it just with gINT Scripts.
Typically EOH remarks would be stored directly in the database or be generated by an expression in your report. If for some reason, you wanted to pass them in through a gINT Script, you could have a Report Variable for your EOH remarks and update that in the Script. There are examples in gINT Help of how you can use Report Variables in gINT Scripts.
Thanks Jesse. I wanted always have EOH remarks below depth in my well log whereas EOH would be either above or below depth in my cored and non-cored log. As I am trying to generate all logs using one script, I wanted to change EOH below depth if EOH is marked as "above depth" in point tab while running script.
I am not very good at Report Variables. Do you have an example script which gINT can change EOH remarks ?
Thanks again
It sounds like Phil has suggested Datgel can support this. But, in general, this sounds like something better managed directly through Report Design rather than a Script. There are many different ways EOH notes could be set up in your Reports, so an exact solution would depend on the specific scenario. But please see the article in gINT Help on "Text Below Last Line" which will give more insight.
Thanks Jesse
I would have to agree with Jesse that the best way to manage the eoh issues is in the log itself rather than via a script. The primary reason is that if you print the log manually without the script it will be different.
A hypothetical example of what you can do is provided below. This example uses made up table and field names and is generated from my memory (ie I did not test it in gINT to see if it works) so it may be missing commas, missing delimiters have incorrect spellings, etc.
It is assumed that you gave separate tables for Soil, Rock, Photos, and Well. You have 4 log formats to present the data: soil (or non core log), rock (or core log), pictures, and well
The below log field of the soil log would contain:
<<IIf(<<Count(<<Rock.Depth>>)>> > 0,_ "Continued on Core Log",_ End of boring at <<Max(<<Soil.Botom>>)>>_ <<IIf(<<Count(<<Well.Depth>>)>> > 0,_ <<cr>>See Well Log for well installation details_ )>>_ )>>
The above log field of the rock log would contain:
Continued from soil log
The below log field of the core log would contain:
<<ListBuildSepTrim(<<cr>>,_ End of boring at <<Max(<<Rock.Bottom>>)>>,_ <<IIf(<<Count(<<Photos.IdNumber>>)>> > 0,_ <<cr>>See Photo Log for core box photos_ )>>,_ <<IIf(<<Count(<<Well.Depth>>)>> > 0,_ <<cr>>See Well Log for well installation details_ )>>_ )>>
The below the log field of the well log would contain:
End of boring at <<MaxValue(_ <<Max(<<Soil.Bottom>>)>>,_ <<Max(<<Rock.Bottom>>)>>_ )>> See soil _ <<IIf(<<Count(<<Rock.Depth>>)>> > 0,_ and rock _ )>>_ log for strata description
Your script would then have the following straight forward logic:
1. Print soil log
2. If there is rock data, print the rock log
3. If there are pictures, print the picture log
4. If there is well data, print the well log
Again this is just a hypothetical example of what can be done. It can be as complicated or as simple as you want.
Hope this provides some insight.