Tag Archives: Curve

DesignScript Curve Translation,Geometry.Curve.DistanceAtPoint#15– Code to Node to Code

Hi Everyone:

This is the fifteenth, in a series of forty-nine curve file translations. The file, Geometry.Curve.DistanceAtPoint.ds, is from the DesignScript Editor (DSE) Sample files.

Geometry.Curve.DistanceAtPoint.ds#15

Geometry.Curve.DistanceAtPoint.ds#15

After opening, copying the script from the DSE and pasting it into DSS, we see that this will again be a short translation.

Geometry.Curve.DistanceAtPoint#15

Geometry.Curve.DistanceAtPoint#15

Quickly, the translation looks like the graph node canvas that is shown above. After developing the nodes properties and definitions further, it will look similar to the layout below.

Geometry.Curve.DistanceAtPoint#15a

Geometry.Curve.DistanceAtPoint#15a

After the translation,  the “Code to Node” operation is performed.

Geometry.Curve.DistanceAtPoint#15b

Geometry.Curve.DistanceAtPoint#15b

The graphic that is generated from the file is shown below.

Geometry.Curve.DistanceAtPoint_Graphic Window

Geometry.Curve.DistanceAtPoint_Graphic Window

The files can be downloaded from the links below.

Geometry.Curve.DistanceAtPoint#15

Geometry.Curve.DistanceAtPoint#15a

Geometry.Curve.DistanceAtPoint#15b

Thanks for looking.

T!M

 

DesignScript Curve Translation,Geometry.Curve.CoordinateSystemAtEqualArcLength#12– Code to Node to Code

Hi Everyone:

This is the twelfth, in a series of forty-nine curve file translations. The file, Geometry.Curve.CoordinateSystemAtEqualArcLength.ds, is from the DesignScript Editor (DSE) Sample files.

Geometry.Curve.CoordinateSystemAtEqualArcLength.ds#12

Geometry.Curve.CoordinateSystemAtEqualArcLength.ds#12

This is similar to the last few previous files. Open it in the DSE, copy it to ones clipboard, then open DSS and paste the script into the blank canvas.

Geometry.Curve.CoordinateSystemAtEqualArcLength

Geometry.Curve.CoordinateSystemAtEqualArcLength

After the initial translation shown above, it’s developed into something like shown below.

Geometry.Curve.CoordinateSystemAtEqualArcLength#12a

Geometry.Curve.CoordinateSystemAtEqualArcLength#12a

Satisfied with the translation the “Node to Code” translation takes place as shown below.

Geometry.Curve.CoordinateSystemAtEqualArcLength#12b

Geometry.Curve.CoordinateSystemAtEqualArcLength#12b

The geometry that results from these translations can be viewed in the image below.

Geometry.Curve.CoordinateSystemAtEqualArcLength-Graphic Window

Geometry.Curve.CoordinateSystemAtEqualArcLength-Graphic Window

The files can be downloaded from the links below.

Geometry.Curve.CoordinateSystemAtEqualArcLength#12

Geometry.Curve.CoordinateSystemAtEqualArcLength#12a

Geometry.Curve.CoordinateSystemAtEqualArcLength#12b

Thanks for looking.

T!M

 

DesignScript Curve Translation, Geometry.Curve.CoordinateSystemAtParameter#11– Code to Node to Code

Hi Everyone:

This is the eleventh, in a series of forty-nine curve file translations. The file, Geometry.Curve.CoordinateSystemAtParameter.ds, is from the DesignScript Editor (DSE) Sample files.

Geometry.Curve.CoordinateSystemAtParameter.ds#11

Geometry.Curve.CoordinateSystemAtParameter.ds#11

After opening the file in the DSE, copy the script and paste it into a blank canvas in DSS. The initial translation looks something like shown below.

Geometry.Curve.CoordinateSystemAtParameter#11

Geometry.Curve.CoordinateSystemAtParameter#11

After it has been roughed out. it might be good to use some of the special nodes to further define and clarify the variables and personalize the nodes to aid in reading and translating them.

CodeBlock node

CodeBlock node

