Tips on Runcutting

It is important to take time to think about the option you are selecting when instructing BlockBuster to perform a type of runcut.

For instance, if, while incrementally improving a runcut, you choose the Cut from Scratch option although you intended to leave the Recut Existing Runs option selected by default, the system cuts from scratch and abandons the incremental improvements you have achieved up to that point. While you can still access a replica of the saved version on which you based your scenario (you should be saving all scenarios yielding improvements and building on them in successive scenarios, hence, the term incremental runcutting), taking the time and being aware of the type of cut that you are making ultimately saves you time and effort.

A significant difference between recutting existing runs and the cutting from scratch option lies in how the algorithms within BlockBuster use parameters. When BlockBuster processes uncut runs, it classifies them all as undesirable/illegal because they are in the uncut state. Therefore, when cutting from scratch, the system uses the information defined in the parameters associated with the Undesirable run types to produce a runcut. Note that this is the opposite strategy to the one employed when recutting existing runs. When recutting existing runs, the system uses the parameters associated with legal run types to produce a runcut.