Grid validity check

[sballin]

Hello, I want to help add a feature to automatically check the grid validity at the end and graphically flag any cells with problems. The shapely library makes it easy to check that cells are not twisted (polygon.is_valid) and that they touch but don't overlap their neighbors (polygon1.touches(polygon2)). I've added the is_valid check, but the overlap check is more subtle because the poloidal indices jump at target plates and X-points. Since I am not very familiar with the codebase yet, is there a simple way, compatible across the different topologies, to get the indices of the physically adjacent cells?

[trognlien]

Sean, UEDGE has two arrays that identify the poloidal index to the right and left of a given cell (ix,iy). These are bbb.ixp1(ix,iy) #gives the poloidal index of the cell to the “right” (clockwise) of the the cell (ix,iy) bbb.ixm1(ix,iy) #gives the poloidal index of the cell to the “left” -Tom

…

------ Thomas D. Rognlien Email: ***@***.******@***.***> L-440 (B3725, R432) Tel: 925-422-9830 LLNL, 7000 East Ave, P.O. Box 808 Admin support: 925-422-7446 Livermore, CA 94551 From: Sean Ballinger ***@***.***> Reply-To: LLNL/INGRID ***@***.***> Date: Monday, April 19, 2021 at 9:37 AM To: LLNL/INGRID ***@***.***> Cc: Subscribed ***@***.***> Subject: [LLNL/INGRID] Grid validity check (#9) Hello, I want to help add a feature to automatically check the grid validity at the end and graphically flag any cells with problems. The shapely library makes it easy to check that cells are not twisted (polygon.is_valid) and that they touch but don't overlap their neighbors (polygon1.touches(polygon2)). I've added the is_valid check, but the overlap check is more subtle because the poloidal indices jump at target plates and X-points. Since I am not very familiar with the codebase yet, is there a simple way, compatible across the different topologies, to get the indices of the physically adjacent cells? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<https://urldefense.us/v3/__https:/github.com/LLNL/INGRID/issues/9__;!!G2kpM7uM-TzIFchu!kf5GDHMGR4BpDAtH1dFcUR1LM3u3Ts4TQa6KL2E72UUDNk8jUSPJHNQLpsatznXlYA$>, or unsubscribe<https://urldefense.us/v3/__https:/github.com/notifications/unsubscribe-auth/AAILAYQXMCD5E7O2RVR4723TJRL2PANCNFSM43GF6YAA__;!!G2kpM7uM-TzIFchu!kf5GDHMGR4BpDAtH1dFcUR1LM3u3Ts4TQa6KL2E72UUDNk8jUSPJHNQLpsbZn3buYA$>.

[bryan-garcia]

Hi Sean,

Yes, there is a simple way to access cells. All cells are stored as a 2D list within each patch under attribute cell_grid regardless of topology.

For example, from an INGRID object that has already made a call to CreateSubgrid, you can access cell (ix, iy) from say Patch A2 with:

ig_obj.CurrentTopology.patches['A2'].cell_grid[ix][iy]

• Bryan