I have been trying to create a graph that inserts a fitting or valve into a pipe whenever it intersects with Spaces that meet some company specific criteria. Thus far, I have been able to identify and select all the pipes in the project that intersect with these Spaces, obtain all the desired intersection points between the pipes and spaces, but when using the MEPFitting.ByPointsAndCurve node from the MEPover Dynamo package to actually insert the valve, I get inconsistent results. A few minutes ago, I ran the graph on a project, and it did exactly what I wanted. But when I “un-did” the graph, restarted it, and ran it again on the exact same model, it only worked for 50% of the pipes. Same graph, same model, within minutes, but different results.
When I test my graph on a small test project (~2 spaces and ~12 pipes) it seems to work every time with valves being placed on the intersection points while also inheriting the host pipe’s system type. However, when I run the graph on a larger scale project (~100 spaces and ~1,000 pipes) I only get a few successful valve placements and rarely will they inherit the host pipe’s system type. The error I get within the MEPFitting.ByPointAndCurve node during these trials reads “Warning: List indices must be numeric.”
Any thoughts on what might be wrong or causing these issues with the graph?
I can only assume that the problem may be related to one of the following things:
User error. This usually seems to be the most likely option…
Timing. With a lot of information, and cross products being passed through the graph, maybe nodes are processing information prematurely, incorrectly, or in other unexpected ways.
Inconsistent or ambiguous Data Types. In some of my research, I’m come across instances where Dynamo was possibly interpreting data inconsistently. Maybe there is some place in the graph where the data being generated is not explicitly one type or another?
Possible random node outputs. I know the Element.Parameters node used to rearrange the results in a different way every time it was run. Maybe there is some other node that behaves inconsistently?
I have already spent a good bit of time trying to test and troubleshoot this issue, and I think I have officially exhausted all of my ideas. I respect your time, but any help or advice that you could lend on the issue would also be greatly appreciated.
Other Forums I found helpful in the creation of my graph: