Closed khelfen closed 1 year ago
@ClaraBuettner / @IlkaCu this PR is completed from my side. Is there any CI run planned? In which CI branch should I merge those changes for testing?
You can use CI branch continuous-integration/run-everything-2022-11-10
. But we didn't schedule the new CI run yet.
@KathiEsterl maybe you could already review this PR?
Do you think it is necessary to run the code and check the results again? I guess you have done it anyways.
I would suggest to approve it, although I "only" looked at the changes in the code one more time and checked the code together with you yesterday. I think for those changes this is sufficient.
Do you think it is necessary to run the code and check the results again? I guess you have done it anyways.
I would suggest to approve it, although I "only" looked at the changes in the code one more time and checked the code together with you yesterday. I think for those changes this is sufficient.
The only thing I can imagine is that the chosen tolerance for the sanity checks is not high enough in all cases in a full run. That way the sanity checks would fail, but everything should still work as expected.
I'm not sure if that should be tested within the CI before merging. Would be an easy fix anyway. @IlkaCu maybe you can decide this?
It has been running on CI meanwhile, right? How is it about the tolerances? If everything is fine, we can merge it to dev now, I guess.
Fixes #1088 .
Before merging into
dev
-branch, please make sure thatCHANGELOG.rst
was updated.black
andisort
.Dataset
-version is updated when existing datasets are adjusted.continuous-integration/run-everything-over-the-weekend
-branch.test mode
.Everything
mode.