Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v1.1.0 Release #760

Merged
merged 154 commits into from
Oct 13, 2024
Merged

v1.1.0 Release #760

merged 154 commits into from
Oct 13, 2024

Conversation

ddobie
Copy link
Contributor

@ddobie ddobie commented Oct 10, 2024

No description provided.

dliptai and others added 30 commits May 19, 2021 17:47
…ead, only pass relevant options required for image ingestion
… writing parquet files outside of the function
…g file that is a subset of the full config options for a pipeline run
Fix README link and documentation 404 assets
[skip ci]
# Conflicts:
#	vast_pipeline/pipeline/main.py
* only read .env if required vars are undefined
Fixes #547
[skip ci]

* updated CHANGELOG

* fixed unused defaults
ddobie and others added 27 commits August 8, 2024 09:31
* Update docker compose syntax

* Updated changelog
* Switch virtualenvs-create: false

* Force numpy=1.18.1

* Undo numpy version adjustment

* Temporarily remove python 3.8 testing

* temporarily force numba install

* hail mary - let's see if python 3.11 works

* Add 3.11 support to pyproject.toml

* Undo

* Updated test-suite actions

* Updated dependencies

* Updated lock?

* Require datashader>0.14

* weird datashader versioning?

* One last attempt at datashader versioning

* Updated lock

* More fiddling

* More dependency fiddling

* test-suite fix?

* Fix docker compose github action syntax

* Limit dask<2022.4.2

* revert to updated test-suite settings

* Try testing python 3.10

* Revert experiments

* More version fixes

* Updated changelog

* Update datashader dependency
* Update github actions

* Bump to python 3.9

* Updated dependencies

* Updated changelog
* Naive attempt

* Revert to python <3.11

* Updated changelog
* Add get_memory_usage function

* Rewrite memory usage functions

* Added memory usage logging to finalise.py

* Added logging to forced_extraction.py

* Added debug logging to loading.py

* Added debug logging to model_generator.py

* Added debug logging to main.py

* Added debug logging to new_sources.py

* Import psutil

* Fix truncated variable name

* Fixed logging in calculate_n_partitions

* Add some logging to partially address #718

* ?

* PEP8

* PEP8

* More PEP8

* PEP8 hell

* Updated changelog
Co-authored-by: Dougal Dobie <[email protected]>
NOTE: I'm not using f-strings for log messages because this is considered bad
practice in logging. f-strings are greedy and will be computed even if the log
isn't printed to the screen. While this isn't an issue here since the log
message is quick to render, it's good practice to always print log messages
in this way in case the message requires an expensive calculation.
See: https://bugs.python.org/issue46200 for some discussion of this.
…dictionary to YAML

This greatly speeds up the initial configuration step since the expansion of
glob expressions for the inputs into thousands of files creates very large
YAML objects that strictyaml is slow to validate. The changes here ensure the
validation step is only done once when writing the updated (expanded glob)
file lists back to _yaml["inputs"].
Each creation of the 'inputs' dictionary in a PipeLine config object
can take a very long time since safeyaml is extremely slow to validate
long file lists when converting to a python list. The PipelineConfig.validation
method recreates the ['inputs'] dictionary many times. Just do it once at the start
then use that dictionary throughout.
Just because I was changing things in this method anyway.
Co-authored-by: Dougal Dobie <[email protected]>
Co-authored-by: Dougal Dobie <[email protected]>
@ddobie ddobie marked this pull request as ready for review October 13, 2024 23:09
@ddobie ddobie merged commit 6eed37d into master Oct 13, 2024
5 checks passed
@ddobie ddobie deleted the release-v1.1.0 branch October 13, 2024 23:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants