How to access multiple relations within one kernel? about rxmesh HOT 4 CLOSED

Sorry for the late reply. I updated to e95b38e and found the oriented V-V works well with my application. Thank you for your excellent work and help!

from rxmesh.

I have not implemented such "compound" queries where multiple queries (e.g., EF, EV, FV in your case) are needed to be computed and be resident in shared memory. But it is on my roadmap!

However, from the code snippet above, I would recommend restructuring your computation such that it would be vertex-centric instead of edge-centric. Doing so, the code would just loop over the vertex (i.e., v1's) one ring. At each step, you would have access to v2. If the query is marked as "oriented" here, you could additionally have access to the vertex before and after v2 i.e., v3 and v4. You would also need to mark the query as "oriented" in prepare_launch_box.

An example of the above suggestion can be found in the mcf_rxmesh_kernel.cuh
where p_id is the center vertex we iterate over q_id is the previous vertex in p_id's one-ring, r_id is the current one-ring vertex, and s_id is the next vertex after r_id.

Hope this is helpful! Please let me know if you have more questions.

from rxmesh.

Hi,

Thank you for your suggestion about reformulating the computation to being vertex-centric and using the V-V relation instead of E-F-V. I think it's feasible as long as using oriented=True to ensure the order of the neighborhood vertices.

However, I find that the oriented V-V query required the input mesh without boundary:

from rxmesh.

I have just pushed e95b38e a fix to allow oriented V-V (and V-E) on input mesh with boundaries (with a unit test). Please let me know if you need anything else to get your cloth simulation working :)

from rxmesh.