Available diagnostics change depending on the what's in the diag_table.

[nichannah]

If I run the model with a standard diag_table, then create a new diag_table based on available_diagnostics after that run, then run the model again, the available diagnostics will be different.

This available diagnostics should be a function of the model configuration, not the diagnostics themselves.

[Hallberg-NOAA]

The available diagnostics file also
  indicates which diagnostics are being used, hence it must be a
  function of the diagnostics themselves.

    - Bob Hallberg

  On 04/28/2015 05:15 PM, Nic Hannah wrote:


  If I run the model with a standard diag_table, then create a
    new diag_table based on available_diagnostics after that run,
    then run the model again, the available diagnostics will be
    different. 
  This available diagnostics should be a function of the model
    configuration, not the diagnostics themselves. 
  —
    Reply to this email directly or view
      it on GitHub.

[nichannah]

OK, my issue description is wrong! The available_diagnostics file was changing but this was actually because of I/O buffering. available_diagnostics was not being closed when the model finished so the contents was variable. Just bad luck that it changed when the diag_table changed! I'll fix this and close the issue as part of #147.