SAC Horizontal Daylight not Catching

[jmartt]

I have a condition where there's supposed to be a horizontal daylight. It works properly as long as it catches, but for one area, the decision point is below existing grade and the existing surface climbs up and away so it never catches.

What I'd like to do is say "if there isn't a daylight, find the most-horizontal line possible to daylight" But that seems like it would be really hard to do.

I'd settle for "if there isn't a daylight, go out ten feet and find the existing ground elevation and daylight there."

I thought I was being clever when I used my Slope to Surface Point "P2" as a decision: "if p2.isvalid is false, then go out ten feet and daylight". 

But I get an error "P2 & L2: Unable to get the intersection point with the surface target". (Well, duh!)

So how in the world would I do this?

[jmartt]

I have a condition where there's supposed to be a horizontal daylight. It works properly as long as it catches, but for one area, the decision point is below existing grade and the existing surface climbs up and away so it never catches.

What I'd like to do is say "if there isn't a daylight, find the most-horizontal line possible to daylight" But that seems like it would be really hard to do.

I'd settle for "if there isn't a daylight, go out ten feet and find the existing ground elevation and daylight there."

I thought I was being clever when I used my Slope to Surface Point "P2" as a decision: "if p2.isvalid is false, then go out ten feet and daylight". 

But I get an error "P2 & L2: Unable to get the intersection point with the surface target". (Well, duh!)

So how in the world would I do this?

[Jowennl]

Hi Jeff,

Just an idea, please try using Conditional Cut and Fill then add subassembly to suit what you need.

Please visit this <thread link> and check out my post number 3. This may give you an idea or guidance.

You may want to do conditional cut fill subassembly and use any daylight subassembly or slope to surface subassembly then you can attach what you need as condition is met.

Cheers,

Jowenn

[Jowennl]

Hi Jeff,

Just an idea, please try using Conditional Cut and Fill then add subassembly to suit what you need.

Please visit this <thread link> and check out my post number 3. This may give you an idea or guidance.

You may want to do conditional cut fill subassembly and use any daylight subassembly or slope to surface subassembly then you can attach what you need as condition is met.

Cheers,

Jowenn

[jmartt]

Update: Upon reviewing the section through this area, it appears that the corridor IS going out ten feet and daylighting. It is doing what I want it to do. But I'm still getting that error. Is there a way to get rid of or bypass this error message?

[jmartt]

Update: Upon reviewing the section through this area, it appears that the corridor IS going out ten feet and daylighting. It is doing what I want it to do. But I'm still getting that error. Is there a way to get rid of or bypass this error message?

[jmartt]

Thanks, Jowenn. But I've got the conditional built-in to the SA. (The only difference between the two conditions is that one will put a "Daylight_Fill" code for the catch point and one will put the "Daylight_Cut".)

As I said in my update I was writing as you were answering, it does appear to do what I want. I'm just getting that error. It's like it sees the error, reports it, and then carries on doing the next step just fine.

I suppose I can live with the error message. There's another one in the corridor that says the intercept is not found, using a different daylight SA, but it clearly IS finding it. So maybe the error messages are just something to shrug off.

[jmartt]

Thanks, Jowenn. But I've got the conditional built-in to the SA. (The only difference between the two conditions is that one will put a "Daylight_Fill" code for the catch point and one will put the "Daylight_Cut".)

As I said in my update I was writing as you were answering, it does appear to do what I want. I'm just getting that error. It's like it sees the error, reports it, and then carries on doing the next step just fine.

I suppose I can live with the error message. There's another one in the corridor that says the intercept is not found, using a different daylight SA, but it clearly IS finding it. So maybe the error messages are just something to shrug off.

[Jowennl]

Hi Jeff,

I checked your pkt and it is already showing  an error in the event viewer. Please check if by adding slope will fix the error. Please see attached revised PKT.

( Cause of Error )( Try this if it will work )

Cheers,

Jowenn 

[Jowennl]

Hi Jeff,

I checked your pkt and it is already showing  an error in the event viewer. Please check if by adding slope will fix the error. Please see attached revised PKT.

( Cause of Error )( Try this if it will work )

Cheers,

Jowenn 

[jmartt]

It does cause an error. But only if it doesn't find the daylight with a horizontal line. Or at least this is how it appears. In all cases where it can daylight horizontally, it models correctly and gives no error. And in the one area where it doesn't find a horizontal daylight, it gives an error but then goes and does my forced daylight at 10' anyway.

That error in the event viewer you've pointed to I'd attribute to a horizontal line never intersecting another horizontal line (the "EG" in the SAC.) In the model, it does usually intersect.

[jmartt]

It does cause an error. But only if it doesn't find the daylight with a horizontal line. Or at least this is how it appears. In all cases where it can daylight horizontally, it models correctly and gives no error. And in the one area where it doesn't find a horizontal daylight, it gives an error but then goes and does my forced daylight at 10' anyway.

That error in the event viewer you've pointed to I'd attribute to a horizontal line never intersecting another horizontal line (the "EG" in the SAC.) In the model, it does usually intersect.

[mathewkol]

If you first use an auxiliary point that attempts a daylight, you should receive no error. After that, use a decision, if the aux point is valid, the horizontal daylight is possible, then add a real point. If not, go out 10 feet.

[mathewkol]

If you first use an auxiliary point that attempts a daylight, you should receive no error. After that, use a decision, if the aux point is valid, the horizontal daylight is possible, then add a real point. If not, go out 10 feet.

[jmartt]

@mathewkolThat was a great idea. I tried it. I went to seek daylight at 0% with AP17. Right under that, a Decision if AP17.isvalid= true then follow it with real points and links. If false, then go out ten feet and daylight there.

The corridor modeled the same way: found the daylights where available, forced it at ten feet otherwise. But it still gave me an error. It just changed to "AP17: Unable to get the intersection point with surface target".

But it works, so I'm content to live with the error message.

Thanks.

[jmartt]

@mathewkolThat was a great idea. I tried it. I went to seek daylight at 0% with AP17. Right under that, a Decision if AP17.isvalid= true then follow it with real points and links. If false, then go out ten feet and daylight there.

The corridor modeled the same way: found the daylights where available, forced it at ten feet otherwise. But it still gave me an error. It just changed to "AP17: Unable to get the intersection point with surface target".

But it works, so I'm content to live with the error message.

Thanks.

[mathewkol · Accepted solution]

Ok, it's easier than we even hoped.  See image.  There is a toggle at the very bottom where you can choose not to display errors.

[mathewkol · Accepted solution]

Ok, it's easier than we even hoped.  See image.  There is a toggle at the very bottom where you can choose not to display errors.

[jmartt]

Ha! I can see how that'd be a dangerous little button to press.
That wasn't the original problem, but that solved the annoyance that the original problem turned into. I'm now building the corridor as intended without error warnings. Thanks a lot!

[jmartt]

Ha! I can see how that'd be a dangerous little button to press.
That wasn't the original problem, but that solved the annoyance that the original problem turned into. I'm now building the corridor as intended without error warnings. Thanks a lot!