I'm trying to present a dynamic constant on a log that is not related to depth. For example, I want to show calculated Ic from a CPT on a Plot vs Depth log and overlaying the cohesive/non-cohesive cut off as a vertical line, I need this line to run from the very top of the log to the very bottom.
If I use the CPT depth, the cut off line only draws to the depth of the CPT and not the page.
I need the vertical line to by dynamic and changeable by the user so unable to draw it directly on the plot.
Is there a way to enter multiple depth values into the depth expression field instead of referencing a field in the database?
Hi Ryan,
I think I've done something similar for a Dilatometer plot. I don't think you can plot a vertical line on your Plot vs Depth entity. What I've done to get vertical lines is to create a separate Vertical Line To Depth entity which lines up with a specific value in my plot.
Since you want it to be dynamic, you'll need to add a report variable which users enter the specific Ic value at output time. This becomes a bit more complicated as you will need to use some math. You should probably specify a default Ic value so that if no one enters anything, the default appears.
For your expression, you'll need to determine what X coordinate on paper corresponds to your specified Ic value. So if your Plot vs Depth log is 2 inches wide starting at X=3, then you need figure out the X coordinate for each Ic value, and then you can back out an expression for Ic value to X coordinate.
Using the Vertical Line to Depth entity, to that location with the Top Depth Expression as 0 and Bottom Depth Expression as either <<PointID.HoleDepth>> or <<Max(<<CPT.Depth>>)>> - whichever convention you're using.
You can position the Vertical Line to Depth entity to match your Plot vs Depth entity and use your expression within the Output Override X field so when it lines up in the correct spot during printing.
Hi Allan,
Many thanks for your reply and suggestion.It seems like such a logical function, I am surprised there is not a easier method within gINT.
Cheers