CORBASS issueshttps://git.gfz-potsdam.de/sec23/korte/corbass/-/issues2020-01-06T12:49:32+01:00https://git.gfz-potsdam.de/sec23/korte/corbass/-/issues/21Benchmark / Test2020-01-06T12:49:32+01:00Stefan MauerbergerBenchmark / TestWeren't it desirable having a benchmark to guarantee integrity of results while development goes on?Weren't it desirable having a benchmark to guarantee integrity of results while development goes on?https://git.gfz-potsdam.de/sec23/korte/corbass/-/issues/17Raise if spanning the fine grid fails2019-11-16T06:53:04+01:00Stefan MauerbergerRaise if spanning the fine grid failsIf something goes wrong in the exploration phase e.g. the range is very little or even zero stop execution.If something goes wrong in the exploration phase e.g. the range is very little or even zero stop execution.https://git.gfz-potsdam.de/sec23/korte/corbass/-/issues/9Numpy warning that the covariance is not PD2019-11-18T13:18:26+01:00Maximilian SchannerNumpy warning that the covariance is not PDCurrently numpy.random.multivariate_normal always throws a warning, that even though we clearly have covariances, they are not positive definite. This may be due to the svd algorithm used. In numpy 1.18 there will be a switch to use chol...Currently numpy.random.multivariate_normal always throws a warning, that even though we clearly have covariances, they are not positive definite. This may be due to the svd algorithm used. In numpy 1.18 there will be a switch to use cholesky instead. Once 1.18 is available via conda, we should use this switch and see wether it makes the warning disappear.
The corresponding line is [here](https://gitext.gfz-potsdam.de/arthus/corbass/blob/master/corbass/evaluation.py#L220).