Slabbing is a technique for making it easier to work with stacks that contain large numbers of images. The concept of slabbing is that you split your stacking into two big steps. In the first big step you might reduce say 200 original source images to 30 intermediate images, by stacking sets of 10-15 photos each, with some overlap between sets. Then in the second big step you stack the 30 intermediate images, the “slab outputs”, to produce an image with the full stack combined.
When you retouch with slabbing, typically you only have to reach back to the intermediate images (the slab outputs), instead of all the way back to each of the original source images. In the example, that means retouching from a set of only 30 images instead of 200.
Slabbing can also be very helpful if you need to explore a variety of settings for the DMap parameters. In this scenario you would generate the slab outputs using the PMax stacking method, then stack the slabs using DMap. The gain here is much faster computation for the stacking, because DMap only needs to work with the much smaller number of slab outputs, instead of all the original source images individually.
Historically, slabbing has been accomplished by using some third-party program to generate a batch script to control the slabbing. Examples of such programs include ZereneVS, Slabberjockey, BugSlabber, and MakeSubStackingScript. Those worked great for a long time, but recent improvements in Apple's macOS security have had the unfortunate side effect of making the third-party programs difficult or impossible to use on Mac computers.
So, the current production build of Zerene Stacker now provides slabbing as a built-in function.
In more detail, here is one possible workflow with slabbing:
The default values of 10 frames per slab and 3 frames overlap mean that the first slab will be frames 0-9, the second will be 7-16, the third will be 14-23, and so on, where frame 0 means the first frame in the Input Files list after alignment has been done. In the Batch dialog, you can select a Task, click the Details button, and scroll down to confirm the Selected Input Indices near the bottom of the Task Details list.
One caution: if you interrupt the batch script while slabbing is being done, then the output image saving parameters may be left as they were for slabbing, not restored to their values used for normal stacking. This is most likely observed by the naming template left as something like “Slab {outseq} PMax”, rather than its default value of “{datetime} ZS {method}” or whatever else you had it set to. This can result in some confusion, as then subsequent normal outputs will be named as if they were slabs. This behavior is on the list of bugs to be fixed in a subsequent release. Until that happens, please check and reset the value of the output naming template if you need to interrupt the slabbing process. It is located at Options > Preferences > Image Saving > Template. The other file saving parameters, such as file type, compression level (for JPEG), and bit depth and compression type (for TIFF) may also be left set incorrectly.