| Date: | 2011-02-03 04:50 |
|---|---|
| Author: | Adam (adam.g.ginsburg@gmail.com) |
| tags: | googlepost, pipeline, deline |
| slug: | some-pretty-neat-things-about-delining |
Well, I did the work, so might as well come up with some plots... I created a gaussian-fitting based delining code that saves all of the fits in a text file! That's a lot of data to play with, and allows me to draw some conclusions:
- For the narrow lines, the linewidth (gaussian sigma) is 0.03 Hz. For the wide lines, it is 0.05.
- The amplitudes from December 2010 are ENORMOUS compared to others!
- The width distributions of the two are similar, though the lines appear to be significantly wider in July 2009
I've also gotten to the point that I'm satisfied with how delining with wing suppression works. Wing suppression is 0.4-2x quicker than fitting directly, depending on... not clear what exactly; it depends on epoch, but that could either be because there are more lines found or because of relative data size. Does delining have to be done on whole timestreams, or can it be done on a scan-by-scan basis? This is not entirely clear... the peaks are less suppressed when done on a scan-by-scan basis (presumably because the S/N is low and peaks are therefore not detected), but incorrect suppression (removing a line that's not there) is reduced. For short scans, the scan-by-scan approach is 10x faster; for longer scans it's ~20% faster. I think the scan-by-scan approach is going to be ideal.
Examples from l089 (0709): Top row: non-fitted line suppression
Bottom row: fitted line suppression
Examples from Uranus (1012, really really liney):
Top row: non-fitted line suppression
Bottom row: fitted line suppression
