New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the metadata keys that uniquely identify a DataArray (DataID) configurable per reader #1088
Make the metadata keys that uniquely identify a DataArray (DataID) configurable per reader #1088
Commits on Feb 25, 2020
Commits on Feb 27, 2020
Commits on Mar 3, 2020
Commits on May 4, 2020
Commits on May 5, 2020
Commits on May 15, 2020
Commits on May 25, 2020
-
-
-
-
-
-
The bad calibration test was moved to the dataset id tests, as it is now handled there.
-
Commits on Jun 3, 2020
Commits on Jun 5, 2020
Commits on Jun 8, 2020
Commits on Jun 9, 2020
Commits on Jul 7, 2020
Commits on Jul 8, 2020
Commits on Jul 9, 2020
Commits on Jul 14, 2020
Commits on Jul 15, 2020
Commits on Jul 27, 2020
Commits on Jul 28, 2020
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Remove handling of derived metadata
I.e. midnight scanline and missing scanlines
-
-
-
-
-
-
-
-
-
-
-
-
Add test utility to make a scene.
Add a test utility to make a scene from artificial data. The artificial data are provided by the user, fake areas are added by the routine.
-
-
Correct dim order when making a scene
In the testing utility to make a scene, correct the order of dimensions.
-
Expand make-a-scene utility and add a test for it
Expand the make_a_scene utility in the tests, and add a test for the test utility itself.
-
-
Rename make_a_scene and accept concrete areas
Rename make_a_scene to make_a_fake_scene. Add an option to accept a concrete area to be used for the generated datasets. Rename cont_dict to content_dict. Improve documentation.
-
Add per-frame decoration to MultiScene
In MultiScene.save_animation, add the ability to add decorations, enhancements, and overlays. As a special case, decoration text will be substituted allowing it to vary per frame. This enables the user to add the time to every frame. I took the unit test out of the `unittest.TestCase` class because I could otherwise not get the call assertions on the `get_enhanced_image` mock to wark.
-
-
Refactor formatting to own method
Refactor the formatting of text in an animated decoration to its own method, reducing code complexity.
-
Fixes in multiscene decoration
In the multiscene decoration and its test, a couple of small fixes. Tests now pass.
-
Refactor part of _get_animation_frames
Refactor part of _get_animation_frames into its own method, reducing the complexity of the former.
-
Tests for Python 3.7 are failing on Travis CI but succeeding on my local workstation. Temporarily add a `conda list` command to be executed on Travis so I can compare versions for numpy and other packages.
-
Replace assert_called_with with direct args check
In the mock for testing decorating a multiscene, replace the assertion that it's called with a particular dataset to more direct argument checking. Any assert_calls with a numpy array is unreliable, because assert_called_with will use an equality operator which may fail, in this case depending on the unpredictable order of calls. See https://stackoverflow.com/q/56644729/974555
-
Adapt deco for correct interface to pydecorate
Fix the animation decoration text replacement for the correct interface; the text to be replaced is in `kwargs["decorate"]["decorate"][0]["text"]["txt"]`.
-
Add decoration example to multiscene documentation
In the multiscene documentation, add an example of how to add the time for each frame to each image.
-
Refactor, group arguments to get_enhanced_image
Reduce number of function arguments to save_animation by grouping the arguments to be passed to get_enhanced_image.
-
Remove conda list from travis.yml again
Remove conda list from travis.yml again, as it was a red herring and did not really help me fix the (now resolved) issue in the unit test mocking.
-
Refactor save_animation to make it shorter
Refactor save_animation to make it shorter, moving some of the functionality to its own method.
-
Fix bug introduced in refactoring, where the caller's dictionary was inadvertently changed.
-
-
Add missing docs with sphinx-apidoc
Added missing documentations by re-running ``sphinx-apidoc -f -T -o source/api ../satpy ../satpy/tests``
-
Remove article from function name
Remove the article ``a`` from the function name in ``make_a_fake_scene``, such that this function is now called ``make_fake_scene``.
-
Fixed formatting which had become un-PEP8-ified due to function renaming. Co-authored-by: Martin Raspaud <martin.raspaud@smhi.se>
-
Remove _maybe from method name
In the multiscene decoration, remove _maybe from the method name.
-
-
Remove duplicate line from multiscene decoration
Remove a duplicate line from the multiscene decoration
-
Remove more duplicate lines, doubly initialising two dictionaries.
-
-
-
Fix "see above" reference at start of enhance docs
Fix a reference to an example "above" that was completely at the start of the enhancements.rst documentation. From an earlier version, it appears this was intended to refer to an enhancements example in composites.rst. Change "above" to instead link to this example in composites.rst.
-
-
-
-
-
-
-
-
Move test_fake_scene to test_utils
Move the function that tests make_fake_scene from testing/utils.py to testing/test_utils.py, so that it should be executed by default as part of the testing suite, including on Travis.
-
Commits on Jul 29, 2020
Commits on Jul 30, 2020
-
-
-
-
-
Fix typo in doc/source/dev_guide/satpy_internals.rst
Co-authored-by: Gerrit Holl <gerrit.holl@gmail.com>
-
-