Hi all, After great help from Bill L. and Bill S. we have come to the following conclusions as to what is essential for CISM to read in the correct time slices from the forcing file: - as stated above: separate input file with initial ice thickness etc.- forcing file under [CF forcing] section in config file- forcing file may contain an unlimited or a fixed time dimension- time values must incrementally increase, as CISM interprets these values rather than the order of the time slices Partial ncdump output giving example of working forcing file: ncdump -v time 2testforcing.nc netcdf 2testforcing {dimensions:time = UNLIMITED ; // (1001 currently)y1 = 701 ;x1 = 376 ; variables:(..)float time(time) ;time:long_name = "Model time" ;time:standard_name = "time" ;time:units = "year since 1-1-1 0:0:0" ; time:calendar = "none" ;data: time = 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, (..)
For whoever is interested, I have written a matlab script with which to alter netcdf files with a single time slice into time varying forcing files for test runs. I'm happy to share it, and can be contacted under l.n.vanderlaan@uu.nl