SMI issueshttps://git.ufz.de/chs/progs/SMI/-/issues2021-02-03T15:55:58+01:00https://git.ufz.de/chs/progs/SMI/-/issues/4Internally calculated moving average2021-02-03T15:55:58+01:00Friedrich BoeingInternally calculated moving averageA note should be added that when choosing a moving average, the first SM values (up to the moving average period) have no preceded SM data, hence the moving average is not calculated correctly. Either these SMI values have to be removed ...A note should be added that when choosing a moving average, the first SM values (up to the moving average period) have no preceded SM data, hence the moving average is not calculated correctly. Either these SMI values have to be removed manually afterwards or these SMI values should be left out in the output. (E.g. choosing 31 days lag, the first 31 daily SM values which are to be processed lack preceded SM information)Stephan ThoberStephan Thoberhttps://git.ufz.de/chs/progs/SMI/-/issues/6Area averaged SMI2020-04-07T15:28:44+02:00Pallav Kumar Shresthapallav-kumar.shrestha@ufz.deArea averaged SMIAt the moment SMI works in **raster-in** (SM) **raster-out** (SMI) mode.
My request for area averaged SMI:
* keeping mHM netCDF file as standard input
* the same **raster-in** (SM from mHM netCDF file) and **point-out** (area averaged...At the moment SMI works in **raster-in** (SM) **raster-out** (SMI) mode.
My request for area averaged SMI:
* keeping mHM netCDF file as standard input
* the same **raster-in** (SM from mHM netCDF file) and **point-out** (area averaged SMI).
* For this a mask is to be provided based on which SM is averaged over each zone of mask and single SMI time series is created for each zone.
@rkumar 's idea:
* SMI program should not do the masking internally
* Input is area averaged point TS i.e. if **point-in** then **point-out**; if **raster-in** then **raster-out**
* SMI should then know (from namelist?) whether input is time series of point data or a field.
* The point netCDF input should have a prescribed structure.Stephan ThoberStephan Thoberhttps://git.ufz.de/chs/progs/SMI/-/issues/11time axis bug2023-10-23T16:09:31+02:00Stephan Thobertime axis bugApparently, SMI does not read the time axis correctly if monthly values do not start in January.
@lese : can you please add your files here?Apparently, SMI does not read the time axis correctly if monthly values do not start in January.
@lese : can you please add your files here?