CHRTOUT results

[Irene G]

Hi,

Could you please let me know if the following I/O volume control makes sense when working with CHRTOUT results? I would like to know what is missing when computing the streamflow for a feature_id? When I looked at the results, it seems something is missing the following equation since adding up the left-hand side terms does not yield to the streamflow. Are there other contributing terms to the streamflow magnitude from other results (e.g. LDASOUT)?

For the feature_id=i

q_lateral(i)+qSfclateralRunoff(i)+q_Bucket(i) =! streamflow(i)

In addition, in the NWM configuration run, which Area do you recommend to use to convert the streamflow to depth? I mean should I use the area of the domain (dx.dy) or the summation of areas of the NHDPlus catchments since the routing is done for each NHDPlus reach segments?

Thanks,

Irene

[Molly]

Hi Irene,

I asked Laura Read on our team and here is her response:

"

In NWM channel routing, we are using Muskingum Cunge, which calcuates streamflow based on upstream and downstream components (previous and current) to update the states.  Here's an example for calculating the downstream current (qdc): 

qdc = 

      = qdp + qup + q_lateral =

      = qdp + qup + qSfcLatRunoff + qBucket = 

      = qdp + qup + qSubsurface + qOverland + qBucket

where qdp = q, downstream previous and qup = q, upstream previous.  Let me know if there are other questions about these components, but they should be referenced in the technical guide.

For the 2nd question, I recommend using the NHD+catchment areas for determining the contributing area to each reach.  "

I hope this is helpful.

Best regards,

Molly