an "operations" field

[roblatham00]

Instead of implying bulk transfers based on size, make the kind of
operation we are doing explicit

[carns]

Looks good overall, just put in a couple of suggestions to resolve.

[roblatham00]

coming back to this after some distractions. thanks for the suggestions. I tried with a bunch of the built-in json configs

[carns]

Something is still weird. I haven't checked the code yet, but I still don't see the operation field getting set in the json:

carns-x1-7g ~/w/s/m/m/build (dev-operations=)> mpiexec -n 4 src/quintain-benchmark -g quintain.ssg -j ../tests/quintain-benchmark-example.json -o foo
# SSG group refreshed; proceeding with benchmark.
carns-x1-7g ~/w/s/m/m/build (dev-operations=)> zcat foo.gz |grep operation
carns-x1-7g ~/w/s/m/m/build (dev-operations=) [0|1]>  

That particular json has defaults for everything (except for setting one mercury parameter, see below), but the benchmark should fill in the default value to show what was used in the run.

{
    "margo": {
        "mercury": {
            "auto_sm":true
        }
    }
}