TissueFAXS scans a region one FOV at a time, moving the stage between frames. Neighboring FOVs overlap so that stitchingLoading... can correct stage errors: its BF/FL Image matching method finds the pixel shift between each pair of neighbors. TissueFAXS recommends an overlap of at least 15%, set as Width/Height Overlap in percent or in pixels. The FOV's physical size comes from Calibrate Field of View, done for each objective.
StrataQuest keeps that structure. It doesn't copy the images; it shows and analyzes the original virtual slideLoading.... Running an engine usually means analyzing each FOV of the sample or ROI, typically in parallel and in no fixed order, and image results are stored per FOV: 10 FOVs and 2 image outputs give 2 sets of 10 images. Some engines, such as Tissue DetectionLoading..., work from an image in the cache instead, and their outputs are projected back onto the FOVs.
Two mechanisms deal with FOV edges. Border Input, an option of the Basic Operations Module and of detection engines such as NucleiLoading..., adds a border of pixels from the neighboring FOVs, Border Size pixels wide, so a filter or detector works on continuous data. Object stitching is a step after Detection in every layer set to stitch objects, which is the default. It matches the local labels along FOV borders into global labels, so a nucleus cut by a border becomes one event in the coded imageLoading... data.
Source: StrataQuest 8.1 User Manual §11.1 (pp. 149–151), §9.6 (p. 144), p. 18; Engines Reference ch. 6 (pp. 19–21), ch. 14–15 (pp. 405–410), ch. 26 (p. 452), ch. 33 (p. 480), ch. 41 (p. 538), ch. 44 (p. 550); TissueFAXS 8.1 User Manual §5.1.3.2 (pp. 174–176), §6.2.1 (pp. 209–215).