Specifications

180
and it is rather heavy computationally. For this reason the BRep directory is structured to enable the user to
link applications to subsets of the body model such as the lower extremities or the shoulder model.
The idea behind the division into ARep and BRep is that each user wants to model the human body in a
special situation. This can take place in the ARep branch with references to the BRep branch but without
tampering with the more delicate BRep parts at all.
Let us stay with the BRep branch for just a moment. The initial models were created by the AnyBody
Research Group from Aalborg, Denmark, but from a rather early stage in the development, other groups of
model developers chipped in. So the BRep branch is divided into separate parts where each group of
developers can keep their own models:
When you develop an application you can choose to link to whatever body model is your favorite or even
choose to generate your own. You may also copy the models of another group into a separate directory and
introduce the changes you favor into it.
Body modeling is challenging because so much data is involved, so most users will - at least initially - prefer
to link to the body models that are already in the BRep branch. This means that the user will create an
application in the ARep directory that links to a number of model parts in the BRep directory. The ARep
directory is structured pretty much like the BRep branch:
Within each of the subdirectories in ARep you will find the different applications that each group has
developed, for instance: