Cameron Smith
Cameron Smith
> This issue has always puzzled me. Is SCOREC/core designed to function properly when parts get emptied? No. Most functionality in core that uses APF will not handle empty parts....
Is support for writing frozen fields needed?
How about manually creating an array for each field and leaving the pumi fields un-frozen? If the mesh and field are static then it sounds like this could work.
> I will have to copy the data from the array to the tag field every time I want to write to disk I'm a bit confused about the purpose...
There is another catch here; before mesh data arrays are written to `.smb` they must be 'compacted' via reordering if there were topological (i.e., mesh adapt) or distribution changes (i.e.,...
Hello Andy, What you described can be done with PUMI. I'm pasting some points from the emails 'for the record'; the questions are good ones and may be helpful to...
Ahhh - good catch. Sorry for missing that limitation of `construct(..)`. We should be able to modify the current version to work with multiple entity types by extending the arguments...
The `pumi_` functions are a lightweight wrapper around the APF (mesh and fields) and GMI (geometric model) libraries and provide a more consistent/unified set of APIs; most of the interface...
@a-jp Did you work out the construction of the pumi instance?
@seegyoung we have the construct API for constructing parallel meshes from node and element data: https://github.com/SCOREC/core/issues/245#issuecomment-526165443 I believe this is what @a-jp is doing for his larger/real meshes.