You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a part of the release notes for each build, there should be a section that provides a set of output values for well-known tests. The tests establish a baseline of performance and allow users to track the expected differences in output of SlideRule over the years.
For example, someone could ask how the results of a SlideRule have changed since 2022. They could be asking this because they did some research with SlideRule in 2022 and published some results and now the question is if they wanted to repeat their analysis in 2024, will their results substantially change.
This information can be used both to capture changes in:
dependencies (e.g. PROJ, GDAL, gcc, etc.)
implementation (e.g. bug fixes to algorithms, enhancements)
data versions (e.g. ATL03 v005 vs v006)
The text was updated successfully, but these errors were encountered:
As a part of the release notes for each build, there should be a section that provides a set of output values for well-known tests. The tests establish a baseline of performance and allow users to track the expected differences in output of SlideRule over the years.
For example, someone could ask how the results of a SlideRule have changed since 2022. They could be asking this because they did some research with SlideRule in 2022 and published some results and now the question is if they wanted to repeat their analysis in 2024, will their results substantially change.
This information can be used both to capture changes in:
The text was updated successfully, but these errors were encountered: