John Cupitt

I think those tests are trying to allow very small but still positive resolutions. I remember we used to have zero res in output file sometimes, and it caused a...

> nifti->nim->dx = 1.0 / image->Xres; That's a common thing in downstream code working with eg. slide output, where resolution is usually expressed as microns per pixel.

Hello @huangjin520, You can't use debian packages within conda. I would use the libvips in conda, or use the python from debian, but not both. In my opinion, conda is...

Hi @Tommy-Glasgow, We've just (earlier today) pushed out pyvips 3.0. This new version downloads the correct libvips binary for you, so it's really easy to install. It supports Linux (musl...

Actually, what you've done might be working. You wrote: > When I go into python and test if it has dzsave it doesn't so I get errors trying to use...

> Installing was successful but trying the python code gave me this error: It only downloads the libvips binary if it can't find a system binary. I'd guess it's picking...

> Similarily trying to use tiffsave with the pyramidal option outputs an image but it doesn't seem to be pyramidal. It should be -- perhaps you are expecting an OME-style...

> I'm not sure if this is related but I originally had libvips without libarchive and later made a version with it and pyramidal support. Yes, it sounds like you...

You'll probably need to split the bands and add some XML metadata. Did you see the threads on `image.sc` about this? Eg.: https://forum.image.sc/t/writing-qupath-bio-formats-compatible-pyramidal-image-with-libvips/51223/13

This is the `vips2ome.py` I normally use: ```python #!/usr/bin/env python3 import sys import pyvips im = pyvips.Image.new_from_file(sys.argv[1]) num_channels = im.bands image_height = im.height # split to separate image planes and...