tt-acm / dynamoforrebar Goto Github PK

Suggestion as improvement: it would be great having an option to toggle the "View Visibility State" of the generated rebars. This because of if you set it once for your bars, and change the number of bars with your Dynamo script, then the "View Vis State" change back to "unchecked". See screenshot below.

When working with the Rebar.FollowingSurface on a trapezoidal surface, I would expect the lines getting trimmed at the surface edge, which is not yet done. See screenshot below.

@bhowes-tt do we have a license header for this case?

Beams are working fine as rebar hosts, but Volumes don't.

I've used the following surface sample file. rebars from curve or container are created, but far far away from the host.

The result vary depending on the project units. best result is centimeters.

worth mentioning project was created from French template

Set up a RTF project in this solution that runs system tests on the package's sample files. Today's release of Dynamo 0.8.2 seems like as good a reason as any to lace this up!

Have a look at the Energy Analysis or Dynamo SAP project for a precedent.

User feedback:
In Revit, apparently the Sofistik content that can be integrated in a project (when initializing the Sofistik rebar tools), gives a conflict when applying a Dynamo script with the Rebar package from TT.
The rebar is not generated at all, and in Dynamo an internal error is pointed to. Also the Sofistik tools give an internal error message at that moment.

• Polysurface support creating polyline based rebar. TT will check how Polysurfaces are behaving etc.

I miss a setting where I can choose "None" for the Rebar Hook Type. Not all rebars need to have hooks at the ends.

User request: using a Cover Input instead of an offset

User feedback:
After switching between the Vectors, “Select Face” becomes unusable.
I cannot return it to its original state.
Recreating the box will, of course, reinstate the functionality.
You can notice it in both videos.

Cut a set of exisintg Bars in a container using a Reference Plane.
Probably the Bars need to be replaced by new instances.
First use the ComputeCurve Method or the GetCenterlineCurves to access the Bars Geometry.
Cut the retrieved Curves by getting the intersection point with the plane.
Recreate Bars using the new intersected geometry.

User feedback:
I miss functions that can call a Rebar shape object, in order to place stirrups in beams i.e.
Now the workaround with Dynamo is to build a custom curve for that basic shape 21.

This would help people to build ie stirrups with var heights, or stirrups in circular forms (i.e. water purification stations)
(path reinforcement is not a solution here as it is limited to system floors and walls, and not work on custom components, not even components built in place with Wall category…)

Something else that popped up during testing is that when the scripts needs rerun due to changes (ie. Number of curves, changing reference faces, …) the element binding is not working properly. The initial generated rebar is not deleted or changing. So the nodes generate new rebar next to the existing. Which is very uncommon for Dynamo with Revit
This was tested with the package v 0.1.3

I can't find drop down nodes after installing the package (0.3), they are only in the sample dyn files. Bizarre??

I keep getting: Warning: RebarContainer.ByCurve operation failed.
An internal error has occurred.

I am using Revit 2016 with Dynamo 8.2...
Just installed 0.8.0 and tried again but still got an internal error from both rebar container and single rebar.

1. TT will open source their repo, and will publish an in-process package to the Dynamo Package Manager as soon as this team agrees it is appropriate to do so. We discussed the possibility of a private release, and it was decided that an early, open beta testing phase is preferable. This will be discussed again during the next progress meeting.

I received some testing geometries from Autodesk, some kind of multi surface families... they aren't really matching the original scope of work where we had to rebar single surfaces. Well we could try to create rebars along multiple surfaces, like polyline bars. But as I already mentioned, they haven't been scope of work.

Hi, it seems that applying the Offset value on the Rebar.FollowingSurface node doesn't influence the radius of a curve when applying on a single curved wall. In an earlier post I read that offset might be interpreted as cover (?). If that is the plan, then this should not just shift the rebar lines with the offset value, but it should change the radius of the rebar lines instead. If not you will get the effect as below, where the rebar objects are not concentric with the wall radius.

If the offset is not intended to be seen as "cover", how can you get then the rebar objects concentric with the curved wall?

I seem to be getting the same error even just using a selected edge as a curve. Probably user error!

Warning: Rebar.ByCurve operation failed.
An internal error has occurred.

Any ideas.

Thanks

• Shorten Bars Node needs to use a perpendicular offset instead of a distance along curves

Node Icons need to be provided.

1. TT will follow up in a separate email thread regarding the support of imported file types (like. SAT) and other native Revit object types as objects that are able to host rebar containers. There was some discussion about the correct workflow for importing SAT files, but it was decided to cut that short and follow up via email.

Seems like there is now way of creating a rebar from a spline or nurbs curve, so all our curves need to be arc based!

“RebarContainer.ByCurve” Worket for curved wall, but it didn’t like double curved (skewed).

