Eric Lappala (formerly with the USGS, I believe) wrote an email addressed to Eric and Vivek on 10/24/16 that has the following recommendation:
"Why does the initial saturated thickness have to be entered separately in the dataset read by the UZT routine, which according to the published input instructions posted with MT3DUSGS have to be entered again when this information is present in the link transport file? Seems to me that the UZT routine could have code added that if the saturated thickness data is present in the link transport file that it does not have to be read again. Although moisture contents above the water table are not presently written to the link transport file by Modflow NWT, it seems that it could be and then be treated the same suggested way by the UZT package."
We should be able to accommodate this request, I would think.
Eric Lappala (formerly with the USGS, I believe) wrote an email addressed to Eric and Vivek on 10/24/16 that has the following recommendation:
"Why does the initial saturated thickness have to be entered separately in the dataset read by the UZT routine, which according to the published input instructions posted with MT3DUSGS have to be entered again when this information is present in the link transport file? Seems to me that the UZT routine could have code added that if the saturated thickness data is present in the link transport file that it does not have to be read again. Although moisture contents above the water table are not presently written to the link transport file by Modflow NWT, it seems that it could be and then be treated the same suggested way by the UZT package."
We should be able to accommodate this request, I would think.