Topic: C3D 2012 - Apply rules to more than 1 pipe

[Matt__W]

Is it possible to apply a rule to more than 1 pipe at a time?  Or even the entire network?  I don't see any way to do this or any options that might control this.  Am I missing sumpin'??

[BlackBox]

Code - Auto/Visual Lisp: [Select]

1. (defun c:ARM () (c:ApplyRulesMultiple))
2. (defun c:ApplyRulesMultiple (/ ss)
3.   (princ "\rApply rules to multiple Civil 3D parts: ")
4.   (while (setq ss (ssget ":S:E:L" '((0 . "AECC_PIPE,AECC_STRUCTURE"))))
5.     (sssetfirst nil ss)
6.     (command "._ApplyRules")
7.     (sssetfirst nil nil)
8.   )
9.   (princ)
10. )
11.  

... You can easily refine this to process a single selection set, etc..

[Matt__W]

So in other words.... I WASN'T missing anything.   

Thanks for the option/solution!

[BlackBox]

Thanks for the option/solution!

No worries; I'm happy to help.

... You can easily refine this to process a single selection set, etc..

Here's another adaptation in kind:

Code - Auto/Visual Lisp: [Select]

1. (defun c:ApplyRulesMultiple (/ ss ss2 i)
2.   (princ "\rApply rules to multiple Civil 3D parts: ")
3.   (if (and (setq ss (ssget "_:L" '((0 . "AECC_PIPE,AECC_STRUCTURE"))))
4.            (setq ss2 (ssadd))
5.       )
6.     (repeat (setq i (sslength ss))
7.       (sssetfirst
8.         nil
9.         (setq ss2 (ssadd (setq e (ssname ss (setq i (1- i)))) ss2))
10.       )
11.       (command "._ApplyRules")
12.       (sssetfirst nil nil)
13.       (setq ss2 (ssdel e ss2))
14.     )
15.   )
16.   (princ)
17. )
18.  

[Matt__W]

Thanks for the option/solution!

No worries; I'm happy to help.

... You can easily refine this to process a single selection set, etc..

Here's another adaptation in kind:

Code - Auto/Visual Lisp: [Select]

1. (defun c:ApplyRulesMultiple (/ ss ss2 i)
2.   (princ "\rApply rules to multiple Civil 3D parts: ")
3.   (if (and (setq ss (ssget "_:L" '((0 . "AECC_PIPE,AECC_STRUCTURE"))))
4.            (setq ss2 (ssadd))
5.       )
6.     (repeat (setq i (sslength ss))
7.       (sssetfirst
8.         nil
9.         (setq ss2 (ssadd (setq e (ssname ss (setq i (1- i)))) ss2))
10.       )
11.       (command "._ApplyRules")
12.       (sssetfirst nil nil)
13.       (setq ss2 (ssdel e ss2))
14.     )
15.   )
16.   (princ)
17. )
18.  

Thanks!  Saves me the trouble of having to do it myself!  #OutOfContextThread

[mjfarrell]

APPLYRULES
Select up slope part in plan (Pipe or Structure):

This will do the entire network; if used properly

[BlackBox]

APPLYRULES
Select up slope part in plan (Pipe or Structure):

This will do the entire network; if used properly

Interesting, that is only displayed when invoking the ApplyRules Command prior to selecting of a Pipe or Structure.

For the reverse (selecting a Pipe or Structure first), this is what's displayed:

Code: [Select]

Command: ApplyRules
Rules successfully applied to 1 network parts.

... not sure why first selecting 'up slope part' is so critical, when that information can be extracted programmatically.

[Jeff_M]

... not sure why first selecting 'up slope part' is so critical, when that information can be extracted programmatically.

This may be of interest to you:
http://beingcivil.typepad.com/my_weblog/2012/01/cover-slope-pipe-rule.html

When I saw the lisp you posted, my first reaction was "I'm not so sure that's a good idea...". But maybe it works for you ok, I just recall all the behind the scenes stuff from that article making it seem like a bad idea.

[BlackBox]

... not sure why first selecting 'up slope part' is so critical, when that information can be extracted programmatically.

This may be of interest to you:
http://beingcivil.typepad.com/my_weblog/2012/01/cover-slope-pipe-rule.html

When I saw the lisp you posted, my first reaction was "I'm not so sure that's a good idea...". But maybe it works for you ok, I just recall all the behind the scenes stuff from that article making it seem like a bad idea.

Too bad Autodesk didn't think this one through (and myriad others pertaining to pipes in general)... It's kind of hard to automate any pipe related workflow (albeit with LISP) when so much is incumbent upon the user starting on one side of the pipe network for it (the Civil 3D Command) to function properly. *Kicks dirt*

[Jeff_M]

Actually, this is one piece that makes complete sense to me. Back before C3D, or LDT, or...., when we designed on paper, we most always started our design at the upstream point, using minimum cover, and worked downstream. We then analyzed how that fit whatever we had to tie in to and made adjustments accordingly. I think the C3D methodology is about the same. Now if you randomly select pipes and expect it to adjust each based on those connected to it, but then one later changes due to being later in the selection order, it would be a nightmare to control.

You do know you can select the upstream part, then select the LAST downstream part, and C3D will autoselect all those in between? This makes it so with 2 picks you can apply rules to a whole section.

[reno]

Interesting, that is only displayed when invoking the ApplyRules Command prior to selecting of a Pipe or Structure.

if you select multiple pipes/structures and run the command it will ask you to select the upstream part. if you have only one part selected, the rules are applied to that part. if you have no parts or multiple parts selected, it will ask you which parts to apply the rules to.