First off there is the CodeBlock Node which can be accessed in the Special Nodes category of the library, or more commonly activated by just double clicking in a blank space in the DesignScript canvas.

Driver Node

Driver Node

The Driver Node can be used in lieu of the CodeBlock node to add naming a definition to a variable, in this case 0.1234 is being shown.

Identifier Node

Identifier Node

Then there is the Identifier Node, which adds naming to a node that can serve as a link between a CodeBlock Node and another graph node. As one continues the translation, its usage will provide adequate identification to all the script that was in the DSE sample file.

Geometry.Curve.CoordinateSystemAtParameter#11a

Geometry.Curve.CoordinateSystemAtParameter#11a

Satisfied with the translation, then the “Node to Code” operation follows.

Geometry.Curve.CoordinateSystemAtParameter#11b

Geometry.Curve.CoordinateSystemAtParameter#11b

And the Graphic Window that results from these translations is shown below.

Geometry.Curve.CoordinateSystemAtParameter-Graphic Window

Geometry.Curve.CoordinateSystemAtParameter-Graphic Window

As a reminder to all, again, this translation was done with the Stand-Alone version of DesignScript, yet it still will work as a AutoCAD plugin.

The files can be downloaded from the links below.

Geometry.Curve.CoordinateSystemAtParameter#11

Geometry.Curve.CoordinateSystemAtParameter#11a

Geometry.Curve.CoordinateSystemAtParameter#11b

Thanks for looking.

T!M

 

 

 

DesignScript Curve Translation, Geometry.Curve.Composite.WithTolerence#8 – Code to Node to Code

 

Hi Everyone:

This is the eighth, in a series of forty-nine curve file translations. The file, Geometry.Curve.Composite.WithTolerence.ds, is from the DesignScript Editor (DSE) Sample files.

Geometry.Curve.Composite.WithTolerence#8

Geometry.Curve.Composite.WithTolerence#8

Some may notice that a previous Composite file, Geometry.Curve.Composite.ds#1 has an error which was not only the misspelling of “Geometry,” which is correct in this case, but that the Composite  command did not fully function.

Geometry.Curve.Composite.WithTolerence#8-error

Geometry.Curve.Composite.WithTolerence#8-error

Like in the previous case Composite Curve fails while a single curve doesn’t. So like the previous translations we will make due with what we have and use one of the curves to illustrate the complete translation. Lets take a look at what we have.

Geometry.Curve.Composite.WithTolerence#8

Geometry.Curve.Composite.WithTolerence#8

Here is the general translation above while the specifics of the error and the alternative method is shown below.

Geometry.Curve.Composite.WithTolerence#8-error2

Geometry.Curve.Composite.WithTolerence#8-error2

Note the Block Node that has the implicit leads from the curves. Normally,  because we are trying to use library graph nodes, the alternative “Set Union” for the curves is not shown. In any case the error is quite plainly seen. The alternative is shown below.

Geometry.Curve.Composite.WithTolerence#8a-edited

Geometry.Curve.Composite.WithTolerence#8a-edited

The “BSplineCurve” node was used as the “contextCurve”(s) to develop the properties of the “myCompositeCurve”.

Geometry.Curve.Composite.WithTolerence#8a

Geometry.Curve.Composite.WithTolerence#8a

The completed Node Graph DSS canvas is shown above. (rather, as complete as can be at this time)

On to the “Node to Code” conversion.

Geometry.Curve.Composite.WithTolerence#8b-edit

Geometry.Curve.Composite.WithTolerence#8b-edit

A little editing is in order as highlighted.

Geometry.Curve.Composite.WithTolerence#8b-edited

Geometry.Curve.Composite.WithTolerence#8b-edited

The graphic that is generated from the code is shown below.

Geometry.Curve.Composite.WithTolerence#8-Graphic Window

Geometry.Curve.Composite.WithTolerence#8-Graphic Window

As usual, liberty was taken with adding color and this was done with the stand alone version of DesignScript. The files are available for downloading from the links (DropBox) below.

Geometry.Curve.Composite.WithTolerence#8

Geometry.Curve.Composite.WithTolerence#8a

Geometry.Curve.Composite.WithTolerence#8b

Thanks for looking.

T!M

DesignScript Curve Translation,Geometry.Curve.ClosestPointTo#7– Code to Node to Code

Hi Everyone:

This the seventh DesignScript file in a series of forty-nine curve translations. The file, Geometry. Curve.ClosestPointTo.ds is from the DesignScript Editor (DSE) Sample files.

Geometry.Curve.ClosestPointTo.ds#7

Geometry.Curve.ClosestPointTo.ds#7

After loading it in the Editor (DSE), copying it to ones clipboard, open DesignScript Studio (DSS)and paste it into the blank canvas.

Geometry.Curve.ClosestPointTo#7

Geometry.Curve.ClosestPointTo#7

Roughed out the translation looks something like the above screenshot. Then the definitions and properties were defined, as shown below.

Geometry.Curve.ClosestPointTo#7a

Geometry.Curve.ClosestPointTo#7a

Some liberty was taken in adding color and exploring the nodes further, after witch the “Node to Code” translation was done.

Geometry.Curve.ClosestPointTo#7b

Geometry.Curve.ClosestPointTo#7b

Parts of the code and the counterpart node graph translation were independent of each other, hence the two columns. The resulting Graphic Window is shown below.

Geometry.Curve.ClosestPointTo_Graphic Window

Geometry.Curve.ClosestPointTo_Graphic Window

The files are available for download from the links below.

Geometry.Curve.ClosestPointTo#7

Geometry.Curve.ClosestPointTo#7a

Geometry.Curve.ClosestPointTo#7b

Thanks for looking.

T!M

DesignScript Curve Translation,Geometry.Curve.Trim.UsingPoints#6– Code to Node to Code

Hi Everyone:

This the sixth DesignScript file in a series of forty-nine curve translations. The file, Geometry.Curve.Trim.UsingPoints.ds is from the DesignScript Editor (DSE) Sample files.

Geometry.Curve.Trim.UsingPoints.ds

Geometry.Curve.Trim.UsingPoints.ds

Like the previous DesignScript file,  the operator Trim for curves,  draws an exception. It should be pointed out that the vast majority of the Sample files work perfectly, so as not to get the wrong idea. DesignScript is a very elegant program, it simply needs (Alpha) development attention. Also, one need to know that these translations are done with the Stand-Alone version of DesignScript, so the functionality of it being a plugin for AutoCAD is not being reviewed.

With that said, lets take a look at the DesignScript Editor.

Geometry.Curve.Trim.UsingPoints.ds

Geometry.Curve.Trim.UsingPoints.ds

With the exception drawn, we get the error.

exception

exception

Continuing on with the initial translation.

Geometry.Curve.Trim.UsingPoints#6-Exception

Geometry.Curve.Trim.UsingPoints#6-Exception

Looking closer we see the Trim node and defined it as myTrimmedCurve.  At this point it’s best to disconnect one of the inputs in order to prevent the program from crashing.

Geometry.Curve.Trim.UsingPoints#6-Index, Out of Bounds

Geometry.Curve.Trim.UsingPoints#6-Index, Out of Bounds

So the “discardBetweenPoints” input of False is disconnected and one imagines the Trim command functions so as to develop the translation.

2013_12_21-Geometry.Curve.Trim.UsingPoints#6a

2013_12_21-Geometry.Curve.Trim.UsingPoints#6a

Above we see the properties extracted from the Trim node to complete the definition. Then the Node to Code operation takes place.

Geometry.Curve.Trim.UsingPoints#6b-edit

Geometry.Curve.Trim.UsingPoints#6b-edit

A few house keeping edits are done.

Geometry.Curve.Trim.UsingPoints#6b

Geometry.Curve.Trim.UsingPoints#6b

The graphic windows that accompanies the running of the file is shown below.

Geometry.Curve.Trim.UsingPoints-Graphic Window.

Geometry.Curve.Trim.UsingPoints-Graphic Window.

The operation ends with the Graphic window below.

Geometry.Curve.Trim.UsingPoints-Graphic Window-error drawn

Geometry.Curve.Trim.UsingPoints-Graphic Window-error drawn

