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
Many applications in PIC and MD operate on a Cartesian Domain decomposition and often employ periodic boundary conditions. Our communication structures currently do not consider a Cartesian case and are instead more general. Because of this, we may miss opportunities for optimization. In addition, it makes support for periodic boundaries difficult.
The text was updated successfully, but these errors were encountered:
Discussed this further with @streeve today - there is a clear implementation path forward in applications without this infrastructure. However, future analysis with ExaMiniMD to see if their Cartesian communication patterns and inline coordinate mapping is significantly more performant on Summit/Sierra
After some further discussion with @streeve today it seems this would be best resolved with a Cabana/Cajita merger. This would allow for combined Cartesian structure with particles in the communication plan which naturally allows for partitioning and handling periodicity.
Many applications in PIC and MD operate on a Cartesian Domain decomposition and often employ periodic boundary conditions. Our communication structures currently do not consider a Cartesian case and are instead more general. Because of this, we may miss opportunities for optimization. In addition, it makes support for periodic boundaries difficult.
The text was updated successfully, but these errors were encountered: