Skip to content
Snippets Groups Projects
  1. Nov 26, 2021
  2. Nov 25, 2021
    • Mark OLESEN's avatar
    • Mark OLESEN's avatar
      f459b11e
    • Mark OLESEN's avatar
      CONFIG: add build information into shell session · bcf8a48c
      Mark OLESEN authored
      - more closely reflect what the binaries report
      - report the installation path
      - change PS1 case/separator to roughly correspond to package names
      
      STYLE: adjust README to mention upcoming v2112
      bcf8a48c
    • Mark OLESEN's avatar
      ENH: additional #word and #message dictionary directives (#2276) · 1804d3fe
      Mark OLESEN authored
      - use `#word` to concatenate, expand content with the resulting string
        being treated as a word token. Can be used in dictionary or
        primitive context.
      
        In dictionary context, it fills the gap for constructing dictionary
        names on-the-fly. For example,
      
        ```
        #word "some_prefix_solverInfo_${application}"
        {
            type    solverInfo;
            libs    (utilityFunctionObjects);
            ...
        }
        ```
      
        The '#word' directive will automatically squeeze out non-word
        characters. In the block content form, it will also strip out
        comments. This means that this type of content should also work:
      
        ```
        #word {
           some_prefix_solverInfo
           /* Appended with application name (if defined) */
           ${application:+_}  // Use '_' separator
           ${application}     // The application
        }
        {
            type    solverInfo;
            libs    (utilityFunctionObjects);
            ...
        }
        ```
        This is admittedly quite ugly, but illustrates its capabilities.
      
      - use `#message` to report expanded string content to stderr.
        For example,
      
        ```
        T
        {
           solver          PBiCG;
           preconditioner  DILU;
           tolerance       1e-10;
           relTol          0;
           #message "using solver: $solver"
        }
        ```
        Only reports on the master node.
      1804d3fe
    • Mark OLESEN's avatar
      BUG: missing unit-normal weighting for surfaceFieldValue (fixes #2273) · 55af2fc2
      Mark OLESEN authored
      - when using a vector field for weighting, it either used mag()
        or mag * area, but did not have a unit-normal projection version
      55af2fc2
  3. Nov 24, 2021
  4. Nov 23, 2021
  5. Nov 22, 2021
  6. Nov 17, 2021
  7. Nov 15, 2021
  8. Nov 11, 2021
  9. Nov 10, 2021