| ... | ... | @@ -124,17 +124,17 @@ raytracer done and useable". At the end of the day our raytracer should also be |
|
|
|
|
|
|
|
Nevertheless: we are always interested in contributions, questions, issues and if somebody implemented cool stuff or is interested in our stuff, we are happy to provide interfaces or code.
|
|
|
|
|
|
|
|
https://github.com/mess42/pyrate/issues/142
|
|
|
|
https://salsa.debian.org/mess42/pyrate/-/issues/142
|
|
|
|
|
|
|
|
## What about the FreeCAD interface?
|
|
|
|
|
|
|
|
The FreeCAD interface has more or less the status of a mockup and is broken since the last large refactoring in 2017. Until now there is no good idea about getting a not-so-tight coupling between FreeCAD classes and pyrate classes. Since the API is not quite settled it is really difficult to start with a full fledged FreeCAD interface without rewriting all the stuff when there is a slight API change appearing. All ideas here are appreciated. If you are interested in digging into the matter, please have a look in the `freecad/PyrateWorkbench` directory.
|
|
|
|
|
|
|
|
https://github.com/mess42/pyrate/issues/136
|
|
|
|
https://salsa.debian.org/mess42/pyrate/-/issues/136
|
|
|
|
|
|
|
|
https://github.com/mess42/pyrate/issues/134
|
|
|
|
https://salsa.debian.org/mess42/pyrate/-/issues/134
|
|
|
|
|
|
|
|
https://github.com/mess42/pyrate/issues/91
|
|
|
|
https://salsa.debian.org/mess42/pyrate/-/issues/91
|
|
|
|
|
|
|
|
## How does the optimizer work?
|
|
|
|
|
| ... | ... | @@ -142,9 +142,9 @@ The optimizer decomposes in backend and frontend whereas the backend determines |
|
|
|
|
|
|
|
There were several discussions on that in the following issues:
|
|
|
|
|
|
|
|
https://github.com/mess42/pyrate/issues/140
|
|
|
|
https://salsa.debian.org/mess42/pyrate/-/issues/140
|
|
|
|
|
|
|
|
https://github.com/mess42/pyrate/issues/137
|
|
|
|
https://salsa.debian.org/mess42/pyrate/-/issues/137
|
|
|
|
|
|
|
|
## How to create a full sphere lens?
|
|
|
|
|
| ... | ... | @@ -154,9 +154,9 @@ Since the `Conic` surface solves the ray intersection equation analytically and |
|
|
|
* use the `Asphere` type surface to avoid the quadratic analytical solution problem and use a numerical solver instead
|
|
|
|
* use a slightly deformed second surface (introduce radius deviation or slight conic const) -> this is no optimal solution when you need an exact sphere
|
|
|
|
|
|
|
|
https://github.com/mess42/pyrate/issues/149
|
|
|
|
https://salsa.debian.org/mess42/pyrate/-/issues/149
|
|
|
|
|
|
|
|
https://github.com/mess42/pyrate/issues/50
|
|
|
|
https://salsa.debian.org/mess42/pyrate/-/issues/50
|
|
|
|
|
|
|
|
|
|
|
|
|
| ... | ... | |
