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

updates for tifffile, vigra, pytorch #2800

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 3 additions & 3 deletions conda-recipe/meta.yaml
Expand Up @@ -53,10 +53,10 @@ outputs:
- python-elf >=0.4.8
- scikit-image
- scikit-learn
- tifffile
- tifffile >=2023
# build 1.11.1=*_1028 on cf is the first to be compatible with numpy>1.19
# need to bump this manually until there is a true version bump in vigra
- vigra
- vigra 1.11.2*
- xarray !=2023.8.0,!=2023.9.0,!=2023.10.0
- z5py
run_constrained:
Expand Down Expand Up @@ -152,7 +152,7 @@ outputs:
run:
- python 3.9.*
- ilastik-core {{ setup_py_data.version }}
- pytorch >=1.6
- pytorch >=2
- tiktorch 23.11.0*
- inferno
- torchvision
Expand Down
6 changes: 3 additions & 3 deletions dev/environment-dev.yml
Expand Up @@ -36,18 +36,18 @@ dependencies:
- scikit-learn
# for python 3.7 compatible environment use
# tiffile >2020.9.22,<=2021.11.2
- tifffile
- tifffile 2023*
# build 1.11.1=*_1028 on cf is the first to be compatible with numpy>1.19
# need to bump this manually until there is a true version bump in vigra
- vigra 1.11.1=*_1033
- vigra 1.11.2*
# xarray versions not compatible with numpy 1.21, 2023.08.0 might be, but lost trust
# 2023.10.1 correctly pins numpy to 1.22 and up
- xarray !=2023.8.0,!=2023.9.0,!=2023.10.0
- z5py

# Neural Network Workflow dependencies
# can be changed to request gpu versions
- pytorch 1.13.*
- pytorch 2*
- cpuonly # comment out for pytorch with cuda
# mamba does not "respect" track_features, which is the idea behind cpuonly,
# with ilastik-pytorch-version-helper-cpu we help mamba on linux and windows
Expand Down