Solution

1. Goal is to improve performance of "brute force" search with parallel computing. ✔️
2. The approach should be very similar to implemented with using of TRunner instance and is used inside loop. ✔️
3. PointCloud should be attribute of "handler", because now different instances of handler should work with different data (rotated by different angles). ✔️
4. TRunnerPool class should be designed maintaining pool of instances of TRunner class and having GetRunner method, which should wait until one of runners will be free. ✔️
5. Initial angles of rotation are stored as attributes of TPointCloud because they are just extra attributes of the same entity (no needs to create additional container). ✔️

Related

#3

Solution

Rename TDownhillSimplexContainer to TDownhillSimplexServer. ✔️

Related

https://action.mindjet.com/task/14790421

Solution

1. Correct text to be more compact and descriptive. ✔️
2. Correct style to move footer down. ✔️

References

https://help.github.com/en/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll
https://www.toptal.com/sass/theming-scss-tutorial
https://github.com/pages-themes/dinky

Solution

1. Minimum bounding box in 3D. ✔️
2. Copy it to the branch 0.9.24 as well. ✔️
3. Move it into separate folder. ✔️
4. Add description to the page. ✔️
5. Format code. ✔️
6. Move interface implementation into separate file. ✔️ #11
7. Rebuild and test Fit. ✔️
8. Add multi-threading example. ✔️
9. "Handlers" should be freed after finishing computation. ✔️

References

https://en.wikipedia.org/wiki/Minimum_bounding_box_algorithms

Related

#11 #15 #31 #38 #43 #48

Solution

TOptimizingApp - the container class (not abstract).
TBoundingBoxServer implements application specific logic.

Related

#3

Related

#11 #3

Components are the same by module but occupy different places.

Conclusion

Not an issue.
Rotation angles can be different if object has axis of symmetry.
More correct criteria is the direction of rotated unit vector. It is seen from optimization on TestModel.obj that final and initial directions are very close. This happens because test object is aligned along X-axis and minimum box volume is achieved with this orientation. This could not be the case with general object.

Related

dvmorozov/fitgrids#6
Counters are here.

Solution

1. Use https://www.mozilla.org/en-US/MPL/2.0/.
2. Review and update sources for both branches.

Solution

1. Make them informative and suitable for automatically generated documentation.
2. Check comments in LorentzPoint.

LCL creates a few processing threads under Linux even for simplest application. This somehow causes failure when event handler creates separate thread and leaves it running. Under Windows only single thread is created and the issue is not reproduced. The issue is not reproduced when event handler waits for termination of all created threads. As a workaround TRunner.Wait is called. Otherwise probably architecture should be changed.

References

https://wiki.freepascal.org/Multithreaded_Application_Tutorial
http://lazarus-dev.blogspot.com/2013/08/threads-with-lazarus.html

Related

#31

Review and update module headers.

Related

#3

References

https://delphi.fandom.com/wiki/Creating_Components
https://edn.embarcadero.com/article/20569

1. Package.
2. Demo application.

Related

#3

Related

#3

Related

#3

Solution

Minimal point should not be one of vertexes of the simplex.

Solution

1. Exclude functionality specific for Windows by compilation keys. ✔️
2. Create Linux-specific replacement. ✔️
3. Update version for Lazarus 0.9.24. ❌ TRunnerPool is not supported under this version.
4. Update pages. ✔️

References

https://wiki.lazarus.freepascal.org/RunError (RunError(232))
https://gist.github.com/Xor-el/aeb711157551d0b071e474fc4a7e9360 (CPU count)

Related

#3 #15

#3

1. Check forms. ✔️
2. Check building package. ✔️
3. Check Lazarus build under Windows. ✔️

References

http://docwiki.embarcadero.com/Libraries/Rio/en/DesignIntf

Related

#3 #31