Maximilian Hoffmann

Ok, sorry, I thought this would be the appropriate place, because it's also general question about the mathematics/implementation of the displacement transform, which probably is ITK. I don't expect it to be a bug.

I currently initialise a displacement transform from a numpy array. Do I get that right, that in principle effects of this transform should be more or less confined to a local environments within the limits of ~ px-coordinate + displacement ? Because I see different results if I compare a cut out of a volume and displacement field + transform versus a cutout of the transformed whole volume + displacement field. Thank you!

Using antspy, when I supply images as numpyarrays which contain negative values I get the error above, is this expected?

Thanks!

Unfortunately I forgot, as I was trying multiple things, but it happens fairly often: i.e. here Default paths used: RAW_DIR = /fast/groups/ag_judkewitz/scratch/xraw/ PROC_DIR = /fast/groups/ag_judkewitz/scratch/xprocessed/ RES_DIR = /fast/groups/ag_judkewitz/work/xresults/ JOBS_DIR = /fast/groups/ag_judkewitz/scratch/jobs LIBS_DIR = /fast/users/jhenning_c/work/img/libs/opm_imaging CAL_DIR = /fast/groups/ag_judkewitz/work/opm_calibration/ b'All_Command_lines_OK Using single precision for computations....

I increased the convergence window size and decreased the convergence value, to see what will change. The volumes are fairly well aligned to begin with, i.e. the rigid translation is not more than 20 px or so as estimated by a 3d xcorr. b'All_Command_lines_OK Using single precision for computations. ============================================================================= The composite transform comprises the following transforms (in order): 1. Center of mass alignment using fixed image: 0x55e30a312f90...

Maybe someone here can help me: My convergence value is mostly reported as Inf, allthough the actual metric is not changing much. What exactly does that mean, and what should I change? Thank you