Autodesk / Autodesk/XLB

Unpredictable behaviour of warp mesh_query_point_sign_winding_number in a loop

Open
#70 3 comments 0 reactions 1 assignee Claimed by @mehdiataei View on GitHub
bug
Dominant language
Python
Stars
507
Forks
85
PR merge metrics
No merged PRs in 30d

Description

- Pull the latest code in major_refactoring branch (e.g after this [PR](https://github.com/Autodesk/XLB/commit/38431881b62c69cdf04b546107e8aaa4fcf7c7cb) )
- Put a break point in L187 of wind tunnel example [here](https://github.com/Autodesk/XLB/blob/38431881b62c69cdf04b546107e8aaa4fcf7c7cb/examples/cfd/windtunnel_3d.py#L187)
- Run in debug mode and see the computed "c_d" (the value should be virtually zero at iteration 0, it is not!).
- delete cache
- Now add this line `wp.config.max_unroll = 32` before xlb_init in the Wind tunnel example and run again in debug mode up to the same breakpoint and see the value of "c_d" (it is zero this time!)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.