File: FAQ.html

package info (click to toggle)
felt 3.02-4
  • links: PTS
  • area: main
  • in suites: slink
  • size: 16,460 kB
  • ctags: 6,885
  • sloc: ansic: 72,103; fortran: 3,614; yacc: 2,825; lex: 1,172; sh: 311; makefile: 279
file content (372 lines) | stat: -rw-r--r-- 16,842 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
<HTML>
<HEAD>
<TITLE>
FElt FAQ
</TITLE>
</HEAD>

<H1>
This is the list of frequently asked questions for FElt
</H1>
last modified: 07-16-95

<OL>
<LI><A HREF="#What-is">What is FElt?</A>

<UL>
<LI><A HREF="#What-kinds">What kinds of problems can FElt solve?</A>
<LI><A HREF="#Can-it">Can FElt solve my type of problem?</A>
<LI><A HREF="#Modify-it">Can I modify FElt to make it solve my type of problem?</A>
<LI><A HREF="#Extend-it">On that same note, can I add new kinds of elements?</A>
</UL>

<LI><A HREF="#Where-is">Where can I get FElt?</A>
<LI><A HREF="#What-machines">What machines does FElt run on?</A>

<UL>
<LI><A HREF="#Windows">Is there a Windows interface to FElt?</A>
<LI><A HREF="#Other-GUIs">What about a Motif or OpenLook interface?</A>
<LI><A HREF="#Compile">Can I compile FElt using X11R4 (R3 ...) ?</A>
<LI><A HREF="#Unpack">Where can I get gzip to unpack the tar files on cs.ucsd.edu?</A>
</UL>

<LI><A HREF="#Bugs">I think I found a bug, what now?</A>
<LI><A HREF="#Newsgroup">Is there a newsgroup or mailing list for FElt?</A>

<UL>
<LI><A HREF="#Posting">What kind of things should I post to the mailing list and what kinds of things should I contact the authors for?</A>
</UL>

<LI><A HREF="#Names">Why do the FElt components have such stupid names?</A>
</OL>

<OL>
<H2><LI><A NAME="What-is">What is FElt?</A></H2>

</P>
FElt is a free system for introductory level finite element analysis.  It
is primarily intended as a teaching tool for introductory type courses
in finite elements - probably in the mechanical/structural/civil fields.
In a command line environment, FElt uses an intuitive, straightforward input
syntax to describe problems.  It also includes a graphical user interface
for workstations that allows the user to set-up, solve and post-process the 
problem in a single CAD-like environment.   

</P>
From the end-user point of view, FElt consists of six programs: felt, 
burlap, velvet, corduroy, patchwork, and yardstick.  felt is the basic
command-line application; burlap is an interactive Matlab-like environment
for scripting your own elements and analyses; velvet is the primary GUI
interface into the bulk of the functionality in FElt; corduroy is command-line 
program for automatic element generation; patchwork is a command-line 
application for file format conversion to and from the FElt syntax; and 
yardstick is a simple program for problem scaling and unit conversion.

</P>
Felt is the simplest - it takes a FElt input file and spits back 
appropriate ASCII based (tabular or ASCII graphics) results depending on 
the problem type.  The command line application felt is the only 
interface of the three analysis engines (felt, velvet, burlap) that
is available under DOS.

</P>
Velvet is the most powerful interface into the pre-programmed functionality 
of FElt - it allows for complete graphical problem definition through pulldown 
menus, popup dialog boxes and an interactive drawing area.  It offers all of 
the capabilities of both felt and corduroy and has several options for 
post-processing, including color stress plots for planar elements, plots 
of the displaced structure, animation, graphical time-displacement plots 
for transient analysis problems, graphical frequency domain plots of transfer 
functions and output spectra for spectral analysis, and graphical plots of 
mode shapes for modal analysis problems.

