Tags give the ability to mark specific points in history as being important
-
0.4.0
Release: 0.4.044220756 · ·Release version 0.4.0 New features ------------ - The narrowband-to-broadband conversion model for the MSI VNS channels is now able to use multiple sets of coefficients, one set per solar zenith angle bin. There are two changes in the config file to reflect this: `coefficients_nb2bb_vns` now contains a set of regression coefficients per solar zenith angle bin, so the number of dimensions is now 3, and a new variable `coefficients_nb2bb_vns_solar_zenith_angles` has been added, specifying the end points of the solar zenith angle bins. Default coefficients from theoretical regressions for the range 0° to 80° have been added. Note that the previous coefficients corresponded to the current coefficients at a solar zenith angle of 30°. - The masking behaviour of the VNS narrowband-to-broadband conversion functions has changed. Broadband quantities derived from the VNS channels will now always be masked outside of the range of solar zenith angles specified in the narrowband-to-broadband model. For the default config file, this means that values will be masked for solar zenith angles between 80° and 90°. Changes breaking backward compatibility of the interface -------------------------------------------------------- None. Other changes ------------- - Fixed a bug in the conversion from brightness temperatures to radiances: the code would silently extrapolate beyond the upper end of the look-up table. Now it masks the data instead. - Avoid a rare error condition where an exception would be raised in the destructor of EcaioBase. It didn't seem to do any harm, but it shouldn't raise an exception, either. - The data model has been reviewed. While this doesn't affect users directly, it does open the door for more powerful testing. - When a variable can't be found in an EarthCARE product, the exception that is raised is now of a custom type, whereas before it used to be of type `AttributeError`. I never advertised the type of this exception, so I don't consider this to be a breaking change for users. - Fixed a bug where the narrowband-to-broadband unfiltered solar radiance wasn't exactly zero at night.
-
0.3.0
Release: 0.3.06db140ba · ·Release version 0.3.0 Added support for the following file types: `BBR_NOM_1B`, `BM__RAD_2B`, `BMA_FLX_2B`. New features ------------ - It is now possible to select the different resolutions in BBR L1 and L2 products with the following syntax: `ec.full`, `ec.standard`, `ec.small`, and with `ec.assessment` for `BM__RAD_2B` and `BMA_FLX_2B`. - For the `BBR_NOM_1B` and `BM__RAD_2B` products, it is possible to obtain Shapely polygons representing the PSF one-weight and zero_weight boundaries with `ec.one_weight_edge_polygons` and `ec.zero_weight_edge_polygons`. - There are new categorical Pandas data types for the BBR views and bands. Changes breaking backward compatibility of the interface -------------------------------------------------------- None. Other changes ------------- - There are two new dependencies: `pandas` and `shapely`.
-
0.2.4
Release: 0.2.48a7f5510 · ·Release version 0.2.4 New features ------------ - EcaioTime now has a class method to initialize from a Python standard library `datetime` object. Note that the `datetime` object must be timezone-aware; naïve `datetime` objects (i.e., not carrying associated time zone information) will be rejected with an exception. Changes breaking backward compatibility of the interface -------------------------------------------------------- None. Other changes ------------- - The file-type handler classes, and their Python files, have been renamed to match the specific file type they should handle. This should scale better as we start to add more file type handlers in the future. As the file-type specific handlers have not been documented and never been advertised so far, this should not be a breaking change for users.
-
0.2.3
Release: 0.2.38c1666b4 · ·Release version 0.2.3 New features ============ None. Changes breaking backward compatibility of the interface ======================================================== None. Other changes ============= - Cleared up an inconsistency in the calculation of the MSI VNS reflectances. Now MSI VNS reflectances are always masked for solar zenith angles >= 90°, regardless of the setting of `reflectance_sza_threshold`. Broadband radiative variables computed from MSI have a solar component equal to zero for solar zenith angles >= 90°; this allows the filtered total radiance to have a meaningful component at night.
-
-
-