climix issueshttps://git.smhi.se/climix/climix/-/issues2023-05-29T09:09:58Zhttps://git.smhi.se/climix/climix/-/issues/270Add a warning and raise a error if datafiles from unrelated datasets are used...2023-05-29T09:09:58ZCarolina NilssonAdd a warning and raise a error if datafiles from unrelated datasets are used together, e.g. tasmin and TNWhen running Climix with two input files from different datasets that uses two different variable names, e.g., tasmin and TN. Climix creates two separate cubes (which is correct), however, Climix only runs the index computation on one of...When running Climix with two input files from different datasets that uses two different variable names, e.g., tasmin and TN. Climix creates two separate cubes (which is correct), however, Climix only runs the index computation on one of them. This can be misleading for the user and go unnoticed. To improve the handling of this case a warning followed by aborting immediately should happen IF there are more than one cube after the concatenation AND if there is only one data variable required for the index calculation.https://git.smhi.se/climix/climix/-/issues/251time.coord check for meaningful amount of time steps2023-06-09T14:04:32ZRenate Wilcketime.coord check for meaningful amount of time stepsclimix calculates an index also for a "year" with only one time step, resulting in a wrong value. That happens when the input data (daily fields) have been created from hourly data but the last time step is the first (00:00:00) of the ne...climix calculates an index also for a "year" with only one time step, resulting in a wrong value. That happens when the input data (daily fields) have been created from hourly data but the last time step is the first (00:00:00) of the next year.
It would be good to have a check for something like number of years mus result in at least number of days to avoid index created from one hour or day.https://git.smhi.se/climix/climix/-/issues/179tasmidpoint as standin for tas2023-04-04T21:15:34ZLars Bärringtasmidpoint as standin for tasThe well established indices were developed within the observational data communities. And in that context daily mean temperature, as in `tas: cell_method = "time: mean"`, brings about a lot of complications (given the limited and shifti...The well established indices were developed within the observational data communities. And in that context daily mean temperature, as in `tas: cell_method = "time: mean"`, brings about a lot of complications (given the limited and shifting observation times). Hence they settled for the draconian solution that **daily mean temperature is defined as `(TN+TX)/2`**, which in terms of CF would be `tas: cell_method = "time: midpoint` (assuming that the time bound specify daily data!), where *`tas`* should have another name, such as `tasmidpoint`.
We should have the possibility to compute `tas`-based indices on `tasmidpoint`, which then should be calculated on the fly as if input data had been specified as `low_data: tasmin, high_data: tasmax`