Hi, Gavin, Gregory, All, We've been seeing some behavior from SISCone at CMS whereas we have too many input towers to the algorithm, such that it takes seconds to process an event (which is too long). At the present time, we're planning on implementing a "hard cut" on the number of input towers, however we were wondering if there was a more graceful way that the SISCone plugin to fastjet can be told to stop processing if it is taking too long? Thanks, Sal