tag:github.com,2008:https://github.com/jewettaij/superpose3d/releases Release notes from superpose3d 2022-03-21T06:57:20Z tag:github.com,2008:Repository/111981267/v1.4.1 2022-03-21T06:59:20Z updated setup.py <p>In the previous release, I forgot to update the version numbers in the setup.py file. This small update fixes that. (It was necessary to do that to upload the changes to pypi.)</p> jewettaij tag:github.com,2008:Repository/111981267/v1.4.0 2022-03-21T06:51:29Z scale factors (c coefficients) are hopefully correct now <p>This version fixes a bug that prevented "c" (the scale factor) from being calculated correctly. This bug was caused by a typo introduced in v1.1.0 (commit <a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/jewettaij/superpose3d/commit/91d30b831649631b9d5aa8dc75b01ee7e6eec5c2/hovercard" href="https://github.com/jewettaij/superpose3d/commit/91d30b831649631b9d5aa8dc75b01ee7e6eec5c2"><tt>91d30b8</tt></a>) when converting the for-loops into compact numpy expressions.<br> Hopefully scale factors are being calculated correctly now.</p> jewettaij tag:github.com,2008:Repository/111981267/v1.3.0 2022-02-24T09:07:28Z non-uniform weights should be working again <p>This fixes a bug which was introduced in v1.1.0.</p> <p>When we first began using numpy to speed up the matrix operations (introduced in v1.1.0), we forgot to incorporate weights in one part of the code. So the python code worked when uniform weights were used (which occurs by default). But we forgot to make sure that non-uniform weights are working.</p> <p>This code has finally been fixed, and the testing code has been updated.</p> jewettaij tag:github.com,2008:Repository/111981267/v1.2.0 2022-01-27T00:13:54Z fixed a mistake in the format of Superpose3D() return value <p>The first entry in the output of Superpose3D() is now a number instead of a rank-0 tensor. The previous behavior (rank-0 tensor) was a mistake which my automated tests failed to catch. Changing this might break backward compatibility for some users, but this new behavior is simpler and is consistent with the documentation.</p> jewettaij tag:github.com,2008:Repository/111981267/v1.1.1 2020-03-13T02:04:29Z alternative quaternion conventions <p>I added some comments explaining alternate conventions for representing rotations with quaternions. The code behavior is not effected. (Perhaps it was not necessary to draft a new release over this...)</p> jewettaij tag:github.com,2008:Repository/111981267/v1.1.0 2020-03-12T23:13:08Z significant speed improvements by replacing for-loops with numpy expressions <p>Removed all for-loops in the code to improve computational efficiency. Thanks to Alfredo Ricci Vásquez for submitting the PR containing these optimizations.</p> jewettaij tag:github.com,2008:Repository/111981267/v1.0.1 2020-02-25T02:29:07Z further hardening against nonsensical input <p>It now avoids crashing when invoked on empty arrays (length 0).</p> jewettaij tag:github.com,2008:Repository/111981267/v1.0.0 2020-02-25T01:32:21Z initial stable release <p>initial stable release. future API change extremely unlikely.</p> jewettaij tag:github.com,2008:Repository/111981267/v0.4.1 2020-02-24T23:02:32Z better error handling and unit testing <p>hardened against non-sensical user input. improved unit tests. added more silly badges.</p> jewettaij tag:github.com,2008:Repository/111981267/v0.4.0 2020-02-21T03:42:15Z quaternions available <p>Callers can supply an optional argument, q which will store the quaternion corresponding to rotation R. From it, the rotation angle and rotation axis can easily be determined.</p> jewettaij