Figure out how to best record the CMT number in the output data.

[tobeycarman]

Need a way to determine post-hoc what CMT or community type each pixel was parameterized as.

On the input side this is controlled via the input vegetation.nc file, but the user can override that with the --force-cmt command line flag.

Ideas:

• have a "run manager" that wraps the model and invoked the model thru a shell script (e.g. job.sh). Save this script with the outputs so that use can look later to see how the program was started.
  • Add a new output file (CMT.nc?) with dimensions like:

    
    netcdf cmt {
    dimensions:
    Y = 1 ;
    X = 1 ;
    variables:
    int cmt(Y, X) ;
    }

[tobeycarman]

I am leaning toward writing an output netcdf file that has the CMT number for each pixel. I think at this time it makes sense to keep it simple and not include a time dimension in this file.

Also maybe it makes sense to always enable this output file?? (Perhaps by having it enabled in the output_spec file. Or maybe it is not even controlled by the output_spec file, it is simply always "ON"?

@rarutter, any thoughts??

[rarutter]

CMTNUM was added as an output in commit d933e91b3e3243a8be4cd69b7fef2c41946c0183, but we should still consider forcing it on by default.