In order to see if the loops we identified are truly loops, the 'locate_bresenham_slit' procedure tags the supposed loops on the full image. To run this, I had to go back to my homemade stack plot procedure because in the original slit extraction procedure there was a byproduct file created that I needed to replicate.
Issues arose from recreating this file. I thought 'phi' 'thick' and 'l0' came from the repointing that happened with TRACE data (from locate_bresenham_slit) and thus set them as 0. As a result, the slit didn't show up on the image and neither did the loop tags. It turns out, 'phi' could still be 0 because it is the angle of inclination of the slit and ours was horizontal. BUT l0 was not a Carrington longitude, but was the length of the slit still on the frame. Thick was the height of the slit, which for us was 5px. This made the slit show up.
At the tail of week 8, I analyzed my data set #1 and began downloading case #2 from Feb 17, 2011.