- 28 Apr, 2019 1 commit
-
-
Mark Olesen authored
- Eg, with surface writers now in surfMesh, there are fewer libraries depending on conversion and sampling. COMP: regularize linkage ordering and avoid some implicit linkage (#1238)
-
- 26 Apr, 2019 1 commit
-
-
Mark Olesen authored
- avoids unnecessary cyclic dependency
-
- 10 Apr, 2019 1 commit
-
- 08 Apr, 2019 1 commit
-
-
mattijs authored
-
- 21 Feb, 2019 1 commit
-
-
sergio authored
and reading dpdt in one basicThermo constructor
-
- 13 Feb, 2019 1 commit
-
-
Mark Olesen authored
-
- 01 Feb, 2019 1 commit
-
-
sergio authored
from e to T. T proved to be more generic solution.
-
- 07 Jan, 2019 1 commit
-
-
Mark Olesen authored
- reduced clutter when iterating over containers
-
- 03 Jan, 2019 1 commit
-
-
Mark Olesen authored
- provide a lookupOrDefault constructor form, since this is a fairly commonly used requirement and simplifies the calling sequence. Before dimensionedScalar rhoMax ( dimensionedScalar::lookupOrDefault ( "rhoMax", pimple.dict(), dimDensity, GREAT ) ); After dimensionedScalar rhoMax("rhoMax", dimDensity, GREAT, pimple.dict()); - read, readIfPresent methods with alternative lookup names. - Mark the Istream related constructors with compile-time deprecated warnings. BUG: read, readIfPresent methods not handling optional dimensions (#1148)
-
- 11 Dec, 2018 2 commits
-
-
Mark Olesen authored
- makes the intent clearer and avoids the need for additional constructor casting. Eg, labelList(10, Zero) vs. labelList(10, 0) scalarField(10, Zero) vs. scalarField(10, scalar(0)) vectorField(10, Zero) vs. vectorField(10, vector::zero)
-
Mark Olesen authored
-
- 13 Dec, 2018 1 commit
-
-
Mark Olesen authored
- for some special cases we wish to mark command-line arguments as being optional, in order to do our own treatment. For example, when an arbitrary number of arguments should be allowed. Now tag this situation with argList::noMandatoryArgs(). The argList::argsMandatory() query can then be used in any further logic, including the standard default argument checking. - with the new default check, can consolidate the special-purpose "setRootCaseNonMandatoryArgs.H" into the regular "setRootCase.H" - revert to a simple "setRootCase.H" and move all the listing related bits to a "setRootCaseLists.H" file. This leaves the information available for solvers, or whoever else wishes, without being introduced everywhere. - add include guards and scoping to the listing files and rename to something less generic. listOptions.H -> setRootCaseListOptions.H listOutput.H -> setRootCaseListOutput.H
-
- 20 Nov, 2018 1 commit
-
-
Mark Olesen authored
- deprecate dimensionedType constructors using an Istream in favour of versions accepting a keyword and a dictionary. Dictionary entries are almost the exclusive means of read constructing a dimensionedType. By construct from the dictionary entry instead of doing a lookup() first, we can detect possible input errors such as too many tokens as a result of a input syntax error. Constructing a dimensionedType from a dictionary entry now has two forms. 1. dimensionedType(key, dims, dict); This is the constructor that will normally be used. It accepts entries with optional leading names and/or dimensions. If the entry contains dimensions, they are verified against the expected dimensions and an IOError is raised if they do not correspond. On conclusion, checks the token stream for any trailing rubbish. 2. dimensionedType(key, dict); This constructor is used less frequently. Similar to the previous description, except that it is initially dimensionless. If entry contains dimensions, they are used without further verification. The constructor also includes a token stream check. This constructor is useful when the dimensions are entirely defined from the dictionary input, but also when handling transition code where the input dimensions are not obvious from the source. This constructor can also be handy when obtaining values from a dictionary without needing to worry about the input dimensions. For example, Info<< "rho: " << dimensionedScalar("rho", dict).value() << nl; This will accept a large range of inputs without hassle. ENH: consistent handling of dimensionedType for inputs (#1083) BUG: incorrect Omega dimensions (fixes #2084)
-
- 12 Oct, 2018 1 commit
-
-
Mark Olesen authored
- use the dictionary 'get' methods instead of readScalar for additional checking Unchecked: readScalar(dict.lookup("key")); Checked: dict.get<scalar>("key"); - In templated classes that also inherit from a dictionary, an additional 'template' keyword will be required. Eg, this->coeffsDict().template get<scalar>("key"); For this common use case, the predefined getXXX shortcuts may be useful. Eg, this->coeffsDict().getScalar("key");
-
- 05 Oct, 2018 1 commit
-
-
Mark Olesen authored
- instead of dict.lookup(name) >> val; can use dict.readEntry(name, val); for checking of input token sizes. This helps catch certain types of input errors: { key1 ; // <- Missing value key2 1234 // <- Missing ';' terminator key3 val; } STYLE: readIfPresent() instead of 'if found ...' in a few more places.
-
- 30 May, 2018 1 commit
-
-
Mark Olesen authored
- make the purpose more explicit, and reduces some work for the compiler as well.
-
- 27 Apr, 2018 1 commit
-
-
Mark Olesen authored
- controlled by the the 'printExecutionFormat' InfoSwitch in etc/controlDict // Style for "ExecutionTime = " output // - 0 = seconds (with trailing 's') // - 1 = day-hh:mm:ss ExecutionTime = 112135.2 s ClockTime = 113017 s ExecutionTime = 1-07:08:55.20 ClockTime = 1-07:23:37 - Callable via the new Time::printExecutionTime() method, which also helps to reduce clutter in the applications. Eg, runTime.printExecutionTime(Info); vs Info<< "ExecutionTime = " << runTime.elapsedCpuTime() << " s" << " ClockTime = " << runTime.elapsedClockTime() << " s" << nl << endl; -- ENH: return elapsedClockTime() and clockTimeIncrement as double - previously returned as time_t, which is less portable.
-
- 24 Apr, 2018 1 commit
-
-
Mark Olesen authored
- generalize some of the library extensions (.so vs .dylib). Provide as wmake 'sysFunctions' - added note about unsupported/incomplete system support - centralize detection of ThirdParty packages into wmake/ subdirectory by providing a series of scripts in the spirit of GNU autoconfig. For example, have_boost, have_readline, have_scotch, ... Each of the `have_<package>` scripts will generally provide the following type of functions: have_<package> # detection no_<package> # reset echo_<package> # echoing and the following type of variables: HAVE_<package> # unset or 'true' <package>_ARCH_PATH # root for <package> <package>_INC_DIR # include directory for <package> <package>_LIB_DIR # library directory for <package> This simplifies the calling scripts: if have_metis then wmake metisDecomp fi As well as reducing clutter in the corresponding Make/options: EXE_INC = \ -I$(METIS_INC_DIR) \ -I../decompositionMethods/lnInclude LIB_LIBS = \ -L$(METIS_LIB_DIR) -lmetis Any additional modifications (platform-specific or for an external build system) can now be made centrally.
-
- 28 Mar, 2018 1 commit
-
-
Andrew Heather authored
-
- 21 Mar, 2018 1 commit
-
-
Mark Olesen authored
- both autoPtr and tmp are defined with an implicit construct from nullptr (but with explicit construct from a pointer to null). Thus is it safe to use 'nullptr' when returning an empty autoPtr or tmp.
-
- 16 Mar, 2018 1 commit
-
-
Mark Olesen authored
- when constructing dimensioned fields that are to be zero-initialized, it is preferrable to use a form such as dimensionedScalar(dims, Zero) dimensionedVector(dims, Zero) rather than dimensionedScalar("0", dims, 0) dimensionedVector("zero", dims, vector::zero) This reduces clutter and also avoids any suggestion that the name of the dimensioned quantity has any influence on the field's name. An even shorter version is possible. Eg, dimensionedScalar(dims) but reduces the clarity of meaning. - NB: UniformDimensionedField is an exception to these style changes since it does use the name of the dimensioned type (instead of the regIOobject).
-
- 08 Dec, 2017 2 commits
- 07 Nov, 2017 2 commits
-
-
Andrew Heather authored
-
Andrew Heather authored
-
- 13 Jul, 2018 1 commit
-
-
Mark Olesen authored
- use scalar(0) instead of scalar(0.0) etc
-
- 02 Jul, 2018 1 commit
-
-
Mark Olesen authored
- relocate some standard functionality to TimePaths to allow a lighter means of managing time directories without using the entire Time mechanism. - optional enableLibs for Time construction (default is on) and a corresponding argList::noLibs() and "-no-libs" option STYLE: - mark Time::outputTime() as deprecated MAY-2016 - use pre-increment for runTime, although there is no difference in behaviour or performance.
-
- 22 Nov, 2017 1 commit
-
-
Mark Olesen authored
- in most cases already checked valid() so don't need additional check for setting an existing pointer
-
- 11 Jan, 2018 1 commit
-
-
Andrew Heather authored
-
- 17 May, 2018 1 commit
-
-
mattijs authored
-
- 14 May, 2018 1 commit
-
-
Andrew Heather authored
-
- 11 May, 2018 1 commit
-
-
Andrew Heather authored
-
- 19 Jul, 2017 1 commit
-
-
Andrew Heather authored
-