Releases: pytti-tools/pytti-core
v0.7.5
Big refactor. Generic powerful test pattern added. Error graphs may be unreliable when using gradient accumulation, consider adding a warning there. not a huge deal, the main use case here is just art anyway. Relative errors still useful.
What's Changed
Full Changelog: v0.7.4...v0.7.5
v0.7.4
v0.7.3
v0.7.2
v0.7.1
What's Changed
- A ton of code cleanup
- Fixed issue caused by duplicate config files in install location
Full Changelog: v0.7.0...v0.7.1
v0.7.0
v0.6.0 - Installable
pytti-core, AdaBins, and GMA codebases modified to permit setuptools installation.
- Resolves common bugs that previously required modifying PATH/PYTHONPATH variables
- Resolves
utils
submodule namespace collisions between AdaBins and GMA - Significantly improves user experience for local use, where these issues commonly caused issues
To facilitate installation, all three codebases were restructured under a src
tree. Incrementing minor version because user-facing API is unchanged, but backend API is not backwards compatible by design.
v0.5.3
v0.5.2
Fixed wonky import structure for GMA and AdaBins. Assumes pytti-notebook setup cell has been run, which includes some hacky repair code. Concretely:
-
Empty
__init__.py
added in several places to facilitate importing without changing directory!touch AdaBins/__init__.py !touch GMA/__init__.py !touch GMA/core/__init__.py
-
Pretrained AdaBins downloaded to top-level
./pretrained
folder rather than./AdaBins/pretrained
!mkdir -p ./pretrained if not path_exists('./pretrained/AdaBins_nyu.pt'): !gdown https://drive.google.com/uc?id=1lvyZZbC9NLcS8a__YPcUP7rDiIpbRpoF if not path_exists('AdaBins_nyu.pt'): !gdown https://drive.google.com/uc?id=1zgGJrkFkJbRouqMaWArXE4WF_rhj-pxW !mv AdaBins_nyu.pt ./pretrained/AdaBins_nyu.pt
-
PYTHONPATH
modification in workhorse.py, moved GMA/core before AdaBins.- This is necessary due to a namespace conflict for importing a
utils
submodule, which is defined in both codebases - Both codebases where designed without installation in mind and so import from "utils" directly.
- Would be safer if we modified respective codebases to import from e.g.
GMA.utils
orAdabins.utils
. Potential solution here is to make these changes in a fork and change the notebook's setup git clone invocations to clone our modified forks rather than the reference implementations
- This is necessary due to a namespace conflict for importing a