.NET

.NET

Reply
Valued Contributor
FFlix
Posts: 95
Registered: ‎11-15-2011
Message 1 of 2 (134 Views)

GetNewSamplePoints Method, relation 'chordHeight' to curve parameter (start/end)

134 Views, 1 Replies
01-08-2012 03:51 PM

the class reference guide states that the above:

 

Returns a list of points on the curve. so far so good. it continuous:

 

This method's behavior is similar to GetSamplePoints except that this method forces the generation of new samples. The samples returned by GetSamplePoints could have a much smaller error than is specified by chordHeight. This method returns sample points with a maximum error as close to chordHeight as possible.

 

this is where i'm running into difficulties: what exactly is an 'error' with regards to sample points? the results that i'm getting from different chordHeight runs are tricky in that in some cases they seem perfectly fine but in others appear unpredictable; notably when the extent of the sample 'ignores' the set boundaries along the curve and 'jumps' to, say, the startparameter. however, i believe to recall instances where start- and endparameter of a curve NOT necessarily are synonymous with start- and endpoint of that curve, i guess depending on how that curve was created maybe - something that i have been conciously trying to avoid in this case.

 

anyway, help appreciated, thanks

 

felix

Valued Contributor
FFlix
Posts: 95
Registered: ‎11-15-2011
Message 2 of 2 (109 Views)

Re: GetNewSamplePoints Method

01-10-2012 04:53 AM in reply to: FFlix

PS well, if someone is interested, here's how i try make sense of it:

 

start- and endPOINT of a curve may be the same but any problem this may cause can be addressed by using its .evaluatepoint() method with its .startPARAMETER and .endPARAMETER value respectively as input parameter.

 

the chordHeight is somewhat of a density of the returned sample points along the curve, possibly in relation to the curve's vertices; this density increases with input values approaching towards zero+. i think an actual input value of zero increases the risk of a crash and so do negative values, whereas values above 1 don't actually effect further change.

 

comments still welcome of course

Post to the Community

Have questions about Autodesk products? Ask the community.

New Post
Announcements
Do you have 60 seconds to spare? The Autodesk Community Team is revamping our site ranking system and we want your feedback! Please click here to launch the 5 question survey. As always your input is greatly appreciated.