I repeat the same again, the normal way is to assign data to geometry, not to mesh!!
![usual_assing_data_on_geometry.png](./download/file.php?id=890&sid=ea2cc2c5ef537f36da60803f16426836)
- usual_assing_data_on_geometry.png (67.73 KiB) Viewed 19133 times
then generate the mesh. You can see drawing the condition by colors that the correct faces of the triangles are marked (note that they don't exists line elements, only triangle elements
![mesh_inherit_data.png](./download/file.php?id=891&sid=ea2cc2c5ef537f36da60803f16426836)
- mesh_inherit_data.png (84.29 KiB) Viewed 19133 times
You can also directly assign to mesh faces, but is harder (but you can use all selection options)
![manual_mesh_assign_data_unrecommended.png](./download/file.php?id=892&sid=ea2cc2c5ef537f36da60803f16426836)
- manual_mesh_assign_data_unrecommended.png (94.21 KiB) Viewed 19133 times
And about the other comment: for a 2D model with triangles must not define a condition
CONDTYPE: over surfaces
CONDMESHTYPE:
over face elements
Do you want to select the whole triangles themselves, must be 'over body elements' not 'over face elements' !!
(and the loop in the .bas to write it must be off course according to the kind of data)
It has sense to define a condition
CONDTYPE: over surfaces
CONDMESHTYPE: over face elements
if do you have a volume model, with tetrahedra, hexahedra, prisms or pyramids, and you are not also explicitly generating the boundary surface elements (triangles or quadrilaterals) and whan't to attach the condition data to a face of a volume element (face 1 to 4 or a tetra, 1 to 6 of an hexa, etc.)
And in a volume mesh will be much better to assign data to geometric surfaces, do it manually on all mesh elements could be a nightmare.