Warpy v0.5.0 - Compatible with QuPath 0.7

This extension can be installed via the PTBIOP Catalog (https://github.com/BIOP/qupath-biop-catalog).
It will automatically install optional depencies.

Running headless is now possible.

Warpy v0.4.2 - Compatible with QuPath 0.6

This extension can be installed via the PTBIOP Catalog (https://github.com/BIOP/qupath-biop-catalog).
It will automatically install optional depencies.

Besides QuPath 0.6 compatibility, this version introduces the possibility to compute on a downscaled grid the deformation field, cache it and interpolate it. This can bring drastic performance improvements for spline transformations with many landmarks ( above 100 )

QuPath 0.6.0 Compatibility, error management, and object names and IDs

New version to work with QuPath 0.6.0

This makes it incompatible with versions before 0.6.0

Names now included when transforming objects
IDs included when transforming objects

Tries to be smarter about errors. When one child object fails, then the rest will still try to go through

This is a pre-release version. We will release the final version compatible with QuPath 0.6.0 when that is out, and based on feedback and issues reported here and on the ImageSC forum.

0.3.1 - adapts to BigWarp version 9

BigWarp has been updated and this requires the addition of a new class support, named InvertibleWrapped2DTransformAs3D.

Full Changelog: 0.3.0...0.3.1

0.3.0 - QuPath 0.5.0 compatibility

This version is the updated extension for QuPath 0.5.0, no additional functionality.

0.2.7 released: huge performance improvement for affine transformed images > 2GPixels

This version solves an issue which made Warpy use too much RAM for images above 2Gpixels, when transformed in an affine manner.

0.2.6 released: huge performance improvement for images > 2GPixels

This version solves an issue which made Warpy use too much RAM for images above 2Gpixels.

Warpy Support for annotation names and TMAs

Following #9 , we added the possibility to transfer TMAs as well, Note that the workflow is a bit different because of the way TMAs are handled. You can see the following script for an idea on how to do it.

https://github.com/BIOP/qupath-scripts/blob/main/Extensions/Warpy/Warpy_transfer_objects.groovy

v0.2.4 for QuPath v0.4+

Unzip jars files contained in the zip files then drag and drop them into QuPath 0.4+

Includes: bug fix that was preventing the image transformation (affine, real) to be applied in QuPath with Image Combiner Warpy.

v0.2.0 for QuPath v0.3

Unzip jars files contained in the zip files then drag and drop them into QuPath 0.3+