Incorrect variable types in routelink file result in inconsistent model behavior

[kafitzgerald]

Expected Behavior

If variable types are important, the model should check for them and notify the user

Current Behavior

The model is failing testing because of inconsistent behavior resulting from incorrect variable types in the new routelink file

Possible Solution

Add in checks for appropriate variable types and roll back testing to old model domain for the time being

@jmccreight has offered to add in checks for this

[tjmills]

Basically the new Route_Link.nc file that Joe (I think) created is causing model testing to fail, because of some weird model behavior when there are incorrect types in the Route_Link.nc file.

James is reverting back to the old domain files for testing (and was going to add some checks in the code - to address this issue). I imagine the new files (probably were changed for a reason) will need to get fixed as well at some point. (edited)

[tjmills]

Yes, I edited the route_link for NWM to remove the errant gage that was present, and then re-saved the file. I did not pay attention to variable types because I thought that was handled by the netCDF standard. Is it not?

[rcabell]

This should be rolled up into an Input/Configuration Validation meta-issue. Tagging pending that issue being opened.