Erroneous Channel Length Causes Bad FTABLE, causes division by zero

[rburghol]

Another case for our edification @jdkleiner -- a custom subwatershed model fails some time during hsp2 execution. Seems to be a model computation error due to the original 60 minute timestep? I have NOT sorted it out yet, but am tracking my debugging steps here.

• Ran:
• Got errors:
  • File "/home/rob/.local/lib/python3.8/site-packages/HSP2/HYDR.py", line 122, in hydr
  • errors = _hydr_(ui, ts, COLIND, OUTDGT, rchtab, funct, Olabels, OVOLlabels) # run reaches simulation code
  • ZeroDivisionError: division by zero
• Changed input/param/river/vahydro_2022/gen_info_rseg.csv
  • From: YP3_6472_6470,3,0,S,60
  • To: YP3_6472_6470,3,0,S,15
  • Reran: /opt/model/meta_model/run_model hsp2_cbp6 $scenario YP3_6472_6470 auto river
  • Got same error.
    Changed channel length from 1.0 to 5280.0 (miles to feet) and all runs completely now.
    Originally posted by @rburghol in Alternate Time Step Segments issues in meta-model, Ex: PS3_6280_6230 #25 (comment)