Skip to content

CRHM_GUI fix version for Issue_432: running crash and bug #452

@loganxingfang

Description

@loganxingfang

I used the fix version for Issue 432https://github.com/srlabUsask/crhmcode/issues/432 and ran a few prj files. I had some crashes and bugs to report.

  1. I ran a Marmot Creek project file, the .prj and obs files are here
    Marmot.zip

When I tried to open the prj file, the CRHM_GUI crashed.

  1. I ran a researcher Di's project files,
    the prj files are here
    20072008_test_prj_files.zip

the obs files are here
20072008_test_obs_files.zip

There two simulation runs:

run 1: S4_group150_generate_init20080101_REW_CRHM134_LFedit1.prj from 2007 1 1 to 2008 1 1, to generate int file used by run 2

run 2: S4_group150_used20080101_init20090101_REW_CRHM134_LFedit1.prj from 2008 1 1 to 2009 1 1, to use int file generated from run 1 and also to generate next int file

These runs finished and were able to generate output and int files. The only issue is the datetime stamp on x-axis in the graphic interface, these look like MS-data number not proper human readable datetime,
see attached screen shots for these two runs
CRHM_GUI_20072008_run_LF_PM
CRHM_GUI_20082009_run_LF_PM

  1. I ran a researcher Di's project files, this is a longer time simulation, 5 years: S4_group150_resetparam_generate_init20120101_test_LFedit1.prj for 2007 to 2012

the prj file is here
S4_group150_resetparam_generate_init20120101_test_LFedit1.zip

the obs files are here
OBS_2007_20190101_RH.zip
OBS_2007_20190101_temp_wind.zip
OBS_2007_20190101_prec_Srad.zip

CRHM_GUI crashed at 2011-10-24T18:00. I attached the output file
CRHM_20072012_crash_output_1.zip

Not sure why it crashed. Too many forcing variables from obs files or the large value of variables WS_flow@EU(1) WS_flow_s@EU(1) in output file:
2011-10-24T18:00 3.051169E+258 2.825157E+254

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions