[X3D-Public] [Cad] Additive Manufacturing File Format-Wikipedia, the free encyclopedia

[Joe D Williams]

Also I finally figured out that this is meant mainly for geometry to 
be sliced as for printing.
Notice the curve function in there to allow high precision in a curve 
without needing lots of points in the user code, For every slice the 
processor computes points that would smooth to the desired curve. Best 
Regards,
Joe

----- Original Message ----- 
From: "Joe D Williams" <joedwil at earthlink.net>
To: "Richard F. Puk" <puk at igraphics.com>; "'Don Brutzman'" 
<brutzman at nps.edu>; "'Cad3D working group'" <Cad at web3d.org>
Cc: "'X3D Graphics public mailing list'" <x3d-public at web3d.org>
Sent: Wednesday, December 18, 2013 3:01 PM
Subject: Re: [X3D-Public] [Cad] Additive Manufacturing File 
Format-Wikipedia, the free encyclopedia


> As usual in this style of encoding of geometry data, the main idea 
> is that we get back to basics and all variables are superficially 
> simple in the user code then combined into application-specific data 
> types like tuples of various kinds in a process one level up, not 
> necessarily in the user code.
>
> Usually it is easy enough to put these into X3D xml or Classic 
> strictly defined data structures or any other 3D tool but that does 
> not mean this degenerate method of encoding X3D scene data should be 
> acceptable in X3D.
>
> Is this naming of elements and representation of data in the user 
> code compatible with Collada - that would be important.
>
> In this
>
> <object id="0">
> <mesh>
> <vertices><vertex><coordinates><x><y><z>
> <volume><triangle><v1><v2><v3>
>
> mesh example 'vertices' with its simple 'vertex' 'coordinates' and 
> 'volume' with its simple  'triangle'(s) would be set into a shape 
> node 'points' and 'coordIndex' fields. Same info, much fewer 
> characters.
>
> Basic check would be to see if there are any keywords like 
> 'triangle' or 'object' could be found that cannot be styled into 
> X3D.
>
>> triplet representations looks extremely inefficient :^)
>
> A supporter of only simple but heavily labelled containerification 
> of actual data at  the user code level is that a lot of the apparent 
> duplication, well, that gets mostly compressed away.
> And really, the simp ... /simp ... lified ... /lified exam ... ples 
> ... are much easier to explain and troubleshoot:)) - at first 
> anyway.
>
> I think a big counter today might be that current X3D and Classic 
> strict typing of fields simply works lots better for JSON.
>
> Best Regards,
> Joe
>
>
> ----- Original Message ----- 
> From: "Richard F. Puk" <puk at igraphics.com>
> To: "'Don Brutzman'" <brutzman at nps.edu>; "'Cad3D working group'" 
> <Cad at web3d.org>
> Cc: "'X3D Graphics public mailing list'" <x3d-public at web3d.org>
> Sent: Wednesday, December 18, 2013 9:58 AM
> Subject: Re: [X3D-Public] [Cad] Additive Manufacturing File 
> Format -Wikipedia, the free encyclopedia
>
>
>> Hi --
>>
>> The format for coordinate and other triplet representations looks 
>> extremely
>> inefficient :^)
>>
>>  -- Dick
>>
>> /******************************************
>> | Richard F. Puk, Ph.D., President
>> | Intelligraphics Incorporated
>> | 7644 Cortina Court
>> | Carlsbad, CA  92009-8206
>> | Tel: +1-760-753-9027  Mobile:  +1-760-809-9027
>> | Email:  puk at igraphics.com
>> \******************************************
>>
>>
>>
>>
>> -----Original Message-----
>> From: cad [mailto:cad-bounces at web3d.org] On Behalf Of Don Brutzman
>> Sent: Wednesday, December 18, 2013 9:36 AM
>> To: Cad3D working group
>> Cc: X3D Graphics public mailing list
>> Subject: [Cad] Additive Manufacturing File Format - Wikipedia, the 
>> free
>> encyclopedia
>>
>> Wondering if anyone in the CAD working group has looked at AMF yet?
>>
>> https://en.wikipedia.org/wiki/Additive_Manufacturing_File_Format
>>
>> p.s. it has been pointed out that the x y z representations are
>> "interesting"...
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <amf unit="millimeter">
>>   <object id="0">
>>     <mesh>
>>       <vertices>
>>         <vertex>
>>           <coordinates>
>>             <x>0</x>
>>             <y>1.32</y>
>>             <z>3.715</z>
>>           </coordinates>
>>         </vertex>
>>         ...
>>       </vertices>
>>       <volume>
>>         <triangle>
>>           <v1>0</v1>
>>           <v2>1</v2>
>>           <v3>3</v3>
>>         </triangle>
>>         ...
>>       </volume>
>>     </mesh>
>>   </object>
>> </amf>
>>
>> p.p.s. Incidentally ASTM is charging $48 for this 15-page ISO 
>> standards
>> document.
>> http://www.astm.org/Standards/F2915.htm
>>
>> all the best, Don
>> -- 
>> Don Brutzman  Naval Postgraduate School, Code USW/Br 
>> brutzman at nps.edu
>> Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA 
>> +1.831.656.2149
>> X3D graphics, virtual worlds, navy robotics 
>> http://faculty.nps.edu/brutzman
>>
>> _______________________________________________
>> cad mailing list
>> cad at web3d.org
>> http://web3d.org/mailman/listinfo/cad_web3d.org
>>
>>
>> _______________________________________________
>> X3D-Public mailing list
>> X3D-Public at web3d.org
>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
>
> _______________________________________________
> X3D-Public mailing list
> X3D-Public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org