Making a finite element code easier to maintain is achieved by further modulaizing it. Due to its two levels of modularity (of procedures and data), object-oriented programming is the method of choice. Its potential is investigated in two bottle-necks of finite element programming where so far it has not proved significantly more successful than classical Fortran programming. The first of these is lack of adequate data structures between the analysis specifications and the basic objects of the finite element method, like the element and the node. This is solved by defining two classes of objects, namely Problem and Domain, with clearly differentiated specifications. The second gap deals with solving linear equation systems. Introducing an intermediate class Unassembled Matrix allows alternative storage/solving schemes to be implemented in a very flexible manner.
DUBOIS-PELERIN Yves;
PEGON Pierre;
1996-09-30
JRC13896
https://publications.jrc.ec.europa.eu/repository/handle/JRC13896,
| Name | Country | City | Type |
|---|
This document is only visible at the Commission level.
You are not authorized to publish or distribute it outside the European Commission.
This is a public document. You can share this publication.
Datasets
| ID | Title | Public URL |
|---|
Dataset collections
| ID | Acronym | Title | Public URL |
|---|
Scripts / source codes
| Description | Public URL |
|---|
Additional supporting files
| File name | Description | File type |
|---|