Hesam Salehipour
Hesam Salehipour
Thanks for spotting this issue! You are right. We have a major refactoring coming in very soon (see branch major-refactoring) in which we have added a second backened to XLB...
Hope this issue has been resolved. Thanks @jcusick13 for your correct response.
hi @BIackthorn , is this issue fully addressed in the this PR https://github.com/Autodesk/XLB/pull/102 ?
Hi @DynoAbd786-Uni . Yes, XLB is capable of that but right now, that particualr use case is not shown in any of our examples. With our current APIs, this is...
That sounds great. Please see the contribution guidelines and submit a PR 😊.
can you create a repro please?
Added the requested changes.
If L99 - L194 in https://github.com/Autodesk/XLB/blob/38431881b62c69cdf04b546107e8aaa4fcf7c7cb/xlb/operator/boundary_masker/mesh_distance_boundary_masker.py#L100 are replaced with the following (effectively making mesh_distance_masker similar to mesh_masker), then "c_d = 0.0" is obtained without increasing `max_unroll`: ``` # evaluate if...
Even when "c_d ~ 0" is obtained, there is some weird randomness in its value everytime it is run. eg. `0.00079` vs `0.00033`