Lacosmicx

I have finished the optimized LA Cosmic implementation. It uses Cython for the main part of the algorithm and uses C for the individual routines. Everything is multithreaded using OpenMP (the Cython standard). For a 4K x 2K image, this implementation is ~35 times faster than cosmics.py written by Malte Tewes (which is already significantly faster than the original IRAF version). 

Given the complexity of this code, should this be included in imageutils or should it be its own package? 

Any other comments are welcome.
Currently, I only expose a single function to the end user (currently named run), but should I expose more of the functionality? I have stayed away from this because the functions are designed specifically for lacosmicx. What do you think? If I stay with the current scheme, would a call structure like "imageutil.lacosmicx.run" be acceptable, without a top level run function? Otherwise, is run_lacosmicx() acceptable?