A new plugin system type was introduced to handle plugins which only operated on a catalog, after all "measurement" plugins had been successfully run. At the time the term afterburner was used as a way to describe a system that was optionally run after other measurements. However in the processing pipeline there may be many other steps after a catalog has been created and measurements have been made. As such I propose we rename the catalog level afterburner plugin system to CatalogCalculation plugin system to better clarify its purpose and to leave the term 'afterburner' free to be used in the context of something that may be run outside the context of normal processing flow.