[rp-ml] RP files and tolerant machines/processes

List.

Lately a question has come up over here with respect to "watertightness"
and stl files (or others).

Does anyone have any information on which machines or processes are more
"forgiving" with respect to errors in the file format. Is there a good
source for seeing what these errors entail (preferably with visual
examples)?

For instance, are some processes more forgiving than others in this
respect? Is this a consequence of the processing software, the machines
or what exactly?

What about when it comes to supplying multiple closed stl files (which
overlap) as opposed to one single stl. Can all machines deal with
producing a part from separate files and is it the processing software
that determines this?

It seems like there is a physical machine/process, a material,
processing software, the file format and the actual file.

I'm curious to understand a little better which one of these controls or
how they interact when it comes to actually producing a file.

In general are the binder based systems are more forgiving than the
laser based systems?

Obviously I have not had a chance to get some hands on experience with
this kind of thing so I'd be happy to hear from those that have.

Most Sincerely,

Jonathan

-- 
Universal Joint Design Associates 
Jonathan Chertok. Principal 
AIA Associate
Austin, Texas  1 512 407 9628 
Development + Design + Construction 
http://www.universaljointdesign.com 
[ bLOG ] on digital tools, rapid prototyping technologies and the fabrication of free-form structure.
This e-mail and its attachments may contain confidential information. It
is intended solely for the use of the addressee(s) named herein. Any use
of the information contained herein by other persons is prohibited. If
you have received this e-mail by mistake, please immediately notify the
sender (via the phone number above or email) and permanently delete the 
original as well as any copy thereof. 
Do not use any files or other data, via ftp or other means, without 
subsequent permission in writing.
UJDA does not accept any liability for the contents of this
e-mail or its attachments.