Hi @anagpuyol , @bhowes-tt
our new "Select Edges" Node allows us to easily recreate imported geometries with adaptive components. Maybe this is helpful in the Dynamo lectures.

The perpendicular Node doesn't consider different directions.
There needs to be a flip switch just in case.

Hi, it seems that the Rebar and RebarContainer by Curve is only working also on curves. But when you use Dynamo, it happens a lot that the result is a line. Apparently this input is not accepted by the Rebar creation nodes. Any workaround for this?
See script below. In there in want to model rebar from one face to the other using surface divsion nodes. Apply this on a model with two different sized rectangular faces which are parallel to each other. (ie. blended column with variable base and top).

What is remarkable besides that, is that the output of the valid nodes, is not showing when the Rebar package nodes show an error.

User Request: Why does the input of the node Rebar.ByCurve say curves as input, when it obviously just handle one curve?

Quoting Autodesk: "For the question regarding unbound curves, I wasn’t sure what our behavior was here. So I did a little test. It seems that we do allow you to query a parameter location outside the 0->1 domain and you can get a point at that location “on” the curve. But we do not use the unbound curve in operations like intersections (see the attached image). So, the short term answer to your second question is, no, we don’t support unbound curves in the way that you would like. The longer term answer is that we need to see whether there are apis available internally on the geometry library that will allow us to support unbound curves for project and intersection operations."

Prodive mor Input Ports for Hook Type, Bar Style, etc.

User Feedback:
Currently the implementation covers design intent or concept and NOT detailed design. For detail design we need the ability to place shapes, within given ranges (or areas) with the applicable spacing and all the relevant options (such as staggers, alternate bars reversed etc). This is a very good start but there is a long way to go for (dare I say it) those areas where intent is not adequate.

User feedback:
I started testing Dynamo for Rebar and would like to share with you the information I have so far.

First of all I had to install Dynamo 0.8 as the nodes don’t work for more recent versions.
The combo boxes I have available in 0.8 aren’t available in 0.9 (as below).

1. TT will explore possibilities related to setting properties of rebar[s] within a rebar container. Upstream and downstream solutions [for parametrically setting rebar properties] were discussed – Ideally TT’s solution could be used both upstream and downstream of a rebar container node.

Structural Containers are currently being recreated each time the dynamo runs.
This needs to be optimized reusing the existing container.

I upgraded to daily build 0.9 and somehow rebars won't generate. Just showing blue lines in the revit model

Maybe we should implement H/V bars aswell, since they are more realistic than the polar arrangement.

User feedback:
I have downloaded Dynamo for Rebar and tested it in Revit 2016 with Dynamo 0.8.2. Still figuring out why this is not working. Based on the blog post, the select surface has a different Element ID than Host Element… This is what I don’t get it.

I've created the same nodes as showed in http://core.thorntontomasetti.com/dynamo-for-rebar-is-now-available/
But in stead of using a 'number' node for the number of curves I've used a 'number slider' node. When Dynamo is running automatically I get a fatal error when changing the number slider.

• Set a standard rebar normal vector and always apply true to the create & use existing shape parameters.

User feedback:
If the object’ coordinate system is aligned with the global coordinate system I can find a vector which will generate the reinforcement as I designed it.
Once I Rotate the element, none of the vectors work.
I’m not quite sure how it should work, if it’s a bug or just something I missed.

Somehow the U,V Parameters are based on a perpendicular rectangle?

Dropdown Definitions following the RevitDynamo Implementation are not working.
They appear empty on the canvas. Code is executed correctly and the Items List is populated.
Does anyone know more about this in Dynamo? @bhowes-tt , @anagpuyol ?

1. TT will confirm that trimmed surfaces (including surfaces with holes cut in them) and surfaces with double curvature are supported - that hosted rebar is properly created for those surface conditions.

If I create rebars somewhere with Dynamo and use the same parameters and nodes to create new rebars elsewhere, Dynamo will delete the previously create rebar before creating the new bars. Completely inefficient workflow on project. This is a Dynamo-Revit issue, but I post it here since it affects rebar workflow very much.

(Similar to any other Revit Element Creation Node we need Revit Bake functionality in Dynamo.)

My guess is that your method doesn't produce a node that returns a Type object. It seems to be returning a Name (string) of the selected value. Is that intended use of this method?

Create Bar Labels using a Rebar Label Node.

Whenever I run a script Dynamo will recreate rebars I already modeled. This is undesirable as it effects performance. If nothing changed - neither should Revit.

(Similar to any other Revit Element Creation Node we need Revit Bake functionality in Dynamo.)

There is no select element Node to get an ElementId for rebar host.

Hi @bhowes-tt ,
setup works great. One question: if I'm using an array output from a Node to plug it into an other Node, Dynamo doesn't run the component multiple times for each element in the array. Is there a way to force it to do that?