On my huge Cygnus run, the fft keeps failing in the deline code. It's actually pretty impressive, but there are 844604 points in the timestream. The prime factorization of 844604 is 2^2 * 211151. This is just damned bad luck, because I think an FFT is extremely inefficient when it can't factorize. What's the best workaround? .... 9 AM update: I've rewritten the deliner to work on a scan-by-scan basis. It's possible that the delining failed in the past because it was essentially removing a constant amplitude at the line frequencies across the observation (or combined observations!) which is not likely to be true.
Looking back at the old pipeline
I've obviously missed something. So to try to figure out what it is, I'm going back to the old pipeline... again... in map_ncdf_reading, lines 441-448, there is something curious that goes back to a definition-of-variables problem: ddec and dra are ADDED to ra and dec to get the new "ra_all" and "dec_all" variables. ddec and dra are calculated from eaz and eel: ERROR OFFSETS in Az and El. Why? What?! I added a new piece of code, correct_eaz_eel.pro. It is extremely short, but extremely necessary.
pro correct_eaz_eel,ra,dec,el,az,eel,eaz,pa dra=-eaz*cos(!dtor*pa)*cos(!dtor*el)+eel*sin(!dtor*pa) ddec=eaz*sin(!dtor*pa)*cos(!dtor*el)+eel*cos(!dtor*pa) dec += ddec/3600. ra += dra/3600. / cos(!dtor*dec) / 15.end
This comes back to the fact that I don't know what ANY of the variables in the NCDF header are supposed to be. Why are "error" variables actually OFFSET variables, and why didn't anyone know about them?
Nothing
No progress today. Spent the whole day re-mapping pointing sources and figuring out which observations ARE pointing sources. Mapping STILL not done - it takes a long time when there are hundreds of separate observations. Also, finding some corrupt files and noting them in /scratch/adam_work/texts/toolarge.txt . A lot more of that work to be done.
Galactic vs. RA mapping
They don't match up. This is a serious problem. I think it's only a problem for the GC: ad2xy refuses to map things right around that transition. I think it's OK elsewhere.
New Pipeline to CVS
Open topic - what needs to be done to put the new pipeline on the CVS?
- Under the assumption that it will be used by others, the documentation needs to be complete.
- Needs to be compatible with current pipeline (no name overlap)
- Have to fix / update some Goddard astrolib routines that have short integer for loops and need long integer for loops Which ones?
- Probably need to add instrument specific pointing model corrections for non-BGPS observations
« Page 5 / 5