Changes between Version 26 and Version 30 of Ticket #28519


Ignore:
Timestamp:
09/25/19 21:58:30 (19 months ago)
Author:
gh-DeRhamSource
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #28519

    • Property Status changed from needs_review to needs_work
    • Property Commit changed from 7d10da93ff7b239c42d2dcb5d96e81cd9e11971a to cf12def3b962118ecc4c3e7d6e2825f0a0b68a43
  • Ticket #28519 – Description

    v26 v30  
    99**Scalar Fields**
    1010
    11 - scalar field can be partially defined in one top chart domain, so the display method was misleading in this case. This is now fixed: the `display()` method shows ''all'' the known expressions. For each such expression, the greatest domain, where this expression is known, is displayed.
     11- scalar field can be partially defined in one top chart domain, so the display method was misleading in this case. This is now fixed: the `display()` method shows ''all'' known expressions. For each such expression, the greatest domain, where this expression is known, is displayed.
    1212- now, multiplication of named scalar fields `f` and `g` leads to `f \cdot g` in LaTeX code
    1313- division by zero in `_div_()` is now checked via `is_trivial_zero()`
     
    1515** Differential Forms / Tensor Fields**
    1616
    17 - wedge product computation in case `zero` simplified
    18 - tensor field addition in case `zero` simplified
     17- tensor algebra computations for the case `zero` simplified: in order to make computations faster, an attribute `_is_field` is added (similar to scalar fields)
     18- multiplication of tensor fields `a` with scalar fields `f` yields name `f*a` and latex name `f \cdot a`
    1919
    2020**Various**
     
    2525  - coercion via restriction rearranged in scalar fields following tensor fields
    2626- minor code rearrangements, i.e. for code reuse or consistency
     27- copies take the attribute `_is_field` from original in method `copy` (both for tensor fields and scalar fields) to ensure zero treatment