User Tools

Site Tools


new-input-files

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
new-input-files [2013/05/28 13:58]
mikael.ohman
new-input-files [2013/06/03 14:12]
mikael.ohman
Line 2: Line 2:
  
   - Renaming of elements. As suggested in the meeting in Prague (April 2013) we need to rethink the naming conventions for elements. Names should specify, in order: problem type, geometric type, order. The names need not be perfect (it gets tricky with specialized structural elements) but should reveal enough about the implementation to make them easy to understand.   - Renaming of elements. As suggested in the meeting in Prague (April 2013) we need to rethink the naming conventions for elements. Names should specify, in order: problem type, geometric type, order. The names need not be perfect (it gets tricky with specialized structural elements) but should reveal enough about the implementation to make them easy to understand.
-  - No default dofs from the domain anymore: The "​domain **domaintype**"​ should be removed. The number of spatial dimensions should instead be set directly by the input field "nsd #" in the domain record. +  - No default dofs from the domain anymore: The "​domain **domaintype**"​ should be removed. ​**Replacement:​** ​The number of spatial dimensions should instead be set directly by the input field "nsd #" in the domain record. 
-  - Dirichlet boundary conditions should be applied to sets instead of directly on dofs. The standard dirichlet b.c. should also take a vector argument for the prescribed values, to go along with "​dofs",​ e.g. "dofs 3 1 2 3 value 3 0. 0. 1." which denotes that: D_u = 0., D_v = 1, D_w = 1.+  - Dirichlet boundary conditions should be applied to sets instead of directly on dofs. The standard dirichlet b.c. should also take a vector argument for the prescribed values, to go along with "​dofs",​ e.g. "dofs 3 1 2 3 value 3 0. 0. 1." which denotes that: D_u = 0., D_v = 1, D_w = 1. **Replacement:​** The input field "​values"​ has been added to the dirichlet b.c. to work as described with the "​dofs"​ field. It is still backwards compatible.
   - With no more default dofs from the domain type, controlling dof-type in hangingnode,​ slavenode or rigidarmnode should be done by supplying the optional "​dofidmask"​ field.   - With no more default dofs from the domain type, controlling dof-type in hangingnode,​ slavenode or rigidarmnode should be done by supplying the optional "​dofidmask"​ field.
   - LoadTimeFunction should be renamed to simply "​TimeFunction"​ as they are used generally.   - LoadTimeFunction should be renamed to simply "​TimeFunction"​ as they are used generally.
   - Nonlinearstatic should use the normal newton solver by default.   - Nonlinearstatic should use the normal newton solver by default.
   - NodalLoad should use the "​dofs"​ input field to determine which components are directly loaded.   - NodalLoad should use the "​dofs"​ input field to determine which components are directly loaded.
new-input-files.txt · Last modified: 2013/06/09 00:17 by mikael.ohman