This file is now ready to be corrected. (Thanks in advance lol.)

The files are available for downloading with the links below.

Geometry.Curve.Trim.UsingPoints#6

Geometry.Curve.Trim.UsingPoints#6a

Geometry.Curve.Trim.UsingPoints#6b

Thanks for looking.

T!M

DesignScript Curve Translation,Geometry.Curve.Offset#4 – Code to Node to Code

Hi Everyone:

This the forth DesignScript file in a series of forty-nine curve translations. The file, Geometry.Curve.Offset.ds is from the DesignScript Editor (DSE) Sample files.

Geometry.Curve.Offset.ds#4

Geometry.Curve.Offset.ds#4

This file has an error which required a work around. Unsatisfactory as that may be, one is still able to imagine it’s purpose and performance. Rather more serious than the misspelling of “Geoemtry , hopefully this will be fixed on the next DesignScript update.

Geometry.Curve.Offset.ds#4-error

Geometry.Curve.Offset.ds#4-error

The offset node was extracted from the lines onboard context menu. In order to complete this exercise the offset node for points was used.

Geometry.Curve.Offset.ds#4-point alt

Geometry.Curve.Offset.ds#4-point alt

Not the most elegant solution but one gets the idea.

Offset.ds#4-point alt_1

Offset.ds#4-point alt_1

The properties of the offset node were taken from the line node. One has to imagine them originating from the Offset node.

Geometry.Curve.Offset#4a

Geometry.Curve.Offset#4a

After completing the translation from code,  the nodes then are again transformed back into code, but first the  editing of the Variable 68 was performed as shown below.

Geometry.Curve.Offset#4b-edit

Geometry.Curve.Offset#4b-edit

The full translation then is shown below.

Geometry.Curve.Offset#4b-error_edit

Geometry.Curve.Offset#4b-error_edit

The highlighted curve operation failure is noted, with  the successful edit as well.

The results of this translation are shown in the Graphic below.

Geometry.Curve.Offset#4-Windows Graphic

Geometry.Curve.Offset#4-Windows Graphic

The files are available to download from the links below.

Geometry.Curve.Offset#4

Geometry.Curve.Offset#4a

Geometry.Curve.Offset#4b

Thanks for looking.

T!M

DesignScript Curve Translation, Curve.CoordinateSystemAtEqualArcLength.UpVector#3 – Code to Node to Code

Hi Everyone:

This the third curve file in a series of forty-nine DS translations. The file, “Geometry.Curve.CoordinateSystemAtEqualArcLength.UpVector”  can be accessed from the DesignScript Editor (DSE) Sample files, which are shown below and are on the DSE opening page.

Geometry.Curve.CoordinateSystemAtEqualArcLength.UpVector.ds

Geometry.Curve.CoordinateSystemAtEqualArcLength.UpVector.ds

After copying the sample file from the DSE and moving it into DesignScript Studio (DSS), it will have a similar node layout as shown below. This is very similar to the previous DSE file.

Geometry.Curve.CoordinateSystemAtEqualArcLength.UpVector#3

Geometry.Curve.CoordinateSystemAtEqualArcLength.UpVector#3

Once again the graph nodes are translated further from the script.

Geometry.Curve.CoordinateSystemAtEqualArcLength.UpVector#3a

Geometry.Curve.CoordinateSystemAtEqualArcLength.UpVector#3a

After the translation is complete the “Node to Code” operation is executed.

Geometry.Curve.CoordinateSystemAtEqualArcLength.UpVector#3b

Geometry.Curve.CoordinateSystemAtEqualArcLength.UpVector#3b

Again this file was straightforward and not requiring further editing. The resulting Graphic is generated from the file.

Geometry.Curve.CoordinateSystemAtEqualArcLength.UpVector#3-Graphic Window

Geometry.Curve.CoordinateSystemAtEqualArcLength.UpVector#3-Graphic Window

The files can be downloaded from the links below.

Geometry.Curve.CoordinateSystemAtEqualArcLength.UpVector#3

Geometry.Curve.CoordinateSystemAtEqualArcLength.UpVector#3a

