- ... ``algorithm
- Within TCAD applications models are represented by
certain data structures and algorithms working on them. Therefore the
Algorithm Library concepts do not distinct between Model classes which are
representing physical models and Model classes representing not
physically motivated algorithms and data structures.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...
library:
- An example can be found in
Appendix A.4.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...s:alib:casetoolinterface):
- Examples can be found in
Appendix A.3.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...exa:alib:extramodellibvmfile.
- An application example
demonstrating the generation of such extension libraries can be found
in Appendix A
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...exa:mdl:submultipleinheritexa.
- While this example is for sure not requiring advanced features
like aggregation or inheritance, it is chosen because it depicts the
features of MDL in a complete example requiring very few lines of
actual code.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.