Subassembly Composer- Having multiple options for the targeting existing surface

[juan_m_urena]

I've been stuck on this issue and i am hoping someone can help:

I created a simple V-Ditch assembly using Sub Assembly Composer, I’ve attached it for reference.  My issue is with the end conditions.

My slope going away from the v-ditch must always go up (ie. Flows must drain into the v-ditch).

I want to have 4 Options for the end conditions plus a “do nothing”.

Option 1: Target existing surface going at 3% for a maximum of 10ft (called 3% Short).  If existing surface is intercepted, then draw the end condition then stop.  Otherwise, go to Option 2.

Option 2: Target existing surface going at 50% for a maximum of 10ft (called 50% Short).  If existing surface is intercepted, then draw the end condition then stop.  Otherwise, go to Option 3.

Option 3: Target existing surface going at 3% for a maximum of 100ft (called 3% Long).  If existing surface is intercepted, then draw the end condition then stop.  Otherwise, go to Option 4.

Option 4: Target existing surface going at 50% for a maximum of 100ft (called 50% Long).  If existing surface is intercepted, then draw the end condition then stop.  Otherwise, go to Option 5.

Option 5: Do nothing.

From my trouble shooting, the problem may be in the decisions.  The code for the decisions is in this format “P2.DistanceTo("AP2") <10”

P2 is the edge of the v-ditch.

AP2 is an imaginary point going from the edge of the v-ditch at 3% seeking the existing surface.  If AP2 does not find existing surface, then what is the distance ("value") between P2 and AP2?  Infinity?  Zero?  Null?  The decision doesn’t seem to know how to compare that "value" with the integer 10. 

@ecfernandez

I would prefer to learn how to accomplish this using subassembly composer.  I think the process would be useful in the future.  However, if there is a simpler way in autodesk’s built-in assemblies then I am ok with that too.

[ecfernandez]

Hi @juan_m_urena, thanks for reaching out to me. Sure, I can help you, but unfortunately, I couldn't find your file (PKT) attached to the drawing.  For the time being, I'll check the conditions you mentioned, and I'll come back with a few comments about it.

Best regards!

[juan_m_urena]

@ecfernandez 

[ecfernandez]

Thanks for the file. I'll check it tomorrow and let you know. Regards!

[ecfernandez]

Hi @juan_m_urena, I hope you're doing fine. I have attached the PKT file. See it and let me know if that is what you were looking for. I hope I did not misunderstand any of your conditions, but if I did, I think this PKT is a good beginning for you to fix what you want and test it in C3D. I worked with SAC 2024. 

[juan_m_urena]

Thank you, @ecfernandez, for your response.  However, I am getting an error message when I try to open the *PKT file (error message:  Invalid .pkt file.  The packet is missing a .dll file.  Only .pkt files created with Autodesk Subassembly Composer are acceptable.).  I am using Autodesk Subassembly Composer for Autodesk Civil 3D 2021.  Do you have any suggestions on what to do?  or can you send me a screenshot of the flow chart?

[juan_m_urena]

@ecfernandez   this is the error that I received.

[ecfernandez]

Unzip the file. I didn't change the file extension but compressed it as zip. Unzip it and open it again with Subassembly Composer 2024.

Regards!

[juan_m_urena]

Unfortunately, my company does not give me access to SAC 2024. Can you send me a screenshot/jpg of the flowchart that you created?

[ecfernandez]

 

[juan_m_urena]

Truly. thank you for all of your time and effort.

[ecfernandez]

Happy to help @juan_m_urena, regards! 

[juan_m_urena]

@ecfernandezI believe I have all of the information to recreate the flow chart, except for 2 pieces of information. 1) what is the expression for the Decision Box (is it the same as the original; :P2.DistanceTo("AP1") <10")?    and      2) what is the expression for the first variable definition: "ConditionToUse <string>"

[ecfernandez]

Hi @juan_m_urena, the decision is just to check that P2 is effectively under the terrain and there is a chance to generate a cut daylight, otherwise, this subassembly does nothing. 

The expression for the first variable is not important because it is later changed after the evaluation of the conditions you provided. However, a default value must be set, and I put "Option1"

[juan_m_urena · Accepted solution]

@ecfernandezyour flow chart worked perfectly.  I learned a lot by studying your flowchart (approach, strategy, and code).  I am certain I will use this new knowledge in the near future.  Thanks again for your time and help.