curvepy issueshttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues2023-01-23T14:26:11Zhttps://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/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/40Monomialcurve overflowed2022-07-08T07:56:31ZLars QuentinMonomialcurve overflowedMaximilian WinklerTimo SpechtMaximilian Winklerhttps://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/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/39rename de_caes2022-02-05T03:11:59ZLars Quentinrename de_caesl o ll o lLars QuentinLars 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/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/9Adding a CONTRIBUTING.rst for merge requests2021-10-17T08:35:33ZLars QuentinAdding a CONTRIBUTING.rst for merge requestsSee [this](https://gitlab.com/BuildGrid/buildgrid/blob/master/CONTRIBUTING.rst) for a good exampleSee [this](https://gitlab.com/BuildGrid/buildgrid/blob/master/CONTRIBUTING.rst) for a good examplehttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/4implement a setup.py as well as setup.cfg2021-10-17T08:35:33ZLars Quentinimplement a setup.py as well as setup.cfghttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/13Implement Blossoming for Chapter 42021-10-17T08:35:33ZLars QuentinImplement Blossoming for Chapter 4This can just be done after it is morged with chapter 5 to avoid unnecessary overlap
Obviously, all blossom properties have to be shown with property based testingThis can just be done after it is morged with chapter 5 to avoid unnecessary overlap
Obviously, all blossom properties have to be shown with property based testinghttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/18Implement structure for Chapter 52021-10-17T08:35:33ZLars QuentinImplement structure for Chapter 5Mostly merging different computational approaches into the current structure of `bezier_curves.py`, derivatives, maybe composite curves, ...
basically everything not mentioned in 5.8Mostly merging different computational approaches into the current structure of `bezier_curves.py`, derivatives, maybe composite curves, ...
basically everything not mentioned in 5.8Lars QuentinLars Quentinhttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/6Evaluate different multiprocessing architectures2021-10-17T08:35:33ZLars QuentinEvaluate different multiprocessing architectures- [ ] threads vs multiprocessing vs asyncio
- [ ] dask
- [ ] distributed computing?- [ ] threads vs multiprocessing vs asyncio
- [ ] dask
- [ ] distributed computing?https://gitlab.gwdg.de/numerikgang/curvepy/-/issues/7Create a Linux package for the GUI2021-10-17T08:35:33ZLars QuentinCreate a Linux package for the GUIAt least `.deb`, an AUR for myself and a `nix`-package for NixOS. Plus points if we write something like a `./curvepygui.ps1` for windows and `./curvepygui.sh` for *nixAt least `.deb`, an AUR for myself and a `nix`-package for NixOS. Plus points if we write something like a `./curvepygui.ps1` for windows and `./curvepygui.sh` for *nixhttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/3Implement Notes and Examples in Docstrings2021-10-17T08:35:33ZLars QuentinImplement Notes and Examples in Docstrings- Examples are cool
- Notes can include LaTeX, which is cool for our sick algorithms
see: https://numpydoc.readthedocs.io/en/latest/format.html- Examples are cool
- Notes can include LaTeX, which is cool for our sick algorithms
see: https://numpydoc.readthedocs.io/en/latest/format.htmlhttps://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.https://gitlab.gwdg.de/numerikgang/curvepy/-/issues/19Implement Composite Bezier Curves2021-10-17T08:35:32ZLars QuentinImplement Composite Bezier CurvesAlthough the book didn't talk about the actual implementation of composite bezier curves one could argue that their base implementation is trivial enough and that by describing their existence and difficulties one could include them as a...Although the book didn't talk about the actual implementation of composite bezier curves one could argue that their base implementation is trivial enough and that by describing their existence and difficulties one could include them as a topic.
As we all know from numerical analysis a composite bezier curve is implemented as
```math
s(t) :=
\begin{cases}
\sum_{k=0}^n \beta_k^0 b_k^n(t) & t \in [0,1]\\
\sum_{k=0}^n \beta_k^1 b_k^n(t-1) & t \in [1,2]
\end{cases}
```
where $`\beta_k^i`$ describes the $`k`$-th polygon point of the $`i`$-th bezier curve.
Therefore it seems trivial to allow 2 curves of $`n-1`$ points to be composited by generating the $`\beta_n^0 = \beta_0^1`$ ourself in order to enforce the curve to be differentiable.
Or we just allow undifferentiable curves as well, which would result in not enforcing $`\beta_n^0 - \beta_{n-1}^0 = \beta_1^1 - \beta_0^1`$
TO BE DISCUSSEDhttps://gitlab.gwdg.de/numerikgang/curvepy/-/issues/14Write Unit Tests and further documentation for Chapter 42021-10-17T08:35:32ZLars QuentinWrite Unit Tests and further documentation for Chapter 4https://gitlab.gwdg.de/numerikgang/curvepy/-/issues/10Depending on its complexity, maybe create a Quickstart Guide2021-10-17T08:35:32ZLars QuentinDepending on its complexity, maybe create a Quickstart GuideOur library itself has a narrow use case. It shouldnt be needed there.
But the GUI may get more complex (If we go from visualisation to graph generation or `dask`-enabled data intensive computing) we should enable a Quickstart Guide wit...Our library itself has a narrow use case. It shouldnt be needed there.
But the GUI may get more complex (If we go from visualisation to graph generation or `dask`-enabled data intensive computing) we should enable a Quickstart Guide within the documentation