Getting the overall size of a 3D solid with orientation data.

[Anonymous]

I just wanted to let the group know that a few of years ago I figured out a
way to get orientation data of a 3D object from pretty much no more then the
points in space. All other applications, except mine, that can create a cut
list must be formula/parametrically driven, except for rapid prototyping
(where the source material is a liquid) because no one had ever really
understood the problem and created a solution.

In the interest of sharing with the other forum member I wanted to point out
our published patent application so that if any of you are attempting to get
data this way you do not waste your time.

I am not currently looking to license this method to any of the coders here,
but if it something you really need I am sure something reasonable can be
worked out.

Thank you.

Here is the link:
http://appft1.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=%2Fnetahtml%2FPTO%2Fsearch-bool.html&r=1&f=G&l=50&co1=AND&d=PG01&s1=smartlister&OS=smartlister&RS=smartlister

David Wishengrad
President & CTO
MillLister, Inc.
http://SmartLister.com

[Anonymous]

Gee, thanks for "sharing". Are you aware of the solid modeling scheme
introduced by Levoy and Whitted back in 1985?

Henrik Vallgren

"Dave" skrev i meddelandet
news:[email protected]...
> I just wanted to let the group know that a few of years ago I figured out
a
> way to get orientation data of a 3D object from pretty much no more then
the
> points in space. All other applications, except mine, that can create a
cut
> list must be formula/parametrically driven, except for rapid prototyping
> (where the source material is a liquid) because no one had ever really
> understood the problem and created a solution.
>
> In the interest of sharing with the other forum member I wanted to point
out
> our published patent application so that if any of you are attempting to
get
> data this way you do not waste your time.
>
> I am not currently looking to license this method to any of the coders
here,
> but if it something you really need I am sure something reasonable can be
> worked out.
>
> Thank you.
>
> Here is the link:
>
http://appft1.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=%2F
netahtml%2FPTO%2Fsearch-bool.html&r=1&f=G&l=50&co1=AND&d=PG01&s1=smartlister
&OS=smartlister&RS=smartlister
>
> David Wishengrad
> President & CTO
> MillLister, Inc.
> http://SmartLister.com
>
>

[Anonymous]

Your more then welcome.

You mean this:
http://216.239.39.104/search?q=cache:VU5kTHW12jwJ:www.cs.unc.edu/~ibr/pubs/nyland-aipr99/nyland-aipr99.pdf+%22Levoy+and+Whitted%22+1985+orientation+solid&hl=en&ie=UTF-8

The rendering stuff that they did and realized that they needed orientation
data and it was not available from the points themselves?

Sure, this would solve their problem if the openGL engine had a routine to
call this information.

It certainly was not patented by anyone. Nor was this approach mentioned in
extensive researching. It does have some drawbacks. When an object has
equally sized sides and you want to make one side larger, you would loose
your orientation information as this method depends on calculation to the
lengths of the sides in relationship to each other in a bigger then, less
then operation. For rendering, this becomes a huge hole that produces
non-function, as rendering is really not that important. it also wants to
have a tight code, without a hole. It is a rule driven, code driven event.
On the other hand, cut listing for manufacturing is critical. It is diverse
and cannot be contained in a rule driven / code driven program. There is
always a situation where is fails to perform. Additionally, there was no way
to stretch multiple 3D solids back then and that also introduced problems.
They went the same way as everyone else eventually. I see it as a flawed
path. It has it's uses and that is for sure. The core of the method they use
it fundamentally tight from a programmers point of view, but not practical
for manufacturing.as compared to my method.

Thanks for the response,

Dave



