On Fri, 3 May 2019, Renato Poli wrote:
> I see a number of error messages, as below.
> I am struggling to understand what they mean and how to move forward.
> It is related to manually setting a system solution and closing the
> "solution" vector afterwards.
> Any idea?
>
> Assertion
> `(this->comm()).verify(std::string("./include/libmesh/petsc_vector.h").size())'
> failed.
> Assertion
> `(this->comm()).verify(std::string("src/mesh/mesh_base.C").size())' failed.
> [Assertion
> `(this->comm()).verify(std::string("./include/libmesh/petsc_vector.h").size())'
> failed.
> [2] Assertion
> `(this->comm()).verify(std::string("./include/libmesh/petsc_vector.h").size())'
> failed.[0] ./include/libmesh/petsc_vector.h, line 812, compiled Feb 22 2019
> at 17:56:59
> 1] src/mesh/mesh_base.C, line 511, compiled Feb 22 2019 at 17:55:09
> ./include/libmesh/petsc_vector.h, line 812, compiled Feb 22 2019 at 17:56:59
> application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0
> application called MPI_Abort(MPI_COMM_WORLD, 1) - process 1
> application called MPI_Abort(MPI_COMM_WORLD, 1) - process 2
>
> Thanks,
> Renato
You're running in parallel, but your different processors have gotten
out of sync. At least 1 is at mesh_base.C line 511, and at least 2 or
3 are at petsc_vector.h 812. Are you not calling PetscVector::close()
on every processor, perhaps? Then the missing processor would
continue to whatever the next parallel-only operation is and the
dbg/devel mode check for synchronization would fail.
---
Roy
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users
