Release v4.13.x
2025-05-09
Version description of the v4.13.1 release of SlideRule Earth.
New/Improved Functionality
v4.13.1 - #466 - source dataset information embedded into results
v4.13.1 - #493 - GEDI results include orbit number
v4.13.0 - Usage statistics and trending now supported through a
managerapplication which collects telemetry and stores it in a persistent DuckDB database that is maintained in our S3 bucket.v4.13.0 - 0478900 - GEDTM uses locally hosted rasters for significant performance increase
v4.13.0 - 5d204f1 - support for EGM08 in
atl03xv4.13.0 - a72bb0a - added track information to GEDI dataframes
Issues Resolved
v4.13.1 - #266 - GEDI rasters support vertical shifts
v4.13.1 - #487 -
atl24xqueries CMR for ATL24 datasetv4.13.1 - #463 - YAPC version 3 fixed
v4.13.0 - 8814ffc - CMR max resources reached returns error instead of silently truncating (matches client behavior)
v4.13.0 - 97a55ae - fixed access to BlueTopo
v4.13.0 - 5a04947 - fixed access to Meta Global Canopy
v4.13.0 - db38b4c - s3 retries always rebuild header
v4.13.0 - db38b4c - the endpoint being called is now provided in the metadata of the return dataframe
v4.13.0 - 5b95dc4 - more robust error handling in metric gathering in orchestrator
v4.13.0 - d8a813a - fixed GEDI raster sampling code to apply vertical offset when necessary
Development Changes
v4.13.1 - #222 - removed jamming dns for github actions; instead just wait for dns to be active
v4.13.1 - #140 - build version information includes OS info
v4.13.1 - #492 - updating signature of override of dns lookup in python client to interface with dask without issues
v4.13.1 - #418, #56 - reworked runtime configuration management
v4.13.1 - #480 - scrubbed header files for faster compile times
v4.13.0 - Overhauled and cleaned up the Python client examples and utilities. They should all work; and the examples should provide a good starting point for using different features of the client.
v4.13.0 - Python client reworked to pull out the code that handles the low-level information exchange protocol between the server and client into its own module
session.py. This should be transparent to users of the client; but makes the code easier to maintain, and supports future use cases where interaction with the server APIs wants to be handled directly.v4.13.0 - db38b4c - pytests do not jam DNS but wait for the cluster to fully come up including DNS entries to become active
v4.13.0 - Static website overhauled with changes to the organization of the documentation, and a scrub of old information to bring it all up to date.
v4.13.0 - GitHub actions / selftests / pytests - all updated to run cleanly
v4.13.0 - 1840282 - parameterized the use of CRS’s in the Python client
Getting This Release
https://github.com/SlideRuleEarth/sliderule/releases/tag/v4.13.1
Benchmarks
clients/python/utils/benchmark.py
atl06_aoi <690326 x 16> - 39.621595 secs
atl06_ancillary <914 x 17> - 2.990283 secs
atl03_ancillary <914 x 17> - 2.724033 secs
atl06_parquet <1577 x 18> - 2.700799 secs
atl03_parquet <22833 x 23> - 1.515308 secs
atl06_sample_landsat <914 x 20> - 8.168051 secs
atl06_sample_zonal_arcticdem <1696 x 27> - 8.840394 secs
atl06_sample_nn_arcticdem <1696 x 20> - 4.531418 secs
atl06_msample_nn_arcticdem <1696 x 20> - 4.470971 secs
atl06_no_sample_arcticdem <1696 x 16> - 2.554142 secs
atl03_rasterized_subset <51968 x 22> - 2.303672 secs
atl03_polygon_subset <50799 x 22> - 1.909250 secs
Baseline
clients/python/utils/baseline.py
GEDI / 3DEP = 2660.2507194650643
ICESat-2 / ArcticDEM = 1603.1273510971787
ICESat-2 / ATL06p = 1810.051657043249
ICESat-2 / PhoREAL = 4.078258037567139