THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#184 - Naming conventions
User who did this - Nicolas Schwenck (Nicolas)
Reason for closing: Implemented
Additional comments about closing: Documented. Will never be finished. Everyone
should make sure that naming
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#184 - Naming conventions
User who did this - Beatrix Becker (Beatrix)
--
Implementation of the naming conventions will be investigated during the next
Dumux day.
--
More information can
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#184 - Naming conventions
User who did this - Nicolas Schwenck (Nicolas)
--
by comparing the decoupled and the implicit models I realized that there are
still different names for the same things
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#184 - Naming conventions
User who did this - Katherina Baber (kathinka)
--
I had a look at the list of Tianyuan in
dumux-devel/doc/naminglist/naming_conventions.ods.
The first sheet contains
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#184 - Naming conventions
User who did this - Thomas Fetzer (Thomas Fetzer)
--
Here is one possibility to get rid of undesired variable names (expemlarily for
the ElementIterator type and eIt or
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#184 - Naming conventions
User who did this - Thomas Fetzer (Thomas Fetzer)
--
I\'ll try to find a HiWi, who creates a list with the suggested subgroups and
optionally brings forward the
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#184 - Naming conventions
User who did this - Bernd Flemisch (bernd)
--
The list should be categorized into more subgroups like \Indices\, for
example, \FluxVariables/Data\, \Problem\ ...
A HiWi
