[esp-r] Re: Failed Simulations in tester

[Jon Hand]

The issue is the --extra-debug argument - this ensures that the esp-r module will crash
with additional information when it detects numerical errors.  And some of the tester
models generate numerical faults with that compiler flag.  For use with tester
you should issue a 'make clean'  and then just use the --debug option when installing.

The SL5_test not found does happen sometimes.

Recently I have been moving away from running tester.pl with the --create_historical_archive option
My approach is to compile a fresh development_branch to /usr/esru (place sensitive is tester) and
my test branch somewhere else.  I then ask tester to run both the standard and test version:

./tester.pl -v --no_h3k /usr/esru/esp-r/bin/bps /home/jon/esru_test/esp-r/bin/bps --ref_loc /usr/esru/esp-r/bin --test_loc /home/jon/esru_test/esp-r/bin

The -v lets me see what is happening.  It generates a file bps_test_report.txt

Also, tester can be a bit more robust on 32bit Linux platform than 64bit.


Regards, Jon Hand

________________________________________
From: esp-r-bounces at lists.strath.ac.uk [esp-r-bounces at lists.strath.ac.uk] On Behalf Of Adam Wills [adamwills at cmail.carleton.ca]
Sent: 23 May 2013 21:16
To: esp-r at lists.strath.ac.uk
Subject: [esp-r]  Failed Simulations in tester

Hello Everyone,

I have been attempting to run the tester scripts for some time now. When I try to create a results archive with tester using a clean version of development_branch, I have a few test cases which crash. I will provide details for how I compiled the branch, ran tester, and the problems I have encountered.

I checked out development_branch @r9232 and launched Cygwin on my Windows XP machine. I compiled ESP-r using the following command:

./Install -d /usr/esru/development_branch/ --xml --no_training --extra-debug --silent

Out of habit, I have been using the --extra-debug switch. Once ESP-r compiled, I navigated to tester/scripts and issued the following command:

./tester.pl -v --databases /usr/esru/development_branch/esp-r /usr/esru/development_branch/esp-r/bin/bps --ref_loc /usr/esru/development_branch/esp-r/bin/ --test_loc /usr/esru/development_branch/esp-r/bin/ --create_historical_archive ESRU_dev_cyg.tar.gz

Tester runs to completion with most test cases running without issue. However, I get the following errors:

ls: cannot access /home/Adam/development_branch/tester/scripts/ESRU_dev_cyg/Annex42_fuel_cell/SOFC_constant/*SL5_test.*: No such file or directory
ls: cannot access /home/Adam/development_branch/tester/scripts/ESRU_dev_cyg/bld_hc_ISO15099/HC/*SL5_test.*: No such file or directory
ls: cannot access /home/Adam/development_branch/tester/scripts/ESRU_dev_cyg/bld_hc_ISO15099/HC_no-ISO/*SL5_test.*: No such file or directory
ls: cannot access /home/Adam/development_branch/tester/scripts/ESRU_dev_cyg/Lion_battery/Lion_battery/*SL5_test.*: No such file or directory
ls: cannot access /home/Adam/development_branch/tester/scripts/ESRU_dev_cyg/plt_lookup_table/elec-follow/*SL5_test.*: No such file or directory
ls: cannot access /home/Adam/development_branch/tester/scripts/ESRU_dev_cyg/NCHE_complete/NCHE_complete/*SL5_test.*: No such file or directory
ls: cannot access /home/Adam/development_branch/tester/scripts/ESRU_dev_cyg/NCHE_complete_noNCHE/NCHE_complete/*SL5_test.*: No such file or directory
ls: cannot access /home/Adam/development_branch/tester/scripts/ESRU_dev_cyg/plt_pre_A42_PEMFC_model/ccht/*SL5_test.*: No such file or directory
ls: cannot access /home/Adam/development_branch/tester/scripts/ESRU_dev_cyg/plt_SDHW/system2_strat_tank/*SL5_test.*: No such file or directory
ls: cannot access /home/Adam/development_branch/tester/scripts/ESRU_dev_cyg/plt_SDHW/system3_water/*SL5_test.*: No such file or directory
ls: cannot access /home/Adam/development_branch/tester/scripts/ESRU_dev_cyg/plt_SDHW/system4_50_per_cent_glycol/*SL5_test.*: No such file or directory
ls: cannot access /home/Adam/development_branch/tester/scripts/ESRU_dev_cyg/plt_SDHW/system4_water/*SL5_test.*: No such file or directory
ls: cannot access /home/Adam/development_branch/tester/scripts/ESRU_dev_cyg/plt_zone_heat_gain_coupling/plt_multizone_construction_gain_test/*SL5_test.*: No such file or directory
ls: cannot access /home/Adam/development_branch/tester/scripts/ESRU_dev_cyg/plt_zone_heat_gain_coupling/plt_multizone_nogain_test/*SL5_test.*: No such file or directory
ls: cannot access /home/Adam/development_branch/tester/scripts/ESRU_dev_cyg/plt_zone_heat_gain_coupling/plt_multizone_surface_gain_test/*SL5_test.*: No such file or directory
ls: cannot access /home/Adam/development_branch/tester/scripts/ESRU_dev_cyg/plt_zone_heat_gain_coupling/plt_multizone_zone_gain_test/*SL5_test.*: No such file or directory
ls: cannot access /home/Adam/development_branch/tester/scripts/ESRU_dev_cyg/window_control/bld_simple/*SL5_test.*: No such file or directory

Depending on the test case, the errors were either floating point exceptions or segmentation errors.

I am curious if anyone else in the community has encountered these issues or can duplicate what I have been observing. Perhaps I am just running tester incorrectly. I'm going to run tester on my Ubuntu version next.

Cheers,

--
Adam Wills
M.A.Sc.
Sustainable Building Energy Systems Laboratory
Solar Energy Systems Laboratory
Department of Mechanical & Aerospace Engineering
Carleton University
Ottawa, Canada
adamwills at cmail.carleton.ca<mailto:adamwills at cmail.carleton.ca>