"Henrik Vallgren" wrote in message
news:[email protected]...
> Gee, thanks for "sharing". Are you aware of the solid modeling scheme
> introduced by Levoy and Whitted back in 1985?
>
> Henrik Vallgren
>
> "Dave" skrev i meddelandet
> news:[email protected]...
> > I just wanted to let the group know that a few of years ago I figured
out
> a
> > way to get orientation data of a 3D object from pretty much no more then
> the
> > points in space. All other applications, except mine, that can create a
> cut
> > list must be formula/parametrically driven, except for rapid prototyping
> > (where the source material is a liquid) because no one had ever really
> > understood the problem and created a solution.
> >
> > In the interest of sharing with the other forum member I wanted to point
> out
> > our published patent application so that if any of you are attempting to
> get
> > data this way you do not waste your time.
> >
> > I am not currently looking to license this method to any of the coders
> here,
> > but if it something you really need I am sure something reasonable can
be
> > worked out.
> >
> > Thank you.
> >
> > Here is the link:
> >
>
http://appft1.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=%2F
>
netahtml%2FPTO%2Fsearch-bool.html&r=1&f=G&l=50&co1=AND&d=PG01&s1=smartlister
> &OS=smartlister&RS=smartlister
> >
> > David Wishengrad
> > President & CTO
> > MillLister, Inc.
> > http://SmartLister.com
> >
> >
>
>

[Anonymous]

Henrik,

I am always interest in working with programmers that work with solids. If
you are interested in joining forces, please let me know. You can see more
about what my software does at SmartLister.com.

Thanks again,

DAve

"Dave" wrote in message
news:[email protected]...
> Your more then welcome.
>
> You mean this:
>
http://216.239.39.104/search?q=cache:VU5kTHW12jwJ:www.cs.unc.edu/~ibr/pubs/nyland-aipr99/nyland-aipr99.pdf+%22Levoy+and+Whitted%22+1985+orientation+solid&hl=en&ie=UTF-8
>
> The rendering stuff that they did and realized that they needed
orientation
> data and it was not available from the points themselves?
>
> Sure, this would solve their problem if the openGL engine had a routine to
> call this information.
>
> It certainly was not patented by anyone. Nor was this approach mentioned
in
> extensive researching. It does have some drawbacks. When an object has
> equally sized sides and you want to make one side larger, you would loose
> your orientation information as this method depends on calculation to the
> lengths of the sides in relationship to each other in a bigger then, less
> then operation. For rendering, this becomes a huge hole that produces
> non-function, as rendering is really not that important. it also wants to
> have a tight code, without a hole. It is a rule driven, code driven event.
> On the other hand, cut listing for manufacturing is critical. It is
diverse
> and cannot be contained in a rule driven / code driven program. There is
> always a situation where is fails to perform. Additionally, there was no
way
> to stretch multiple 3D solids back then and that also introduced problems.
> They went the same way as everyone else eventually. I see it as a flawed
> path. It has it's uses and that is for sure. The core of the method they
use
> it fundamentally tight from a programmers point of view, but not practical
> for manufacturing.as compared to my method.
>
> Thanks for the response,
>
> Dave
>
>
>
> "Henrik Vallgren" wrote in message
> news:[email protected]...
> > Gee, thanks for "sharing". Are you aware of the solid modeling scheme
> > introduced by Levoy and Whitted back in 1985?
> >
> > Henrik Vallgren
> >
> > "Dave" skrev i meddelandet
> > news:[email protected]...
> > > I just wanted to let the group know that a few of years ago I figured
> out
> > a
> > > way to get orientation data of a 3D object from pretty much no more
then
> > the
> > > points in space. All other applications, except mine, that can create
a
> > cut
> > > list must be formula/parametrically driven, except for rapid
prototyping
> > > (where the source material is a liquid) because no one had ever really
> > > understood the problem and created a solution.
> > >
> > > In the interest of sharing with the other forum member I wanted to
point
> > out
> > > our published patent application so that if any of you are attempting
to
> > get
> > > data this way you do not waste your time.
> > >
> > > I am not currently looking to license this method to any of the coders
> > here,
> > > but if it something you really need I am sure something reasonable can
> be
> > > worked out.
> > >
> > > Thank you.
> > >
> > > Here is the link:
> > >
> >
>
http://appft1.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=%2F
> >
>
netahtml%2FPTO%2Fsearch-bool.html&r=1&f=G&l=50&co1=AND&d=PG01&s1=smartlister
> > &OS=smartlister&RS=smartlister
> > >
> > > David Wishengrad
> > > President & CTO
> > > MillLister, Inc.
> > > http://SmartLister.com
> > >
> > >
> >
> >
>
>