Clarification Regarding Use of "Q_OUT" Values for T-Route Input

[johnsunghun]

Hello.
I hope this message finds you well. I have a question regarding the configuration of input files for T-Route in the ngen-routing-template.yaml file. It specifies that the input files for T-Route are located in the ./outputs/ngen/ directory, using the "nex-*" format.
In this context, I would like to confirm if the Q_OUT values for each nexus point, as set in the ngen-realization-template.json file, are the ones being utilized by T-Route. Additionally, I am curious whether these Q_OUT values represent the lateral flow at each nexus point.
I appreciate your time and clarification on this matter. Please let me know if further details are needed from my side.

[JoshCu]

Hello! 👋

You're correct.
t-route looks for input files that are generated by next gen. Those files are one file per nexus timeseries csv files that contain Q_OUT as the lateral flow at each timestep for that nexus in cubic meters per second.

Here's a sample from one of those nexus csv files. They're headerless and should be index(timestep), date time, Q_OUT in m³/s

josh@desktop:/mnt/raid/ngiab/example_data$ head outputs/ngen/nex-488322.csv
0, 2010-01-01 00:00:00, 0.122452
1, 2010-01-01 01:00:00, 0.122446
2, 2010-01-01 02:00:00, 0.122439
3, 2010-01-01 03:00:00, 0.122432
4, 2010-01-01 04:00:00, 0.122425
5, 2010-01-01 05:00:00, 0.122418
6, 2010-01-01 06:00:00, 0.122411
7, 2010-01-01 07:00:00, 0.122404
8, 2010-01-01 08:00:00, 0.122397
9, 2010-01-01 09:00:00, 0.12239

[johnsunghun]

Got it. Thanks for letting me know. Have a great day!

…

________________________________ From: Josh Cunningham ***@***.***> Sent: Tuesday, October 29, 2024 6:34 PM To: CIROH-UA/NGIAB_data_preprocess ***@***.***> Cc: Kim, Sunghun ***@***.***>; Author ***@***.***> Subject: Re: [CIROH-UA/NGIAB_data_preprocess] Clarification Regarding Use of "Q_OUT" Values for T-Route Input (Discussion #51) WARNING: This message has originated from an External Source. This may be a phishing expedition that can result in unauthorized access to our IT System. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email. Hello! 👋 You're correct. t-route looks for input files that are generated by next gen. Those files are one file per nexus timeseries csv files that contain Q_OUT as the lateral flow at each timestep for that nexus in cubic meters per second. Here's a sample from one of those nexus csv files. They're headerless and should be index(timestep), date time, Q_OUT in m3/s ***@***.***:/mnt/raid/ngiab/example_data$ head outputs/ngen/nex-488322.csv 0, 2010-01-01 00:00:00, 0.122452 1, 2010-01-01 01:00:00, 0.122446 2, 2010-01-01 02:00:00, 0.122439 3, 2010-01-01 03:00:00, 0.122432 4, 2010-01-01 04:00:00, 0.122425 5, 2010-01-01 05:00:00, 0.122418 6, 2010-01-01 06:00:00, 0.122411 7, 2010-01-01 07:00:00, 0.122404 8, 2010-01-01 08:00:00, 0.122397 9, 2010-01-01 09:00:00, 0.12239 — Reply to this email directly, view it on GitHub<#51 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BGZYNPIOGEVBP5MBELEAA5LZ6ALPNAVCNFSM6AAAAABQ2TGCU6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMBZGM2TSOI>. You are receiving this because you authored the thread.Message ID: ***@***.***>