Community
Today I have to figger-out how to code this daylight condition.
Which I've thought a bit about and I think my problem comes down to my current inability to say (code) "If there is no catch..."
How would I say that?
Thanks in advance, wizards.
Today I have to figger-out how to code this daylight condition.
Which I've thought a bit about and I think my problem comes down to my current inability to say (code) "If there is no catch..."
How would I say that?
Thanks in advance, wizards.
Okay, so now of course I want to move that decision to the hinge point atop the levels of strata.
I've done this before, and had redundant branches to daylight the substrata into the resultant slopes using Intersection: TwoPointsSlope.
But it occurs to me that there may be a more elegant way to do this. I want to have the preferred slope be an input parameter because it'll vary for different regions. But if I can redefine that parameter (when needed) within the SA, using the resultant slope of the (AP1.IsValid is not true) Decision, I could perhaps use the redefined parameter to build the substrata.
But I don't see a "Redefine Parameter" tool. And the "Define Variable" tool doesn't have Slope as an option.
If this isn't possible, I can still get it done with two branches. I just thought if it is possible, I'd save myself untold hours of redundant building of layers.
Okay, so now of course I want to move that decision to the hinge point atop the levels of strata.
I've done this before, and had redundant branches to daylight the substrata into the resultant slopes using Intersection: TwoPointsSlope.
But it occurs to me that there may be a more elegant way to do this. I want to have the preferred slope be an input parameter because it'll vary for different regions. But if I can redefine that parameter (when needed) within the SA, using the resultant slope of the (AP1.IsValid is not true) Decision, I could perhaps use the redefined parameter to build the substrata.
But I don't see a "Redefine Parameter" tool. And the "Define Variable" tool doesn't have Slope as an option.
If this isn't possible, I can still get it done with two branches. I just thought if it is possible, I'd save myself untold hours of redundant building of layers.
@KMercier_C3D, Thank you very much indeed for your help yesterday. I was able to get a SA that works for me. (I've noticed that my "SA"'s seem to be more like full Assemblies.)
I was having some problems with the sideslope catching on EG above the bottom of structural, which sometimes meant I wanted to opt for forcing the daylighting to the existing ditch, but quite often it would be better if I "punched-through" and found a second daylight...And then I found that sometimes I had to find a tertiary daylight, like when the 4:1 "hooked" through the existing shoulder, crossing the EG surface twice. See screenshot of a section where it is utilizing a secondary daylight.
Anyway, when I attempted to do this, I couldn't get the daylight to see past the previous daylight. Like if the first daylight was called P1, and I told it to start at P1 and find daylight again, it would just find P1 again. I found that if I borrowed @Jowennl's method of .0001 and created P2, which I created from P1, cheated down the slope by .0001 and told it to daylight from P2 it worked. See screenshot.
I wonder if there's a better way of punching-through and finding multiple daylights than the one I came up with?
@KMercier_C3D, Thank you very much indeed for your help yesterday. I was able to get a SA that works for me. (I've noticed that my "SA"'s seem to be more like full Assemblies.)
I was having some problems with the sideslope catching on EG above the bottom of structural, which sometimes meant I wanted to opt for forcing the daylighting to the existing ditch, but quite often it would be better if I "punched-through" and found a second daylight...And then I found that sometimes I had to find a tertiary daylight, like when the 4:1 "hooked" through the existing shoulder, crossing the EG surface twice. See screenshot of a section where it is utilizing a secondary daylight.
Anyway, when I attempted to do this, I couldn't get the daylight to see past the previous daylight. Like if the first daylight was called P1, and I told it to start at P1 and find daylight again, it would just find P1 again. I found that if I borrowed @Jowennl's method of .0001 and created P2, which I created from P1, cheated down the slope by .0001 and told it to daylight from P2 it worked. See screenshot.
I wonder if there's a better way of punching-through and finding multiple daylights than the one I came up with?
Forums Links
Can't find what you're looking for? Ask the community or share your knowledge.
Post to forums
