[Insight-developers] check-in the FEM classes in itk
Aljaz Noe
noe@grasp.cis.upenn.edu
Wed, 21 Nov 2001 15:37:24 -0500
This is a multi-part message in MIME format.
------=_NextPart_000_0004_01C172A2.6A8C42D0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Hi!
We're planning to check-in the first pre-alpha version of the Finite Element
Modeling (FEM) code by the end of the next week. We'll be adding a lot of
new files (>50) and classes into the toolkit and I really don't want to
screw something up while doing this.
So, can you give me some guidelines on how to import some new code into itk
toolkit? Currently our FEM code is not a part of itk, but only uses the itk
via the #include statements. How do we make our files a part of itk, that
will compile as expected when checked out with the rest of the itk? Here I'm
particularly interested about what to do with CMake.
Where do we put the files? Do we get a separate folder (called FEM???), or
should we dump everything in the common folder?
Is it possible (allowed?) to use another namespace within the itk namespace
to mask internally used classes? Since the FEM toolkit was originally
developed independently of itk, we currently use quite a few of them, and
they really serve no purpose outside the FEM framework.
What is the status of LightDataObject (or whatever it's called), which
doesn't have regions? Most of the Data Objects that we use don't have
regions. It makes little sense to, for example, apply only half of the
prescribed boundary conditions or material properties to the system. It
would be nice if we all use the same base classes (if they exist) to create
corresponding data and process objects.
Any other comments that you may have, are of course appreciated...
Aljaz
------=_NextPart_000_0004_01C172A2.6A8C42D0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D171012019-21112001>Hi!</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D171012019-21112001></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D171012019-21112001>We're =
planning to=20
check-in the first pre-alpha version of the Finite Element Modeling =
(FEM)=20
code by the end of the next week. We'll be adding a lot of new =
files=20
(>50) and classes into the toolkit and I really don't want to screw =
something=20
up while doing this.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D171012019-21112001></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D171012019-21112001>So, =
can you give me=20
some guidelines on how to import some new code into itk=20
toolkit?</SPAN></FONT><FONT face=3DArial size=3D2><SPAN =
class=3D171012019-21112001>=20
Currently our FEM code is not a part of itk, but only uses the itk via =
the=20
#include statements. How do we make our files a part of itk, that will =
compile=20
as expected when checked out with the rest of the itk? Here I'm=20
particularly interested about what to do with=20
CMake.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D171012019-21112001></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D171012019-21112001>Where do we put=20
the files? Do we get a separate folder (called FEM???), or should =
we dump=20
everything in the common folder?</SPAN></FONT><FONT face=3DArial=20
size=3D2></DIV></FONT>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D171012019-21112001>Is it =
possible=20
(allowed?) to use another namespace within the itk namespace to mask =
internally=20
used classes? Since the FEM toolkit was originally developed =
independently of=20
itk, we currently use quite a few of them, and they really serve no =
purpose=20
outside the FEM framework.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D171012019-21112001></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D171012019-21112001>What =
is the status=20
of LightDataObject (or whatever it's called), which doesn't have =
regions?=20
Most of the Data Objects that we use don't have regions. It makes little =
sense=20
to, for example, apply only half of the prescribed boundary conditions =
or=20
material properties to the system. It would be nice if we all use =
the same=20
base classes (if they exist) to create corresponding data and =
process=20
objects.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D171012019-21112001></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D171012019-21112001>Any =
other comments=20
that you may have, are of course appreciated...</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D171012019-21112001></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Aljaz</FONT></DIV>
<DIV> </DIV></BODY></HTML>
------=_NextPart_000_0004_01C172A2.6A8C42D0--