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
I don't think it will work as coded right now. It may not be worth supporting this combination anyway, but if not we should check for it and throw a helpful exception.
The text was updated successfully, but these errors were encountered:
I'm surprised that this doesn't work. Where are we breaking our orthogonality in assumptions between the PETSc interactions and Fortran kernels? I think if we are not willing to fully support the Python kernels we should remove them.
The issue was that grid.n was being used to determine loop limits. Now grid.n is the size of the whole grid, while grid.ng is the size of the processor's global vector. It is fixed.
It is quite possible that there will be features in PyClaw that we're not willing to support in PetClaw, though I would like to avoid that. PyClaw has a design goal of being used for teaching and rapid prototyping, which makes the Python kernels important.
I don't think it will work as coded right now. It may not be worth supporting this combination anyway, but if not we should check for it and throw a helpful exception.
The text was updated successfully, but these errors were encountered: