Hello,
Please refer to the file attached.
I noticed GINT is trying to provide N values throughout the depth of the hole, including SS (split spoon) and AU (auger) intervals. At the auger intervals, obviously I did not record any blowcounts, therefore GINT is printing a dashed line.
Anyone knows how to show this area as blank instead of show dashed lines?PDF
There are 2 ways to acomplish this,
1. modify your text expression in in the text vs depth entity to return nothing for samples that have no blow counts. a text expression such as:
<<HasData(<<Sample.Blows_1st>>,_
[your current expression for assembling the blow counts and SPT N would go here],_
,_
)>>
This HasData function checks to see if anything is entered in the blows_1st field and prints the first argument if there is data and the second argument (in this case nothing) if there is no data.
2. use the Body Data Output Condition in the configuration tab of the text vs depth entity. You would enter an expression that evaluates to true for the case that you want the text to print. An expression similar to:
<<Calc(<<Sample.Type>> = "SS"}>>
should return true if the sample type is SS causing the entity to print; anything else will return false and the data will not print.
Obviously these expressions need to be adapted to your specific data structure and data
Thanks szang.
I tried both options. I both options it did not print any N values (including the ones from SS samples). Also I noticed that somehow the lines between layers got shifted. I don't know if am using the Hasdata function properly. Please advise.
See attached.
PDF
As I said my example was an example. You need to adapt it to your specific data fields and requirements. In this case the name of your blows field appears to be <<SAMPLE.Blows 1st>>; my example used <<sample.blows_1st>> which is not the same thing. Also you need to remove the extra blank lines in your expression as these are being returned as carriage returns on the log which is causing your boundary lines to be bumped down. I have tried to type what the code should look like based on the information in your pdf in the code window below. HOWEVER, since I did not enter it in an actual entity and do not have your data structure I do not guarantee this will work verbatim. I may have missed a delimiter or parenthesis or comma or underbar continuation somewhere. Further, your existing code for SPT and N value has some potential flaws but I tried to reproduce it verbatim with minor syntax corrections
<<HasData(<<SAMPLE.Blows 1st>>,_ <<SAMPLE.Blows 1st>>-<<SAMPLE.Blows 2nd>>-<<SAMPLE.Blows 3rd>>-<<SAMPLE.Blows 4th>> [_ <<IIf(<<isnumeric(<<SAMPLE.Blows 1st>>)>> And _ <<isnumeric(<<SAMPLE.Blows 3rd>>)>>,_ <<calc(<<SAMPLE.Blows 3rd>> + <<SAMPLE.Blows 2nd>>)>>,_ <<FirstData(<<SAMPLE.Blows 3rd>>,_ <<SAMPLE.Blows 2nd>>,_ <<SAMPLE.Blows 1st>>,_ )>>_ )>>_ ]_ ,_ )>>
Thanks szang. It worked.
However, the extra lines are showing up. See the file attached. I noticed the extra lines started showing up after the refusal depth.
Do you have any suggestions?
My guess is as follows:
Your extra lines show up at 24' and continue past the end of the hole by about the same. This indicates to me that you have a boundary line depth expression set to something like <<Sample.depth>> + <<SAMPLE.length>> (insert your own actual field names here) since your sample length is in inches and the depth is in feet the first sample generates a bottom boundary line at 0+24=24 feet. The auger sample generates a bottom boundary line at 2+36=38 feet, the second sample generates a bottom boundary line at 5+24=29 feet. And so on. That is exactly where your extraneous lines are on the sample you sent. It is not a function of your refusal blow, that is merely a coincidence.
You will need to modify your boundary line depth expression in the boundary line tab of the entity to something like <<Calc(<<SAMPLE.depth>> + (<<SAMPLE.length>>/12))>> (Again, this is an example, insert your own field names as appropriate)
You likely have a top boundary line depth expression that is just <<SAMPLE.depth>>. This is placing boundary lines at the correct location. Since your sample record is continuous (ie the bottom of one sample is exactly equal to the top of the next sample) the entity will actually generate 2 lines at the same location when working properly (the bottom of one sample will be in the exact same location as the top of the next lower sample). You actually only need one line but you can keep both for the case when your sample record is not continuous.
Thanks szang, It worked.