Luca Bertagna

> Oh, that's nice! Thanks. Should we be alarmed by the missing required fields? No, though we need to improve it in v1.1. The missing fields are just fields that...

Is the list in EAM containing all fields that are in pbuf, pbuf+state, or other? Also, does it contain all fields or just those to be written to out/restart file?

Well, we can print something like ``` Name Units Grid/Layout DataType Dims Goups horiz_winds m/s Phsics GLL:[COL,LEV] double [xyz,128] state, restart ... ``` Not sure if all the fields/columns (overloaded...

I am actually surprised to see that 0.0 is indeed our default value for fields. I actually thought we used NaN (or whatever is the "invalid" vallue according to `ekat::ScalarTraits`)....

We do not explicitly set an initialization value. We just create the managed view, and Kokkos handles the allocation. You should not rely on 0.0 be the value in the...

> I would recommend against using the special value of NaN for anything intentionally. I disagree. NaN can trigger FPEs, so it can be used to detect when we are...

Even if we don't explicitly init stuff to NaN, some values in the padded entries will inevitably cause FPEs (e.g., divide by 0, or sqrt of neg number), regardless of...

@mt5555 we are still hard-coding `adjust_ps=true` in Hommexx. Do we need to start making this a configurable param in hommexx?

We could modify our Jenkins script to report a fail if all tests pass and non-BFB is on. However, there are different builds, and we don't know if the nonbfb...

We cannot hack how the AT handles labels. The AT only knows the meaning of 3-4 labels (the green ones starting with AT:), the others are just random strings from...