Geometry.Curve.CoordinateSystemAtEqualArcLength.UpVector#3b

Thanks for looking.

T!M

DesignScript Curve Translation, Curve.Composite#1 – Code to Node to Code

Hi Everyone:

This the first in a series of forty-nine curve file translations. The file, Geometry.Curve.Composite.ds is from the DesignScript Editor (DSE) Sample files.

Geometry.Curve.Composite.ds#1

Geometry.Curve.Composite.ds#1

The first thing to note is that Geoemtry” is not really a new branch of Math, just a misspelling, which at some point hopefully gets corrected. More importantly though is the error this file generates when run in the DSE.

Geometry.Curve.Composite.ds_error

Geometry.Curve.Composite.ds_error

The problem turns out to be, when executing the (“Create composite curve using method : Composite” ) Composite command.

Geometry.Curve.Composite.ds- Error highlighted

Geometry.Curve.Composite.ds- Error highlighted

Note the highlighted “Composite curve operation failed” statement after which the “Deferencing a non-pointer  warning is given for the remainder of the script.

One can investigate this error in node form, but first the preliminary translation to DesignScript Studio is required.

Geometry.Curve.Composite.ds#1

Geometry.Curve.Composite.ds#1

After the initial nodes have been laid out the composite node is gotten from the library and linked into position.

Geometry.Curve.Composite#1-error

Geometry.Curve.Composite#1-error

As can be seen, we get a failure. However if one just takes one of the elements, a successful result can be obtained.

Geometry.Curve.Composite#1-error_solution

Geometry.Curve.Composite#1-error_solution

We can work with this to finish developing this translation, although this need some coding attention from the powers that be. (hint Autodesk)

Geometry.Curve.Composite#1a

Geometry.Curve.Composite#1a

Sticking with just the mySpline node as the operator for the Curve.Composite node we are able to extract the other specified properties. Satisfied, as much as possible with the translation thus far, the “Node to Code” translation can be initiated.

Geometry.Curve.Composite#1b

Geometry.Curve.Composite#1b

The script being rather long, can also be broken up to be more manageable.

Geometry.Curve.Composite#1b

Geometry.Curve.Composite#1b

Among all the anomalies in the script, the above middle stand-alone coordinate Point2 doesn’t figure to really have a purpose. With that said the relatively simple Window Graphic that is generated from this visual code is shown below.

Geometry.Curve.Composite_Windows Graphic

Geometry.Curve.Composite_Windows Graphic

As usual, liberty was taken with color for visual interest. The files are available for downloading below.

Geometry.Curve.Composite#1

Geometry.Curve.Composite#1a

Geometry.Curve.Composite#1b

Thanks for looking.

T!M

DesignScript Curve Translation, Curve.Line.IsColinear#3- Code to Node to Code

Hi Everyone:

This is the third Line file, Geometry.Curve.Line.IsColinear.dsin a series of four curve- line translations from the DesignScript Editor Sample files.

Geometry.Curve.Line.IsColinear.ds

Geometry.Curve.Line.IsColinear.ds

The highlighted file, Geometry.Curve.Line.IsColinear.ds is shown in the DSE (DesignScript Editor). Copy the resulting script to the clipboard and then open DSS (DesignScript Studio). Paste the script from the clipboard into the blank canvas. Develop the translation and it will look something like below.

Geometry.Curve.Line.IsColinear#3

Geometry.Curve.Line.IsColinear#3

Note the how the properties are developed in a sequence.

Geometry.Curve.Line.IsColinear#3a

Geometry.Curve.Line.IsColinear#3a

The “Node to Code” translation can now take place.

Geometry.Curve.Line.IsColinear#3b

Geometry.Curve.Line.IsColinear#3b

The graphic generated from the files is shown below.

Geometry.Curve.Line.IsColinear- Windows Graphic

Geometry.Curve.Line.IsColinear- Windows Graphic

The files can be downloaded from the links below.

Geometry.Curve.Line.IsColinear#3

Geometry.Curve.Line.IsColinear#3a

Geometry.Curve.Line.IsColinear#3b

Thanks for looking.

T!M