curvepy issueshttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues2022-07-08T07:56:31Zhttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/40Monomialcurve overflowed2022-07-08T07:56:31ZLars QuentinMonomialcurve overflowedMaximilian WinklerTimo SpechtMaximilian Winklerhttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/39rename de_caes2022-02-05T03:11:59ZLars Quentinrename de_caesl o ll o lLars QuentinLars Quentinhttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/38Define a default bezier curve2022-05-23T15:49:14ZLars QuentinDefine a default bezier curvei.e. the sane choice for anyone who doesn't want to think further about it.
I think BezierCurveDeCaes is a great one.i.e. the sane choice for anyone who doesn't want to think further about it.
I think BezierCurveDeCaes is a great one.Timo SpechtTimo Spechthttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/37Properties der Bezierkurven mit Property-Based-Tests "beweisen"2021-12-07T10:33:35ZLars QuentinProperties der Bezierkurven mit Property-Based-Tests "beweisen"Beweis via "es klappt im kanonischen Fall"Beweis via "es klappt im kanonischen Fall"Lars QuentinLars Quentinhttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/35Version 1.0 auf PyPi releasen2023-01-23T14:26:11ZLars QuentinVersion 1.0 auf PyPi releasenLars QuentinMaximilian WinklerTimo SpechtLars Quentinhttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/34Repo am Ende aufraeumen2022-05-24T09:04:50ZLars QuentinRepo am Ende aufraeumen- [x] Alle TODOs
- [x] `debug`-Ordner entfernen
- [x] `ui_curvepy` entfernen
- [x] `requirements.txt`-Versionen sowie `python`-Dockerversion fixieren
- [x] dummy tests entfernen
- [ ] Ganze Gitlab-ci aufraeumen
- [x] Imports ordnen
- [x]...- [x] Alle TODOs
- [x] `debug`-Ordner entfernen
- [x] `ui_curvepy` entfernen
- [x] `requirements.txt`-Versionen sowie `python`-Dockerversion fixieren
- [x] dummy tests entfernen
- [ ] Ganze Gitlab-ci aufraeumen
- [x] Imports ordnen
- [x] Nirgends mehr generic `Exception`s mehr haben damit sie einfacher zu catchen sind
- [x] Tests splitten in `<test>.py` und `<test>_data.py`Lars QuentinMaximilian WinklerTimo SpechtLars Quentinhttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/33README sauber schreiben2022-07-11T07:35:09ZLars QuentinREADME sauber schreibenErst am absoluten Ende. Wahrscheinlich in PersonErst am absoluten Ende. Wahrscheinlich in PersonLars QuentinMaximilian WinklerTimo SpechtLars Quentinhttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/32DocStrings fuer jede Methode schreiben2022-07-11T07:30:38ZLars QuentinDocStrings fuer jede Methode schreibenIn Person, Termin: tbd
(absurd stark alkoholisiert)In Person, Termin: tbd
(absurd stark alkoholisiert)Lars QuentinMaximilian WinklerTimo SpechtLars Quentinhttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/31Unit Testscoverage erhoehen2021-12-07T10:34:00ZLars QuentinUnit Testscoverage erhoehen- [x] `bezier_curve.py`
- [x] `de_caes.py` (WIP Timo)
- [x] `delaunay.py`
- [x] `types.py` (WIP Maxi)
- [x] `utilities.py`(WIP Lars)
- [x] `voronoi.py`- [x] `bezier_curve.py`
- [x] `de_caes.py` (WIP Timo)
- [x] `delaunay.py`
- [x] `types.py` (WIP Maxi)
- [x] `utilities.py`(WIP Lars)
- [x] `voronoi.py`Lars QuentinMaximilian WinklerTimo SpechtLars Quentinhttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/30Implement Dirichlet Tessellations/Voronoi Diagrams based on Delaunay Triangul...2021-07-25T12:58:19ZLars QuentinImplement Dirichlet Tessellations/Voronoi Diagrams based on Delaunay TriangulationsLars QuentinLars Quentinhttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/29Clear up master branch2021-06-26T17:02:44ZLars QuentinClear up master branchLars QuentinLars Quentinhttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/28Implement affine parameter transformations for bezier curves2021-10-17T08:35:14ZLars QuentinImplement affine parameter transformations for bezier curvesThis just makes sense when testing is properly implemented as it has to be validated numerically, not just geometrically by comparing graphsThis just makes sense when testing is properly implemented as it has to be validated numerically, not just geometrically by comparing graphshttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/27Change complex docstring types to typing values2021-10-17T08:35:17ZLars QuentinChange complex docstring types to typing valuesFor example, when using a List, instead of
```
x: list
Lorem ipsum dolor sit amet
```
one should use
```python
from typing import List
...
x: List[float]
Lorem ipsum dolor sit amet
```
as it is more verbose and
```python
x: list[floa...For example, when using a List, instead of
```
x: list
Lorem ipsum dolor sit amet
```
one should use
```python
from typing import List
...
x: List[float]
Lorem ipsum dolor sit amet
```
as it is more verbose and
```python
x: list[float]
Lorem ipsum dolor sit amet
```
is undefinedhttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/26AbstractBezierCurve.box can be used uninitialized2021-10-17T08:35:19ZLars QuentinAbstractBezierCurve.box can be used uninitializedInitialized in `AbstractBezierCurve.__init__`, the `box` attribute is public but lazily generated iff `min_max_box()` (or `curve`) got called before. This is bad, especially if someone wants to use `box_collision_check`.
Although `mix_m...Initialized in `AbstractBezierCurve.__init__`, the `box` attribute is public but lazily generated iff `min_max_box()` (or `curve`) got called before. This is bad, especially if someone wants to use `box_collision_check`.
Although `mix_max_box()` just has to be computed once since it's Complexity is `nlogn` I'd prefer to have it lazy.
I recommend to solve it analogously to #20 with `@cached_property`https://gitlab.gwdg.de/numerikgang/curvepy/-/issues/25Make all Subclasses of AbstractBezierCurve statically callable (where it make...2021-01-17T09:30:37ZLars QuentinMake all Subclasses of AbstractBezierCurve statically callable (where it makes sense at least)Analogously like I implemented it in BernsteinPoly that a Class respresenting a function, when all parameters specified, does immediately get reduced to a primitive valueAnalogously like I implemented it in BernsteinPoly that a Class respresenting a function, when all parameters specified, does immediately get reduced to a primitive valuehttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/24Refactor Tholder into an generic multithreaded iterator class2021-10-17T08:35:32ZLars QuentinRefactor Tholder into an generic multithreaded iterator classAs shown [here](https://docs.python.org/3/library/collections.abc.html), I'd say the most beautiful way would be to inherit from `collections.abc.Iterator`, since
1. Once we implement `__next__` we get `__iter__` for free
2. Mixins are ...As shown [here](https://docs.python.org/3/library/collections.abc.html), I'd say the most beautiful way would be to inherit from `collections.abc.Iterator`, since
1. Once we implement `__next__` we get `__iter__` for free
2. Mixins are Python best practises
3. Inheriting from sth called `Iterator` is a great way to explain the classes semantic usage
For the concept of mixins is [this](https://rednafi.github.io/digressions/python/2020/07/03/python-mixins.html) the best literature I've ever read, [that](https://www.youtube.com/watch?v=zVFLBfqV-q0) should suffice as wellhttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/23implement property based tests for chapter 32021-07-17T14:50:26ZLars Quentinimplement property based tests for chapter 3Since we use those tests as implicit documentation of known theorems it is mandatory to
- either write small proofs as $`\LaTeX`$ in the Docstring, see the `pdoc3` for syntax examples
- reference the according literature for the proofs, ...Since we use those tests as implicit documentation of known theorems it is mandatory to
- either write small proofs as $`\LaTeX`$ in the Docstring, see the `pdoc3` for syntax examples
- reference the according literature for the proofs, preferably freely accessible links. If it is not obvious that the link will be alive in a few years (think wikipedia/Wolfram's mathworld) please use [the wayback machine](https://archive.org/web/)https://gitlab.gwdg.de/numerikgang/curvepy/-/issues/22Implement unit tests for chapter 32021-10-17T08:35:32ZLars QuentinImplement unit tests for chapter 3Maximilian WinklerMaximilian Winklerhttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/21First Implementation of Chapter 32021-10-17T08:35:32ZLars QuentinFirst Implementation of Chapter 3This implementation will stand on it's own and will not be structurally merged into the source code.
Once this is done the structual merge could be planned.This implementation will stand on it's own and will not be structurally merged into the source code.
Once this is done the structual merge could be planned.Maximilian WinklerMaximilian Winklerhttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/20Use functools caching for `AbstractBezierCurve._curve`2021-10-17T08:35:32ZLars QuentinUse functools caching for `AbstractBezierCurve._curve`See https://docs.python.org/3/library/functools.html#functools.cached_property
this _should_ work as long as we enforce the immutability of the bezier curve objects
Currently we are caching manually w/ `AbstractBezierCurve._get_or_crea...See https://docs.python.org/3/library/functools.html#functools.cached_property
this _should_ work as long as we enforce the immutability of the bezier curve objects
Currently we are caching manually w/ `AbstractBezierCurve._get_or_create_values()`
Iff that works, I think it should work w/ `AbstractBezierCurve.curve`, `AbstractBezierCurve.min_max_box` and even `AbstractBezierCurve.plot` as well.