Views
Renumbering backend nodes & elements
There are a number of different ways to renumber nodes and elements in cmiss.
- In the backend I know of 2 options which are:
- 1) Use the CMISS utilities module 'RenumIp':
use CmUtils::RenumIp; renumIp("fitted_arm_6.ipnode",30,"fitted_arm_6.ipelem",30);POTENTIAL PROBLEM - if your mesh has versions, the nodes pertaining to your version numbers in your ipelem file will not be offset correctly
- 2) This option uses a function within cmiss:
fem renumber mesh node_offset 10 element_offset 10 region 1;POTENTIAL PROBLEM - if your mesh has versions, the nodes pertaining to your version numbers in your ipelem file will be incorrectly set to zero
- 1) Use the CMISS utilities module 'RenumIp':
- In the frontend:
- To ensure version numbers are offset correctly in the ipelem file, you can renumber the nodes and elements in CMGUI (the frontend) using the gfx change_identifier command, then export them to backend files using the command:
gfx export cm region name field coordinates ipcoor name.ipcoor ipbase name.ipbase ipnode name.ipnode ipelem name.ipelem; - This command is very useful! It will output your exnode and exelem into ipnode and ipelem files, at the same time it will output a coordinate and basis file. Note however that you cannot output only node and element files, you need to output coordinate & basis files for the command to work.
- To ensure version numbers are offset correctly in the ipelem file, you can renumber the nodes and elements in CMGUI (the frontend) using the gfx change_identifier command, then export them to backend files using the command: