Eo-grow

Latest version: v1.7.11

Safety actively analyzes 640549 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 5

1.6.3

- Pipelines can request specific type of worker when run on a ray cluster with the `ray_worker_type` field.
- Area managers now generate the patch lists more efficiently.
- Pipelines have option to fail when temporally-ill defined EOPatches are encountered with the `raise_on_temporal_mismatch` flag.

1.6.2

- Fixed a bug in `BatchDownloadPipeline` where the evalscript was not read correctly.

1.6.1

- Pipelines can now save EOPatches in Zarr format
- Testing utilities now also compare vector-based files. Numerical precision of comparison was adjusted.
- Evalscripts are now read from storage. Removed import-path capabilities of config language.

1.6.0

- Adjusted to use `eo-learn 1.5.0`
- `compression` parameters were removed since they are redundant
- Removed interpolation from `eogrow.pipelines.features`.
- `LinearFunctionTask` moved to `eogrow.tasks.common` from `eo-learn`
- many adjustments due to parser changes
- In pipeline configs dictionary keys can now also contain variables.
- Default resizing backend changed to cv2 (to comply with changes in eo-learn).
- Merging timestamps of samples is no longer an option in the sample-merging pipeline.

1.5.2

- Pipelines using a Ray cluster now add the cluster configuration file to the logs folder.
- The CLI command `eogrow-ray` no longer supports `--screen` and `--stop` commands.
- Changelog now also stored in the `CHANGELOG.md` file.
- Improved test-data generating pipeline.
- Switched from `flake8` and `isort` to `ruff`.
- Various minor improvements.

1.5.1

- Fix bug in `LoggingManager.Schema` where `Tuple[str]` was used instead of `Tuple[str, ...]` for certain fields, preventing parsing of correct configurations.

Page 3 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.