Results 262 comments of Cameron Smith

@Sichao25 Thank you. This was found when building with C++20?

closed with https://github.com/SCOREC/core/pull/482

For the record, @onkarsahni suggested looking at cray-mpich docs and variables controlling buffer sizes: > This seems old but check Slide/Page 10: [](http://www.archer.ac.uk/training/courses/craytools/pdf/mpi-variables.pdf)

I thought I had remembered using pre-constructed meshes for performance testing. The `read(...)` function you found looks correct and the `write(...)` function to produce the constructed mesh is also in...

@dhyan1272 @Angelyr Any thoughts?

Hi @eisungy, We typically don't run PUMI with so few elements per part (MPI rank). > I'm worried that PUMI didn't work because all meshes are duplicated and they don't...

Removing this call to `PCU_Protect(...)` https://github.com/SCOREC/core/blob/81440fa6deec1405baa7a2cd5cbcd1d82350c1bb/phasta/chef.cc#L35, which bypasses the 'pcu/reel/reel.c' signal handler, does not change the behavior.

## meeting notes 11/4/2022 - for a (partial) summary of how parallel mesh construction works see https://github.com/SCOREC/core/issues/245 - the current HEAD of `develop` has added multi-topology support via repeated calls...

## meeting notes 11/18/2022 - multi topo file format - coordinate file does not change - element file - header per block/topology: - num verts per element - num elements...