In the newest version, it is no longer necessary to hand-edit the
constants in "recvTask.c" and "readtile_mpiio.c".  Instead, the file
"SIZE.h" has been modified in two ways:
  (1) SIZE.h  now includes the constant "sFacet"
  (2) SIZE.h  may now be #include in both C and Fortran files
This means that "recvTask.c" and "readtile_mpiio.c" now get the
information they need directly from "SIZE.h", so the magic constants
for the run only need to be edited in one place (namely, SIZE.h).


One tile per rank is recommended, mostly for pickup input performance,
but it is not strictly necessary.

Choose dumpFreq and pChkptFreq as usual. We're not set up
to do the rolling checkpoints yet. It'll dump u,v,t, and etan now -
send me a list of other fields you want, as it is rather involved
to change them. But this should be enough to see if it works.


>>>>>>>>>>>>>>>>>>>>>>>>>>>>
From Bron, February 28, 2019

To use, set run-time parameter: useSingleCPUio=.FALSE.

Only a couple of files are different from the sources I copied from you.
But note in particular that  "SIZE.h"  is a new file in that directory,
and "recvTask.c" has a huge number of changes.


A couple of notes:

The input scheme implemented here is only invoked on
the 64bit pickup files.  It is specific to the LLC decomposition and will
not work on e.g. the Monterey high-res simulations we did a couple years
ago.  (Although, the code should work for any facet size as specified
in SIZE.h)  The format of SIZE.h was changed so that it can be included
in both C and Fortran files, and I also added the "sFacet" constant that
specifies the base facet size (e.g. 1080).  So SIZE.h will probably look
kinda weird at first, but shouldn't be hard to figure out.  The major
advantage is that now you no longer need to edit any magic constants in
recvTask.c and readtile_mpiio.c - they now derive the info they need by
directly including SIZE.h

The code now automatically figures out how many ranks are running per node.
You can run with whatever number of ranks per node that you want, but the
number needs to be consistent for all nodes (except possibly the last node,
which can be short).

The initial burst of output generated by recvTask.c (the "map" describing
the way the I/O processes are allocated) is now somewhat longer and more
detailed, but can continue to be ignored.

I did NOT try to cure the "integer" problem.  It seems that the code is
getting fairly close to bumping into the 2G (i.e. 2^31) limit on numbers
that fit into a default integer.  I *think* you can probably do one more
doubling of the resolution (to 8640), but I'm also pretty sure that going
past that will break the code.