Common Errors

[rburghol]

Note: the cbp model (and the meta_model) framework use the presence of a file named "problem" to indicate that an error has occured at some step in the process. This works well to pass messages amongst separate scripts, however, under some circumstances, like when you are using a predefined TEMP directory for testing, a routine may not delete an old "problem" file before running, so the old problem file fools the routine into thinking something bad happened, when in fact, the problem may have been fixed.

Other "real" errors:

• Missing the MET and PRAD wdms (need to regenerate):

  land segment:  N51540  did not run for land use:  aop
  rerun lug in non-quite mode
  input file  aopN51540.uci
  check the file ../../tmp/rob-scratch/rob-121-0043/aopN51540.ech

[rburghol]

• Trying to run river after land completes ok with a new scenario.
• only difference between this and the base scenario () which runs OK is that this scen had different DIVERSIONS in the config/control/river/ .con file.
  • Also had some different years, and a different met input (met input should be good to go)

Error

 All Res Passthru Effs are 1 ... nothing to do ...
 calscen = CFBASE30Y20180615_Y2020
 TOTNvadeq_2021CFBASE30Y20180615_Y2020
  getscenmod

 PROBLEM FILE WRITTEN

could not open file
../../../output/river/scenario_compare/vadeq_2021/JL1_6770_6850.
 error =            2

Fix: CALIBSCEN in Phase 6

• CALIBSCENshould be set to the new scenario name, otherwise you will receive an error: could not open file../../../output/river/scenario_compare/p6ss/YP3_6472_6471.csv`
  • So, for example, if I clone a phase6 scenario subsheds to drought, I need to make the following changes to config/control/river/drought.con:

    CALIBSCEN
    subsheds
    END CALIBSCEN

    to

    CALIBSCEN
    drought
    END CALIBSCEN

    see also https://github.com/HARPgroup/HARParchive/issues/288

[rburghol]

Tried:

• set RUN_ANNLOAD = 1
• set RUN_AVGLOAD = 1
• Error running the full James basin tn value outside the range and it is a NaN. Maybe a problem with just running hydro?

 PROBLEM FILE WRITTEN

tn value outside the range of the table
 tn=               NaN
expand the table

srun: Step created for job 178

Tried:

• set RUN_ANNLOAD = 0
• set RUN_AVGLOAD = 1
• Still failed.

Try:

• set RUN_ANNLOAD = 1
• set RUN_AVGLOAD = 0
• Got a different error: problem in transport factor program model run is earlier than allowed, change 'y1' in file

  
  PROBLEM FILE WRITTEN

problem in transport factor program model run is earlier than allowed, change 'y1' in file pp/src/postproc/del/tfs/tfs.inc

- This has y1=1980, y2=2100, don't know why tyhis causes an error.  Speculate that something in a wdm default time series is earlier and that causes this?
- Try 
- `set RUN_ANNLOAD        = 0`
- `set RUN_AVGLOAD        = 0`
- Recall earluier Gopal said we DID need at least one of these, but perhaps that is only when running the land segments, and when running the river we can omit?

[rburghol]

Realized that we were running pqual etc in the land and river config, but should only be running water. Tried disabling the river quality models and just rerunning ETM and river (disabled land too but didn't rerun)

• set RUN_ANNLOAD = 0
• set RUN_AVGLOAD = 0

 PROBLEM FILE WRITTEN

EOR load can not be zero
stb JL3_7090_7150 N51125 sed
   0.0000000000000000        6.6079224973203399E-006

[rburghol]

ERROR:  the wdm file
../../../tmp/wdm/river/hsp2_2022/stream/JL1_7080_7190.wdm
 Had zero flow for the first month

• flow WDM goofedup. Maybe empty precip or upstream flow simulation did not complete OR data from another model, like hsp2 did not populate the WDM with valid flows after the last model step completed.

[rburghol]

Ran: /opt/model/meta_model/run_model cbp_hsp2 hsp2_2022 JL1_7080_7190 /opt/model/p6/vadeq/tmp/rob-scratch/h2_test river run 11_scour_org Error:

ERROR:  the wdm file
../../../tmp/wdm/river/hsp2_2022/stream/JL1_7080_7190.wdm
 Had zero flow for the first month

• but the wdm DOES have flow in the first month. Maybe the problem file from the previous still exists?
• Try deleting it. Boom!!! It works!
• Note: sometimes, an old problem file makes you think you still have a problem.