Fixed a special case where the obliteration of 32 s windows into windows of up to 512+32 s long caused the final window to extend into another frame, which constructWhitespace had not prepared for. To minimize intrusion into other parts of the code, an edit was made directly to the failure point in the HoftEditor windower function, where the frameTail is attached; the Hoft.data and Hoft.baseline structures are extended by the required amount, which is exactly the length of the frameTail. A variety of checks are made the ensure this only occurs where needed and that it survives in cases where the window needs to be renormalized due to vetoes. All checks out with one test case, and since the entire category of so-called type 1 errors in the 2013-01-22-1 LHO and 2013-02-21 LLO production runs were similar across all the variables that are invoked, I think it is safe to say this should solve the problem for all errors involving loopPRC. Note that loopMICH and initialMICH, also known as type 0 and type 2 errors, are due to issues with 64 and 96 s LDAS frames sneaking into ligo_data_find and the cluster nodes, and I cannot resolve those without extensive recoding, so I think I will ignore them and just write over those jobs with interstitialFrame.m