Closed zebengberg closed 3 months ago
One question: does our definition of a "breaking change" just include changes to intended behavior, or also bug fixes that change behavior for cases affected by the bug? (The
step_threshold
changes are in the second category, and I'm not sure if we should note them in the breaking changes section of the changelog.)
You're absolutely right -- we often blur this line. In this case, I think it's enough to note the change just in the fix category ... but it's definitely a matter of opinion.
Fixes
step_threshold
inFlight._altitude_interpolation
. This correction is only relevant when passing in a non-default value forfreq
inFlight.resample_and_fill
.VectorDataset.__eq__
method to check for the same keys. Previously, if the other dataset had a superset of the instance keys, the method may still returnTrue
.Internals
Improve the runtime performance of
Fleet.to_flight_list
. For a largeFleet
, this method is now 5x faster. The plot below shows my benchmarking.Improve the runtime performance and memory footprint of
Cocip._bundle_results
. When runningCocip
with a largeFleet
source,Cocip.eval
is now slightly faster and uses much less memory.Tests
make test
)