[SOLVED] How sofa folders hierarchy is organized?

[Noura]

Hello,

I’m confused by the folders hierarchy in SOFA.

Basiclly, the SofaKernel directory.

– Is there some reason to separate the directory SofaKernel/modules from SofaKernel/framework/sofa/core? Aren’t modules part of the core? is there a difference between SofaKernel and the core?

The question comes to mind when looking at some common used components in Sofa for example: constraints, contacts, and forcefields.

— constraints classes are placed in
/SofaKernel/framework/sofa/core/behavior

— some of contact classes are in
src/SofaKernel/framework/sofa/core/collision
while others are in
src/SofaKernel/modules/[BaseCollision/MeshCollision/etc.]

— some of ForceFields classes are in
/src/SofaKernel/framework/sofa/core/behavior
others in
src/SofaKernel/modules/Sofa[Deformable/Rigid/SimpleFem/etc.]

I know that this maybe somehow not easy to explain, but I would appreciate any enlightening about the organization of the files.

Thanks,

Noura

[Hugo]

Hey Noura,

You’re right, the folder hierarchy can be somehow confusing. But a new refactoring will be proposed soon. Stay tuned 😉

The idea of SofaKernel was to gather most-used components:
– it includes the base/abstract classes of classes (usually in SofaKernel/framework)
– and it also includes implementations of these classes (usually in SofaKernel/modules)

But the future refactoring (by the end of 2017) should ease the understanding of the folder architecture.

Best,

Hugo

[Noura]

Hi Hugo,

Thanks for the clue that abstract classes are grouped in the framework directory.

It is also interesting to know about the upcoming architecture. Nice project!

Noura

[Author]

Posts