1. Objective of the exercise#

We propose to create a new macro-command that converts a mesh from the format ASTER, GIBI or GMSH in MED format and create a table containing some information extracted from the mesh.

Here is the intended use case:

tab1 = CONV_MAIL_MED (UNITE_IN =20, INFO =2)

tab2 = CONV_MAIL_MED (UNITE_IN =21, FORMAT_IN =" GMSH ", UNITE_OUT =81, INFO =2)

tab3 = CONV_MAIL_MED (UNITE_IN =22, FORMAT_IN =" GIBI ", UNITE_OUT =82, INFO =2)

Different meshes are used, one in each format. It is verified that the number of nodes and meshes entered in the tables produced are the expected ones.

It is a good practice to start a development by writing the layout data and therefore the test case that we want to arrive at, even if it is only a draft.

A test case should be:

  • small in size (a few seconds of time CPU, mesh with the minimum number of meshes);

  • easy to understand (few lines) and should cover a single feature (elementary test), all configurations and keywords;

  • example: should not trigger alarms (by default, an alarm in a test case produced an error);

  • documented: in the validation manual.