Hi Lisandro, Thanks for your reply. Waiting for PETSc 3.13 and the matching petsc4py 3.13 would work just fine for me. It would be nice, however, to know what’s causing the issue.
Best, —Alejandro On 27 Mar 2020, at 18:39, Lisandro Dalcin <dalc...@gmail.com<mailto:dalc...@gmail.com>> wrote: On Fri, 27 Mar 2020 at 17:10, Matthew Knepley <knep...@gmail.com<mailto:knep...@gmail.com>> wrote: On Fri, Mar 27, 2020 at 3:31 AM Alejandro Aragon - 3ME <a.m.ara...@tudelft.nl<mailto:a.m.ara...@tudelft.nl>> wrote: Dear Matthew, Thanks for your email. I have attached the python code that reproduces the following error in my computer: I think I see the problem. There were changes in DM in order to support fields which only occupy part of the domain. Now you need to tell the DM about the fields before it builds a Section. I think in your code, you only need f = PetscContainer() f.setName("potential") dm.addField(field = f) Except that petsc4py do not expose a Container class :-( @Alejandro, PETSc 3.13 is about to be released. Once that is done, we have a small windows to make a few enhancements in petsc4py before releasing the matching petsc4py-3.13 that you can use to upgrade your code. Would that work for you? -- Lisandro Dalcin ============ Research Scientist Extreme Computing Research Center (ECRC) King Abdullah University of Science and Technology (KAUST) http://ecrc.kaust.edu.sa/<https://urldefense.proofpoint.com/v2/url?u=http-3A__ecrc.kaust.edu.sa_&d=DwMFaQ&c=XYzUhXBD2cD-CornpT4QE19xOJBbRy-TBPLK0X9U2o8&r=U1Pry6bTDByPujjSnTcPY6KNXqrym6APfmtom-lIPFA&m=HY1fXOtcfYiUbV-8yfY4iJFGJrKGJpALLyYLQbL63n0&s=U7jpaATgQWRTP15qiro-xfWS9FZ2fqFxRM_t-Zj6g5w&e=>