</P>
Burlap is the most powerful interface in terms of raw FE computing power
simply because you can make it perform analyses that are not otherwise
available in FElt simply by scripting your own analyses algorithms in
burlap's powerful Matlab-like syntax.  You can also use burlap to 
try out new element definitions quickly and easily or to manipulate the
results from one of FElt's pre-programmed analyses in a novel way that is
otherwise not provided for.

<UL>
<H3><LI><A NAME="What-kinds">What kinds of problems can FElt solve?</A></H3>

<P>
As distributed, FElt can solve the classic problems in linear statics 
and linear dynamics for both structural and thermal mechanics (i.e., problems 
of the form Kd = F, Md'' + Cd' + Kd = F , or Md' + Kd = F).  It can also solve 
the generalized eigenvalue problem (K - lM)x = 0 and use this information in 
modal analysis.  It can do spectral (frequency domain) analysis of transient 
structural problems.  The element library consists of truss, beam (Timoshenko 
and Euler), constant strain triangular, bilinear planar isoparametric,  plate 
bending (selective reduced integration quadrilateral), isoparametric solid 
(eight node brick) elements, and rod and constant temperature gradient
thermal elements.

<H3><LI><A NAME="Can-it">Can FElt solve my type of problem?</A></H2>

<P>
Unless it fits into one of the classes above there are no built-in solvers
for your type of problem.  You may be able to use burlap to write your own
solver though.

<H3><LI><A NAME="Modify-it">Can I modify FElt to make it solve my type of
problem?</A></H3>

</P>
Probably, and we'd be happy to help.  The only reason FElt cannot do
more right from the start is partly because we don't have time and partly
because it is very hard to keep everything simple, straightforward and
intuitive if we support every different type of analysis and algorithm -
especially because beyond the basics there are so many different
possibilities.  What may interest one person on the serious research 
level is probably not going to interest the majority of other users.

</P>
FElt does offer a lot of basic support that would be useful in a broad 
class of finite element programs.  If you do want to add your own analysis
algorithms, the best place to start is to probably look at the source
code for the felt driver program (bin/Felt/felt.c) and see how it handles
switching between static, dynamic and modal analyses.  Then take a look at
the routines for static (lib/Felt/fe.c), dynamic (lib/Felt/transient.c),
modal (lib/Felt/modal.c), and spectral (lib/Felt/spectral.c) problems to see 
how the different types of algorithms make use of the data structures and 
general routines to actually go about getting a solution.

</P>
Finally, we want people to know that our major motivation for creating
burlap were questions just like this.  With burlap you now have two 
options for performing analyses that don't already exist - you can modify
and add to the FElt source as outlined above or you can script your
algorithm in burlap.  The latter is probably much easier and we encourage
people to try it out.  If we do end up with a lot of neat analyses scripted
into burlap then perhaps we can start putting together a library of
this functionality for general distribution.  That kind of growth in 
functionality sounds a lot nicer to us because it would be a lot easier to 
maintain and distribute.

<H3><LI><A NAME="Extend-it">On that same note, can I add new kinds of
elements?</A></H3>

</P>
Absolutely, there's even a whole chapter in the user's manual devoted to
this very topic.  We'd be very interested if you did add a new element
because we'd like to start putting a user contributed element library
together for distribution with with regular sources.

</P>
Also, just like you can add your own new analyses through burlap,
keep in mind that you can script new elements in burlap as well.  This
is a potentially much easier way to go about it.  Whichever way
you choose to go about it, let us know what you come up with -
we'd like to hear whatever success (or horror) stories people might have.

</UL>

<H2><LI><A NAME="Where-is">Where can I get FElt?</A></H2>

<P>
The latest version of FElt, in all its incarnations, is always available
via anonymous ftp from cs.ucsd.edu.  Once you have ftp'd to cs.ucsd.edu
login as anonymous and give your email address as the password.  cd
to /pub/felt and grab whatever files you need for your particular
situation.  As of this update, the latest version is v3.00.
Information (and hypertext access to the ftp site) is available via
World Wide Web (e.g., Mosaic) at

<P>
http://www-cse.ucsd.edu/users/atkinson/FElt/felt.html 

<P>
if you want to take a more serious look at some of FElt's capabilities
before you actually take it for a test drive on your machine.
 
<H2><LI><A NAME="What-machines">What machines does FElt run on?</A></H2>

<P>
The complete version of FElt (including the X11 based graphical user
interfaces) has compiled and tested on HPs, DECs, Suns, SGIs, 386/486s
running Linux and SysV R3, and IBM workstations. It should do the same
on any reasonable Unix system with X11R5 or R6.  In general we provide
binaries for Sparc stations running SunOS or Solaris and 386s with Linux, 
but there is no guarantee that the binaries are as up to date as the source 
code.  When in doubt just grab the source code and build it yourself - 
really, it's easy.

<P>
DOS executables are available for the command-line applications felt,
corduroy, yardstick, and patchwork.  A simple graphical application, feltvu 
is also available.  You need to have at least a 386 to use the DOS versions.

<UL>
<H3><LI><A NAME="Windows">Is there a Windows interface to FElt?</A></H3>

<P>
Not yet, and we're probably not the folks to write it as neither of us
have much experience with Windows programming.  If someone else would
like to volunteer then I'd suggest starting with something like xfelt
as it's really pretty simple.   There may be people working on this -
let us know if you're thinking about something like it and we'll try
our best to make sure that people don't duplicate a lot of effort.

<H3><LI><A NAME="Other-GUIs">What about a Motif or OpenLook interface?</A></H3>

<P>
Well we originally chose to work with the Athena widgets because the price
is right and because they allow us to maintain FElt as a 100% free product.
With the current set-up anyone (in theory at least) can get and build 
everything they need to get FElt up and running free.  If we had worked
in Motif then we at least would have had to shell out for Motif for Linux
and people without Motif simply would be out of luck unless they happened
to be working on one of the few machines that we could provide statically
linked binaries for.  We also recognize that we could maintain separate
GUI interfaces, but we feel that our development time is better spent on
functionality rather than on constantly keeping two or more separate interfaces
up to date.  In addition, it's our feeling that Motif or OpenLook or any other 
widget set would not offer us any significant additional capabilities that we 
haven't already worked out with the Athena widgets.  

<P>
However, if you just want a slightly different look and feel than the 
stylized default look of velvet then please feel free to change it -
that's what Xresources are for after all.  The easiest way to get a slightly
more Motif look (not really the feel though) is to switch to the 3d Athena
widgets.  I know that these are readily available as compiled libraries for
Linux and should be for some other machines as well; they're also really
easy to build yourself if you are so inclined.  Once you have them all you
have to do is swap them for your regular Athena shared library (or re-link
if you don't use shared libs); the next time you run velvet everything should
be 3d.  There are some recommended changes to the app defaults for velvet if
you do decide to go this route, they're at the bottom of Velvet.ad in
src/Velvet.

<H3><LI><A NAME="Compile">Can I compile FElt using X11R4 (R3 ...)?</A></H3>

<P>
Not really - you really should have X11R5 or R6.  Compiled libraries should 
be available for most machines.  If not, source code for the X11R5
distribution is available via anonymous ftp from ftp.x.org and pre-
compiled libraries should be available from many places on the net.
Now that X11R6 is available you should be able to use that just as
well as R5.

<P>
If you really want to do it with X11R4, then you can try the following:
from ftp.x.org get three header files from the untarred R5 or R6 sources -
Xfuncs.h, Xfuncproto.h, Xosdefs.h.  Make a directory FElt-x.xx/inc/X11
and copy these three files into it.  Then just do a regular make as
described in the INSTALL file.  See the notes on SGIs in the INSTALL file 
if you need a few more details.

<H3><LI><A NAME="Unpack">Where can I get gzip to unpack the tar files on
cs.ucsd.edu?</A></H3>

<P>
Source code is available from prep.ai.mit.edu.  Binaries for a wide
variety of machines should also be available from various archives
on the net.  Building gnu binaries from source is really easy, just 
untar them, cd into the directory into which they unpacked, type
configure and then type make.
</UL>

<H2><LI><A NAME="Bugs">I think I found a bug, what now?</A></H2>

<P>
Send one of us email (jgobat@mit.edu or atkinson@ucsd.edu).  Please,
please, please, include as much information as possible in your report.
Things that are absolutely essential: 
<UL>
<LI> version of FElt that you are using
<LI> the application that you think the bug is in (felt, velvet, everything, 
     etc.), this is particularly helpful if the bug only shows up in velvet
     but not in felt (or the reverse)
<LI> type of machine and operating system (including the OS version) that you 
     are using
<LI> if you are using a pre-built binary or if you are using a binary that you 
     built yourself; if you built the binary, how did you build it (gcc, 
     native cc, etc.)
<LI> and of course a detailed description of what went wrong and what you 
     were doing when it went wrong.  If possible send us the input file that  
     causes the problem, if you can't do that then tell us what kind of 
     analysis you are doing and any other relevant details specific to your 
     problem.  
</UL>


<H2><LI><A NAME="Newsgroup">Is there a newsgroup or mailing list for
FElt?</A></H2>

<P>
There is a mailing list.  To subscribe to the list send a one line email
message that says

<P>
subscribe felt-l

<P>
to listserv@mecheng.asme.org.  To send a message to the list just send
it like regular email to felt-l@mecheng.asme.org.  Incremental
release announcements and bug fixes will be posted to the mailing list.
Major release announcements will be made to the following newsgroups:
comp.os.linux.announce, sci.math.num-analysis, sci.engr, sci.engr.civil,
and sci.engr.mechanical.  So if you really want to keep up on new 
versions and capabilities, you should subscribe to the mailing list.

<UL>
<H3><LI><A NAME="Posting">What kind of things should I post to the mailing
list and what kinds of things should I contact the authors for?</A></H3>

<P>
The list is generally for announcements, bug fixes, and questions that
several FElt users might have an interest in (i.e., I'm trying to make
FElt solve a problem like xxx, how have other people modeled this? or
I really think that velvet should be able to do xxx, what does everyone
else think?).  We'd also like it to be a forum for discussion of what
types of things people would like to see in FElt.

<P>
For bug reports that you think are specific to your machine or things
that other users probably don't have an interest in, feel free to send 
email to one of us: jgobat@mit.edu or atkinson@ucsd.edu.  See
the <A HREF="#Bugs">question on bugs</A> for details on how to submit
a bug report.
</UL>

<H3><LI><A NAME="Names">Why do the FElt components have such stupid
names?</A></H3>

<P>
Well, FElt is obvious, right?  Finite ELemenT.  felt the application
came first - it's the most basic interface into the system.  
Now when it comes to fabrics, everybody knows that velvet is 
smoother than felt ... thus the slickest GUI interface is called
velvet.  xfelt is simply xfelt because it is nothing more than
an encapsulator, with no real functionality beyond that provided by
felt.

<P>
After this, we start to stretch because with the felt - velvet connection
we have this fabric motif to keep up on.  

<P>
  - Burlap is rough but functional, just like its namesake fabric.  It may
    not be as easy to use as velvet (or maybe it is if you like scripting
    in Matlab-like mathematical languages) but you can do an awful lot
    with it.
<P>
  - Corduroy has that regular ripple effect so its sort of like a mesh ... 
<P>
  - Patchwork, well we figured that was better than convert simply to 
    avoid conflicts.  How many systems have some local app called convert 
    to do whatever, or how many little hacks are there called convert.  
    It seemed common enough to us that we figured we might as well call it 
    something different.  Patchwork implies a lot of different fabrics 
    coming together so it seemed as good as anything else.  
<P>
  - A yardstick is used to measure fabric ... measuring implies some sort 
    of units.
</OL>
<P>
<A HREF="index.html">Back</A> to the FElt Demo Document.
</HTML>