CV test failing - Json::LogicError

oloapinivad commented 5 years ago

Hi @h-dh sorry to re-open issue #11, but I am now using the Github version with the most recent commit.

Unfortunately I still get the same error as before:

NEXT File: clt_3hr_EC-Earth3_historical_r4i1p1f1_gr_185001010130-185012312230.nc terminate called after throwing an instance of 'Json::LogicError'
  what():  in Json::Value::operator[](ArrayIndex)const: requires arrayValue
/home/ms/it/ccpd/perm/ecearth3/qa-dkrz/scripts/qa-exec-check: line 2052: 87696 Aborted                ${cmd} > out_${name}.txt

Here below the current configuration:

APPLY_MAXIMUM_DATE_RANGE=t
ARITHMETIC_MEAN=t
CF=1.7
CF_AREA_TYPES=cf-area-type-table.txt
CF_CHECK_LIST=/home/ms/it/ccpd/.qa-dkrz/QA_TABLES/tables/projects/CF/CF_check-list.conf
CF_FOLLOW_RECOMMENDATIONS=t
CF_STANDARD_NAMES=cf-standard-name-table.xml
CF_STD_REGION_NAMES=cf-standardized-region-list.txt
CHECK_MODE=CV
CONFIG_FILE=/home/ms/it/ccpd/.qa-dkrz/config.txt
CT_PATH_INDEX=2,3,6,8
DEFAULT_VALID_MAX=1E+17
DEFAULT_VALID_MIN=-1E-15
DRS_PATH_BASE=CMIP6
EXCLUDE_ATTRIBUTE=comment,contact,history,references,title
FILE_NAME_SEP=_
FILE_NAME_VAR_INDEX=0
FREQ_INDEX_PATH=5
HARD_SLEEP_PERIOD=10
IGNORE_REF_DATE_ACROSS_EXP=t
IGNORE_REFERENCE_DATE=t
LOG_FILE_INDEX=2,1,3
LOG_FNAME_DIR=/lus/snx11062/scratch/ms/it/ccpd/tmp_cmor/QA/chis/results/check_logs
LOG_PATH_INDEX=2,3,4,5
MAIL=mailx
NEVER_BREAK_SESSION=t
NUM_EXEC_THREADS=1
PATH_SEP=/
PROJECT=CMIP6
PROJECT_DATA=/lus/snx11062/scratch/ms/it/ccpd/tmp_cmor/QA/chis/linkdata
PROJECT_TABLE_PREFIX=pt
QA_BIN=/home/ms/it/ccpd/perm/ecearth3/qa-dkrz/bin
QA_CHECK_LIST=CMIP6_check-list.conf
QA_CONF=/home/ms/it/ccpd/.qa-dkrz/QA_TABLES/tables/projects/CMIP6/CMIP6_qa.conf
QA_EXEC_HOSTS=cca-login4
QA_HOST=cca-login4
QA_RESULTS=/lus/snx11062/scratch/ms/it/ccpd/tmp_cmor/QA/chis/results
QA_SRC=/home/ms/it/ccpd/perm/ecearth3/qa-dkrz
QA_TABLES=/home/ms/it/ccpd/.qa-dkrz/QA_TABLES
QUERY_EMPTY_DIR=t
QUERY_EMPTY_FILE=t
QUERY_NON_NC_FILE=t
QUERY_ONLY_NC=t
REATTEMPT_LIMIT=5
RESUME_SESSION=f
RUN_PREPARE=t
SELECT=CMIP6/CMIP/EC-Earth-Consortium/EC-EARTH-AOGCM/historical/r4i1p1f1
SESSION=2019-06-28_09:17:03
SESSION_LOGDIR=/lus/snx11062/scratch/ms/it/ccpd/tmp_cmor/QA/chis/results/session_logs/2019-06-28_09:17:03
SHOW_CONF=t
SLEEP_PERIOD=300
TABLE_DRS_CV=CMIP6_DRS_CV.csv
TABLE_EXPERIMENT=CMIP6_experiment_table.txt
TABLE_PATH=/lus/snx11062/scratch/ms/it/ccpd/tmp_cmor/QA/chis/results/tables
TABLE_TIME_SCHEDULE=CMIP6_time_table.csv
TABLE_VAR_REQ=CMIP6_MIP_tables
TASK=CMIP6_qa.conf

oloapinivad commented 5 years ago

Here is the also the complete logfile. EC-Earth-Consortium_EC-Earth3_historical_r4i1p1f1.log

Please let me know if there is anything else that could help you in the debugging...

h-dh commented 5 years ago

Did you set the configuration option CHECK_MODE yourself? If yes, the text below should give an explanation (I hope you did, because otherwise I don't have any explanation).

In the year 2017, it was agreed that CMIP6-CV is to be checked by the CMOR-PrePARE tool. Then, the development of anyCMIP6-CV checks by the QA-DKRZ tool was stopped (without solving a conflict actually occurred at the time). The default of the QA-DKRZ option CHECK_MODE was set to 'DRS,CF,TIME', which is still checked by QA_DKRZ. If a user changes CHECK_MODE by setting a different one including 'CV', then the incomplete ciding gets in effect again. From now on a hard-coded fix prevents reactivation of the erroneous code snippet.

oloapinivad commented 5 years ago

Thanks @h-dh, this makes completely sense. Yes, I did force the CHECK_MODE=CV in order to try the full QA-DKRZ suite, but I wasn't aware of the 2017 decision: we won't use the CV check but simply rely on PrePARE. Closing this!

h-dh commented 5 years ago

Resetting CHECK_MODE goes like this: a) the default is disabled completely. b) setting a signless component like CV enables only this one. c) a minus sign in front of a component, e.g. -CV, activates all modules but CV.

cheers, hdh

On 7/1/19 3:06 PM, Paolo Davini wrote:

Thanks @h-dh https://github.com/h-dh, this makes completely sense. Yes, I did force the |CHECK_MODE=CV| in order to try the full QA-DKRZ suite, but I wasn't aware of the 2017 decision: we won't use the CV check but simply rely on PrePARE. Closing this!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/IS-ENES-Data/QA-DKRZ/issues/20?email_source=notifications&email_token=ACJZOW3K5DITUPN6G5F3IALP5H6OTA5CNFSM4H4DUPZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY6B6WY#issuecomment-507256667, or mute the thread https://github.com/notifications/unsubscribe-auth/ACJZOWYB2WGECTIYTBV6XK3P5H6OTANCNFSM4H4DUPZA.

-- Dr. Heinz-Dieter Hollweg Abteilung Datenmanagement Deutsches Klimarechenzentrum GmbH (DKRZ) Bundesstraße 45a • D-20146 Hamburg • Germany

Phone: +49 40 460094-212 FAX: +49 40 460094-270 Email: hollweg@dkrz.de URL: www.dkrz.de

Geschäftsführer: Prof. Dr. Thomas Ludwig Sitz der Gesellschaft: Hamburg Amtsgericht Hamburg HRB 39784

IS-ENES-Data / QA-DKRZ

CV test failing - Json::LogicError #20