full_syntax

This shows you the differences between two versions of the page.

Both sides previous revision Previous revision Next revision | Previous revision | ||

full_syntax [2019/10/10 13:45] marijn.nijenhuis |
full_syntax [2019/10/10 13:50] marijn.nijenhuis [5. Optional] |
||
---|---|---|---|

Line 92: | Line 92: | ||

- the last load step is due to both the full initial and full standard load. | - the last load step is due to both the full initial and full standard load. | ||

- | The same holds for prescribing //standard// displacement (''displ_{x,y,z}'') and //initial// displacement (''displ_initial_{x,y,z}''). | + | The same holds for prescribing //standard// displacement (''displ_{x,y,z}''), //initial// displacement (''displ_initial_{x,y,z}''), //standard// rotation (''rot'') and //initial// rotation (''rot_initial''). |

==== 4. Element properties ==== | ==== 4. Element properties ==== | ||

Line 146: | Line 147: | ||

| ''filename'' | string | Filename of the data files involved in the SPACAR simulation. If omitted, filenname 'spacar_file' is used. | | | ''filename'' | string | Filename of the data files involved in the SPACAR simulation. If omitted, filenname 'spacar_file' is used. | | ||

| ''silent'' | ''true'' | Activation of 'silent' mode of SPACAR Light. In the silent mode, the input arguments (''nodes'', ''elements'', ''nprops'', ''eprops'', ''rls'') are not validated and not checked for errors (improving speed). Also, visualization after simulation is turned off. This feature can be useful when e.g. running a lot of SPACAR Light simulations in an optimization or iteration loop. | | | ''silent'' | ''true'' | Activation of 'silent' mode of SPACAR Light. In the silent mode, the input arguments (''nodes'', ''elements'', ''nprops'', ''eprops'', ''rls'') are not validated and not checked for errors (improving speed). Also, visualization after simulation is turned off. This feature can be useful when e.g. running a lot of SPACAR Light simulations in an optimization or iteration loop. | | ||

- | | ''calcbuck'' | ''true'' | Calculation of buckling loads. Multipliers with respect to the combined applied load are returned. Input displacements cannot be used with this option. It is recommended to only apply a single force or moment to the system. Note that the loads ''nprops(i).force'' and ''nprops(i).moment'' are applied in (linearly increasing) steps: they only reach the user-specified value at the last step. The multipliers are calculated with respect to the current load at each of these steps. | | + | | ''calcbuck'' | ''true'' | Calculation of buckling loads. Multipliers with respect to the combined applied load are returned. It is recommended to only apply a single force or moment to the system. Whenever input displacements or rotations are used, the multipliers are also with respect to the equivalent reaction loads. Note that the loads ''nprops(i).force'' and ''nprops(i).moment'' are applied in (linearly increasing) steps: they only reach the user-specified value at the last step. The multipliers are calculated with respect to the current load at each of these steps. | |

| ''calccompl'' | ''false'' | Disable calculation of compliance matrices of the nodes.| | | ''calccompl'' | ''false'' | Disable calculation of compliance matrices of the nodes.| | ||

| ''gravity'' | 1x3 vector | Loads due to gravity. Values represent the components of the gravitational acceleration in ''x''-, ''y''-, and ''z''-direction (in unit m/s<sup>2</sup>). For example: ''[0 0 -9.81]''. | | | ''gravity'' | 1x3 vector | Loads due to gravity. Values represent the components of the gravitational acceleration in ''x''-, ''y''-, and ''z''-direction (in unit m/s<sup>2</sup>). For example: ''[0 0 -9.81]''. | |

full_syntax.txt · Last modified: 2019/10/10 13:50 by marijn.nijenhuis