- Mar 20, 2018
-
-
Andrew Heather authored
-
Andrew Heather authored
-
- Mar 19, 2018
-
-
Andrew Heather authored
-
- Mar 16, 2018
-
-
Mark OLESEN authored
-
- Mar 15, 2018
-
-
Mark OLESEN authored
- also ensure fewer side-effects from inplaceReorder - provide ListOps::reorder especially for PackedList and PackedBoolList since they behave differently from regular lists.
-
- Mar 14, 2018
-
-
Mark OLESEN authored
- this also provides a better separation of the intent (ie, inserting a single value, or inserting multiply values)
-
Andrew Heather authored
-
- Mar 13, 2018
-
-
Mark OLESEN authored
- using const reference to temporary was failing. Remedy by using a direct copy, which is a reasonable solution since surfZone content is quite minimal.
-
Andrew Heather authored
-
Andrew Heather authored
-
Andrew Heather authored
-
Mark OLESEN authored
- eliminate iterators from PackedList since they were unused, had lower performance than direct access and added unneeded complexity. - eliminate auto-vivify for the PackedList '[] operator. The set() method provides any required auto-vivification and removing this ability from the '[]' operator allows for a lower when accessing the values. Replaced the previous cascade of iterators with simpler reference class. PackedBoolList: - (temporarily) eliminate logic and addition operators since these contained partially unclear semantics. - the new test() method tests the value of a single bit position and returns a bool without any ambiguity caused by the return type (like the get() method), nor the const/non-const access (like operator[] has). The name corresponds to what std::bitset uses. - more consistent use of PackedBoolList test(), set(), unset() methods for fewer operation and clearer code. Eg, if (list.test(index)) ... | if (list[index]) ... if (!list.test(index)) ... | if (list[index] == 0u) ... list.set(index); | list[index] = 1u; list.unset(index); | list[index] = 0u; - deleted the operator=(const labelUList&) and replaced with a setMany() method for more clarity about the intended operation and to avoid any potential inadvertent behaviour.
-
- Mar 07, 2018
-
-
Mark OLESEN authored
- consistency with other containers. Allows range-for, enables various std algorithms, and can be used with ListOp::create() with an iterator range.
-
- Mar 15, 2018
-
-
Mark OLESEN authored
- clockValue class for managing the clock values only, with a null constructor that does not query the system clock (can defer to later). Can also be used directly for +/- operations. - refactor clockTime, cpuTime, clock to reduce storage.
-
- Mar 14, 2018
-
-
Mark OLESEN authored
-
Mark OLESEN authored
- make constexpr noexcept
-
- Mar 16, 2018
-
-
Andrew Heather authored
-
Andrew Heather authored
-
- Mar 06, 2018
-
-
Andrew Heather authored
-
- Feb 28, 2018
-
-
Mark OLESEN authored
- downgrades some diagnostics about nonconformant code from errors to warnings. Oddly enough, the errors actually arise from STL library elements shipped with gcc itself. Affects kahip compilation with gcc-6, gcc-7
-
Mark OLESEN authored
-
Mark OLESEN authored
-
- Feb 23, 2018
-
-
Andrew Heather authored
-
Andrew Heather authored
-
- Mar 15, 2018
-
-
sergio authored
-
sergio authored
-
Mattijs Janssens authored
Feature shortest path set See merge request OpenFOAM-plus!151
-
mattijs authored
-
mattijs authored
-
- Mar 14, 2018
-
-
- now only seed boundary faces and an internal face of cell that itself has a blocked face.
-
Mark OLESEN authored
- provides a simple means of writing an internal dimensioned field when fvMesh is not available (eg, during mesh creation).
-
mattijs authored
-
mattijs authored
-
- Mar 12, 2018
- Mar 08, 2018
- Feb 23, 2018
-
-
Mark OLESEN authored
-
Andrew Heather authored
The minimum number of particles per parcel can now be set in the injection model input, e.g.: model1 { type ...; massTotal ...; parcelBasisType ...; minParticlesPerParcel 1; <-- new optional entry SOI ...; ... Uses a value of 1 by default if the entry is not present. The value of 1 is generally recommended and beneficial for coupled cases where small time steps can lead to the injection of too many parcels and subsequently greatly over-predict the particle source contributions (momentum, heat, mass transfer etc)
-