Changes between Version 5 and Version 8 of Ticket #28519
- Timestamp:
- 09/23/19 07:28:14 (19 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #28519
-
Property
Status
changed from
new
toneeds_review
-
Property
Branch
changed from
to
u/gh-DeRhamSource/mixed_forms_improvements
-
Property
Commit
changed from
to
786c32297948142bc75ba0927a41d2520a634576
-
Property
Status
changed from
-
Ticket #28519 – Description
v5 v8 1 **Mixed Forms** 2 1 3 - readability of code improved in `mixed_form.py` and `mixed_form_algebra.py` 2 4 - now, mixed form components are declared as copies 5 - `set_form_name()` method is added 6 7 **Scalar Fields** 8 9 - 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 chart on greatest domain, where this is expression is known, is displayed. 10 - now, multiplication of named scalar fields `f` and `g` leads to `f \cdot g` in LaTeX code 11 - division by zero in `_div_()` is now checked via `is_trivial_zero()` 12 13 **Various** 14 3 15 - more consistency between scalar fields and tensor fields: 4 16 - a copy of scalar fields took the name from the original, a copy of tensor fields did not; now, a copy takes the name in any case 5 - method `set_restriction` added to scalar fields 6 - scalar field can be partially defined in one top chart domains, so the display method was misleading in this case; this will be fixed 7 - now, multiplication of named scalar fields `f` and `g` leads to `f \cdot g` in LaTeX code 8 - other minor improvements (see commit [soon...]) 17 - method `set_restriction()` added to scalar fields 18 - minor code rearrangements, i.e. for code reuse or consistency