Combine these to a single flag: maybe PCMS_ENABLE_TRANSFER #355

Activity

1. jacobmerson commented on Aug 12, 2026

   

   jacobmerson

   on Aug 12, 2026

   Collaborator

   More actions

   We may want to have a separate flag for enabling transfer overall, but we have already relaxed some of the constraints that required both of these libraries to perform transfer.

   • Petsc is required for the transfer methods that require doing global solves (for now this is just projections).
   • The mesh intersection variants only work with Omega_h meshes.
   • The current version of the conservative transfer probably does require mesh fields for the integration, but eventually we can relax that for order 0/order one where we just use the barycentric coords from Omega_h. This is how we support evaluations without meshfields installed.

   👍React with 👍1Reacted by Fuad Hasibul Hasan
2. jacobmerson commented on Aug 14, 2026

   

   jacobmerson

   on Aug 14, 2026

   Collaborator

   More actions

   @Fuad-HH and I had a productive offline discussion. the point he was trying to get across is that most of our PCMS_ENABLE flags are dependency / PCMS developer focused. However, for the end-user, they are going to be much more interested in capability focused ENABLE flags that help them to turn on the features they want.

   For example, we could have a flag called PCMS_ENABLE_CONSERVATIVE_TRANSFER which when turned on would require that PCMS was configured with PETSC/MeshFields/Omega_h.

   I think this is probably a fairly good idea. However, it will take a fair amount of effort to figure out what the appropriate capabilities should be called and then figure out how to get CMake to handle properly.

   I am leaving this issue open for future discussion and potential coordination on how to accomplish this.