On Wed, Jan 30, 2019 at 11:08 AM Stogner, Roy H <royst...@ices.utexas.edu> wrote:
> > On Wed, 30 Jan 2019, Li Luo wrote: > > > I am using libMesh for large scale parallelization. To enable the usage > of > > 65536 processor cores, the options > > --with-dof-id-bytes=8 --with-processor-id-bytes=4 > > --with-subdomain-id-bytes=4 > > are already used for configuration. > Would you mind looking in your $LIBMESH_DIR/include/libmesh/libmesh_config.h file and verifying that #define LIBMESH_PROCESSOR_ID_BYTES 4 is indeed set? 65536 is right at the uint16_t limit, so I just want to rule out any funny business with the configure test that sets that value. Also, 4 bytes is now the default for processor_id_type so you should be able to safely omit that option if you are using a relatively recent version of libmesh. Speaking on which, can you let us know what version of libmesh you are using? A number of improvements have been made to the parallel communications routines since the last tagged release, so you'd be best off using libmesh master for any huge runs you are attempting. -- John _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
