data-qa issueshttps://git.smhi.se/uwe.fladrich/data-qa/-/issues2019-08-16T09:43:35Zhttps://git.smhi.se/uwe.fladrich/data-qa/-/issues/121pctCO2 r1i1p1f12019-08-16T09:43:35ZUwe Fladrich1pctCO2 r1i1p1f1DECK run 1pctCO2 r1i1f1p1 at SMHI:
`b604; 1pctCO2; r1i1p1f1; 1850-2000; trunk r6369; Beskow; tbl3-2160; IFS: CMIP/EC-EARTH-Veg/cmip6-experiment-CMIP-piControl ; NEMO: test-all-mips`DECK run 1pctCO2 r1i1f1p1 at SMHI:
`b604; 1pctCO2; r1i1p1f1; 1850-2000; trunk r6369; Beskow; tbl3-2160; IFS: CMIP/EC-EARTH-Veg/cmip6-experiment-CMIP-piControl ; NEMO: test-all-mips`https://git.smhi.se/uwe.fladrich/data-qa/-/issues/114xCO2 r1i1p1f12019-08-16T09:43:31ZUwe Fladrich4xCO2 r1i1p1f1DECK run 4xCO2 r1i1p1f1 at SMHI:
`b603; 4xCO2; r1i1p1f1; 1850-2000; trunk r6369; Beskow; tbl3-2160; IFS: CMIP/EC-EARTH-Veg/cmip6-experiment-CMIP-piControl ; NEMO: test-all-mips`DECK run 4xCO2 r1i1p1f1 at SMHI:
`b603; 4xCO2; r1i1p1f1; 1850-2000; trunk r6369; Beskow; tbl3-2160; IFS: CMIP/EC-EARTH-Veg/cmip6-experiment-CMIP-piControl ; NEMO: test-all-mips`https://git.smhi.se/uwe.fladrich/data-qa/-/issues/10ssp1-1.9 r1i1p1f12019-10-29T08:23:57ZUwe Fladrichssp1-1.9 r1i1p1f1ScenarioMIP ssp1-1.9 r1i1p1f1 at SMHI:
`t625; ssp1-1.9; r1i1p1f1; 2015-2100; trunk r6679; Tetralith; t613-2015; yes; ScenarioMIP/cmip6-experiment-ScenarioMIP-ssp126 + fixes`ScenarioMIP ssp1-1.9 r1i1p1f1 at SMHI:
`t625; ssp1-1.9; r1i1p1f1; 2015-2100; trunk r6679; Tetralith; t613-2015; yes; ScenarioMIP/cmip6-experiment-ScenarioMIP-ssp126 + fixes`https://git.smhi.se/uwe.fladrich/data-qa/-/issues/9ssp1-1.9: Missing output control files2019-07-11T08:21:35ZUwe Fladrichssp1-1.9: Missing output control filesThere are no output control files present in the EC-Earth trunk for the ssp1-1.9 scenario, which formally prevents cmorisation. I guess the reason is that this scenario is not prioritised, but at least SMHI has made the r1i1p1f1 member f...There are no output control files present in the EC-Earth trunk for the ssp1-1.9 scenario, which formally prevents cmorisation. I guess the reason is that this scenario is not prioritised, but at least SMHI has made the r1i1p1f1 member for it.
My guess is that, at least for cmorisation, the `varlist.json` file from the other ScenarioMIP runs of the same model configuration (`EC-EARTH-Veg` in our case), would be fine, but I would like to confirm. Can I use one of the others (e.g. `cmip6-data-request-varlist-ScenarioMIP-ssp126-EC-EARTH-Veg.json`) for ssp1-1.9?https://git.smhi.se/uwe.fladrich/data-qa/-/issues/8ssp5-8.5 r1i1p1f12019-08-16T09:43:28ZUwe Fladrichssp5-8.5 r1i1p1f1ScenarioMIP ssp5-8.5 r1i1p1f1 at SMHI:
`t624; ssp5-8.5; r1i1p1f1; 2015-2100; trunk r6679; Tetralith; t613-2015; yes; ScenarioMIP/cmip6-experiment-ScenarioMIP-ssp126 + fixes`ScenarioMIP ssp5-8.5 r1i1p1f1 at SMHI:
`t624; ssp5-8.5; r1i1p1f1; 2015-2100; trunk r6679; Tetralith; t613-2015; yes; ScenarioMIP/cmip6-experiment-ScenarioMIP-ssp126 + fixes`https://git.smhi.se/uwe.fladrich/data-qa/-/issues/7ssp3-7.0 r1p1i1f12019-08-16T09:43:30ZUwe Fladrichssp3-7.0 r1p1i1f1ScenarioMIP ssp3-7.0 r1i1p1f1 at SMHI:
`t623; ssp3-7.0; r1i1p1f1; 2015-2100; trunk r6679; Tetralith; t613-2015; yes; ScenarioMIP/cmip6-experiment-ScenarioMIP-ssp126 + fixes`ScenarioMIP ssp3-7.0 r1i1p1f1 at SMHI:
`t623; ssp3-7.0; r1i1p1f1; 2015-2100; trunk r6679; Tetralith; t613-2015; yes; ScenarioMIP/cmip6-experiment-ScenarioMIP-ssp126 + fixes`https://git.smhi.se/uwe.fladrich/data-qa/-/issues/6ssp2-4.5 r1i1p1f12019-08-16T09:43:27ZUwe Fladrichssp2-4.5 r1i1p1f1ScenarioMIP ssp2-4.5 at SMHI
`t622; ssp2-4.5; r1i1p1f1; 2015-2100; trunk r6679; Tetralith; t613-2015; yes; ScenarioMIP/cmip6-experiment-ScenarioMIP-ssp126 + fixes`ScenarioMIP ssp2-4.5 at SMHI
`t622; ssp2-4.5; r1i1p1f1; 2015-2100; trunk r6679; Tetralith; t613-2015; yes; ScenarioMIP/cmip6-experiment-ScenarioMIP-ssp126 + fixes`https://git.smhi.se/uwe.fladrich/data-qa/-/issues/5ssp1-2.6 r1i1p1f12019-08-16T09:43:23ZUwe Fladrichssp1-2.6 r1i1p1f1ScenarioMIP ssp1-2.6 r1i1p1f1 at SMHI:
`t621; ssp1-2.6; r1i1p1f1; 2015-2100; trunk r6679; Tetralith; t613-2015; yes; ScenarioMIP/cmip6-experiment-ScenarioMIP-ssp126 + fixes`ScenarioMIP ssp1-2.6 r1i1p1f1 at SMHI:
`t621; ssp1-2.6; r1i1p1f1; 2015-2100; trunk r6679; Tetralith; t613-2015; yes; ScenarioMIP/cmip6-experiment-ScenarioMIP-ssp126 + fixes`First set of experiments published by at ESGF (SMHI)https://git.smhi.se/uwe.fladrich/data-qa/-/issues/4piControl r1i1p1f12019-08-16T09:41:55ZUwe FladrichpiControl r1i1p1f1piControl experiment at SMHI:
`b601; piControl; r1i1p1f1; 1850-2450; trunk r6369; Beskow; tbl3-2160; IFS: CMIP/EC-EARTH-Veg/cmip6-experiment-CMIP-piControl ; NEMO: test-all-mips`piControl experiment at SMHI:
`b601; piControl; r1i1p1f1; 1850-2450; trunk r6369; Beskow; tbl3-2160; IFS: CMIP/EC-EARTH-Veg/cmip6-experiment-CMIP-piControl ; NEMO: test-all-mips`First set of experiments published by at ESGF (SMHI)https://git.smhi.se/uwe.fladrich/data-qa/-/issues/3historical r1i1p1f12019-08-16T09:43:25ZUwe Fladrichhistorical r1i1p1f1Historical run at SMHI:
`t607; historical; r1i1p1f1; 1850-2014; trunk r6379; Tetralith; b601-1930; CMIP/EC-EARTH-AOGCM/cmip6-experiment-CMIP-historical`Historical run at SMHI:
`t607; historical; r1i1p1f1; 1850-2014; trunk r6379; Tetralith; b601-1930; CMIP/EC-EARTH-AOGCM/cmip6-experiment-CMIP-historical`First set of experiments published by at ESGF (SMHI)https://git.smhi.se/uwe.fladrich/data-qa/-/issues/2AMIP r1i1f1p12019-08-16T09:43:19ZKlaus ZimmermannAMIP r1i1f1p1First set of experiments published by at ESGF (SMHI)https://git.smhi.se/uwe.fladrich/data-qa/-/issues/1piControl r1i1p1pf: Time series broken in NEMO files for 19872019-10-09T06:31:33ZUwe FladrichpiControl r1i1p1pf: Time series broken in NEMO files for 1987For the SMHI **piControl** **r1i1p1f1** run (#4), `nctime` reports a broken time series for variables:
```
3hr: tos
Oday: omldamax, tos, tossq
SIday: siconc, siu, siv, sithick
```
More specifically, the time series is broken like:
...For the SMHI **piControl** **r1i1p1f1** run (#4), `nctime` reports a broken time series for variables:
```
3hr: tos
Oday: omldamax, tos, tossq
SIday: siconc, siu, siv, sithick
```
More specifically, the time series is broken like:
```
siconc_SIday_EC-Earth3-Veg_piControl_r1i1p1f1_gn_19870101-19871218.nc
BREAK
siconc_SIday_EC-Earth3-Veg_piControl_r1i1p1f1_gn_19880101-19881231.nc
```
for all of the variables, i.e. always between the end of 1987 and beginning of 1988.
Checking the raw NEMO output, it turns out that indeed all daily files for 1987 (leg 138 of b601) are shorter (end on December 18th):
```
> for f in 138/b601_1d_19870101_19871231_*.nc ; do echo -n "$f: "; ncdump -h $f | grep "time_counter ="; done
138/b601_1d_19870101_19871231_lim_grid_T_2D.nc: time_counter = UNLIMITED ; // (352 currently)
138/b601_1d_19870101_19871231_lim_grid_U_2D.nc: time_counter = UNLIMITED ; // (352 currently)
138/b601_1d_19870101_19871231_lim_grid_V_2D.nc: time_counter = UNLIMITED ; // (352 currently)
138/b601_1d_19870101_19871231_opa_grid_T_2D.nc: time_counter = UNLIMITED ; // (352 currently)
```
The same is true for the 3hourly file (which contains only `tos`). This suggests that even the monthly files may somehow be affected, even though there is no formal problem as of now.
It is not known, at this stage, why the last days are missing. The corresponding NEMO log file indicates that the run continued to `DATE Y/M/D = 1987/12/31 nday_year = 365` and the IFS files for the same year do not show any irregularities (as far as checked).