Kenneth E. Jansen

Jed said: > Regarding BCs, `GridLocation_t` can take the value `FaceCenter`, so this is just a naming thing (preferring to call it `PointList` with `FaceCenter` instead of `ElementList`). Notable that...

Jed said (much more) > As I look at the [documentation](https://cgns.github.io/CGNS_docs_current/sids/gridflow.html#Elements), it shows ElementType_t between ElementRange and ElementConnectivity. Does cgnsview just not show this or, it it promoting that to...

Thanks @jedbrown this is much more clear now. Thanks also to @jrwrigh who explained quite a bit of this to me when we met on Tuesday to discuss this. As...

DEVELOPMENT ROADMAP 1. Fix SCOREC-core’s CGNS writer to output CGNS data structures that have boundary element connectivity with the same node numbering used on the interior. The current SCOREC-core capability...

>Life will be easiest if those face elements are oriented the same way on the periodic and donor surfaces. I see three issues here to clarify completely what `oriented the...

> On the last point, it will be possible to read any cgns checkpoint as mesh and initial condition. If the number of ranks matches, we can continue with the...

After meeting with @cwsmith and @jrwrigh this morning, and then thinking a bit about it during my bike ride in to campus it occurs to me that we do have...

@jedbrown thanks for the links to how PETSc sets up these files and writes data. For now I have abandoned the clunky idea of making a post-chef converter from posix...

I think I have all the data in flat 1-D arrays for coordinates, volume connectivity, and boundary element connectivity to be chucked into a CGNS file in a parallel way....

As I start to add the calls to CGNS to write the CGNS file, I am noticing some places to easily get confused: 1. chef was already preparing for PHASTA...