You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Create Poly2D .cpp and .h files
* Adding Poly2D to core.cpp
* Add Poly2d to source CMake
* Constructor for Poly2d
* add dunder methods and read-only properties
* Including eval function
* Add read_only functions for range and azimuth orders
* Add Poly2d unit test
* Add poly2d unit test to CMakefile
* Evaluate values for each x, y positions in eval function
* Change check in x and y size in eval dunder method
* removed extra elements in vector eval and formatted
* added unit test for vector input and minor formatting
* Remove iterator in eval function
* More Pythonic __getitem__ dunder methods
* Fix bug in eval function to work with x/y arrays
* updates to poly2d vector eval
replaced std containers with eigen
now returns (m,n) array from evaluating poly2d with (m,1) and (n,1) vectors
* updates to poly1d vector eval
replaced std containers with eigen
now returns (m,n) array from evaluating poly1d from (m,n) input array
* Revert "updates to poly1d vector eval"
This reverts commit 8b760e388914a2ea304501bc8c2e5849a89783d1.
* Correct typo (comma) and remove __str__ method
* Correct missing & in __call__ method, remove __len__ method
* Move return statement in outer loop. Replace py::list with Eigen:ArrayXXd
* Replace np.ones with np.full in poly2d unit test
* Use Eigen ArrayXXd for Poly2d coefficients
* Remove __call__ dunder method
* Add coeffs property, remove __getitem__, modify constructor
* correct range/azimuth order in constructor, transpose coeffs in unit test
* address PR comments and fixes
eval operates over meshes instead of vectors
coeff property order fixed
* refactored eval vector test to eval mesh test
* added grid eval, renamed mesh eval, and added docstrings
* added unit test for grid eval and consolidated common code
* clean up
* Correct typo in Poly2d.h and add doc string to pybind implementation
* Swap x/y in eval and replace counter size_t with Eigen::Index
* Replace range/azimuth with x/y
* Correct missing +1 in return coeffs
* Change eval2d function to overrid method eval
* Modify constructor and remove __getitem__ function
* Change docstring of eval function
* Remove x_order and y_order from constructor doc string
* updated Poly2d init calls
* fix x, y order parameter init
* changed range/azimuth prefixes to x/y respectively
* changed range/azimuth prefixes to x/y respectively
* address PR comments
fixed overload eval method
made y & x args consistent with C++
changed range/azimuth prefixes to x/y respectively
* update inits, test grid/mesh with np.polynomial
* fix incorrect order
* address PR comments
fix numerous typos in comments
fix erroneous eval arg order
add coeff comparison test
clang-formatt'd pybind code
* Update Poly2d.eval() bindings for array input
Previously, Poly2d.eval() could handle input arrays of arbitrary
rank by taking input `py::array_t<double>` arguments. However, due to
the limited functionality of py::array_t, the implementation was clunky
and could have the unintended side-effect of modifying the input arrays.
This update replaces the previous Poly2d.eval() implementation with two
overloads using Eigen data structures (one for 1-D arrays, one for 2-D
arrays) in order to avoid troublesome implementation issues.
Co-authored-by: vbrancat <[email protected]>
Co-authored-by: Liang Yu <[email protected]>
Co-authored-by: Liang Yu <[email protected]>
Co-authored-by: Geoffrey M Gunter <[email protected]>
0 commit comments