|This task describes storage management principles involving manikins in the Human family of products.|
will allow you to reduce the number of manikin reference files to be
used for, in particular, complex and complete simulation scenarios where
a large number of workers need to be involved, and sometimes changed for
trying different modeling alternatives.
The only change is related to the Tools/Options page for Human Builder.
allowing you to decide the attributes to be saved on the reference and
those to be saved on an instance, we want to have the possibility to
make each manikin instance unique, but with regards to those attributes
that you have chosen to be locally overridden. This will also support
existing industrial scenarios where a reference manikin, put in
database, is shared by a large number of users, each user overriding
only one small aspect of the manikin locally. When saving the multiple
instances, the local change from each user is NOT expected to go back to
the reference, and therefore NOT impact all other users.
|A manikin is created in the same document as its father
product, thus avoiding file duplication in the saving process. Manikins
created in such a manner can further be imported into a new document, and
most importantly, manikins created with previous releases of the software
will import as well, without any particular required operation from the
user (no data migration needed). There is no duplication of files on the
user disk unless it is really necessary.