I recently went out and captured about 130 320-megapixel HDR 360 panoramas. Each panorama consists of about 4.25 GB of raw files from a Sony a7r II and takes nearly an hour to detect and render on a Windows machine running an 10-core Intel Core i7-6950X overclocked to 4.2Ghz and a Titan X GPU--about 5 days of continuous rendering (using Kolor Autopano Giga).
I'm willing to leave my machine on for 5 days to do this sort of rendering, especially when it's cold outside, as I'd have to run a heater in the room if I wasn't doing this sort of rendering, anyway (hah), but long rendering sessions like this require software that can essentially remain running continuously forever. Autopano Giga is stable and will run for long periods of time, but it consumes a huge amount of temporary disk space when detecting and rendering, especially when working with raw images, which must be decoded, converted, and stored to disk. In my specific project, each detection or render requires 16GB of temporary disk space. It's cleared when Autopano closes, but my 130 panoramas would require about 2TB of temporary disk space to detect or render (!). Because Autopano doesn't have an option to clear temporary disk space for each pano after completing a task (presumably, so you can continue to work on each panorama without having to do a full raw conversion again), you need to have this sort of disk space free in your temporary folders to successfully do batch operations in Autopano. Luckily, Autopano supports up to 3 temporary folders; in theory, it should be easy to find enough disk space to run.
This is great in theory, but I've come back from long batch operations to a crashed program even when giving the program plenty of extra temporary storage, and I was unable to run long batch operations without breaking them up into smaller units. Autopano isn't really made for setting up many panoramas at once, so this is a painful process.
I finally settled on using Task Scheduler in Windows 10 to periodically run a batch file that deletes all folders older than 90 minutes. I used the process outlined in this article at StackOverflow. The batch file uses FileTimeFilerJS.bat. DO THIS AT YOUR OWN RISK, and test on non-critical data!
@echo off for /f "tokens=* delims=" %%# in ('c:\path\to\FileTimeFilerJS.bat "z:\cache-autopano" -mm -90 -show dirs -direction before') do ( echo deleting "%%~f#" rmdir "%%~f#" /q /s )
Change "c:\path\to\FileTimeFilerJS.bat" to wherever it is located on your machine, and "z:\cache-autopano" to your temporary folder location.
Go to Control Panel -> Schedule Tasks to launch Task Scheduler. Create a new task that runs your new batch file at any interval you'd like.
Note that each time your task runs, you'll see a command window flash up on the screen briefly. This window will steal input focus, so if you're typing something, you'll be interrupted. I'm sure there's a way to fix this, but I haven't looked into it. I'm just happy that I can walk away from my machine now for many hours and know that Autopano won't crash due to full temporary folders.
I'm told that I could also use a command-line interface to drive AutoPano giga, which might also solve some of these problems, but I haven't looked into it. Finally, the Autopano projects and batch lists are just text files and are easy to edit. I'm finding myself manually editing the project files when I move from machine to machine, or need to change settings in multiple projects at once (e.g., switching from absolute to relative file locations).