-bash-3.00$ du -h --max-depth=1 ../16K ../lost+found80G ../sliced1.3G ../elatov70G ../cleaned58G ../mapped179G ../sliced_polychrome4.0K ../ironsides49G ../coadd_mapped2.1G ../pca_coadd2.8G ../3pca_3iterations11M ../centroid17M ../lost34M ../ptg_maps3.8G ../montage31G ../maps_from_polychrome93M ../ptg_mmd32G ../backup_from_kilauea31G ../sharc1.8M ../distortion6.9G ../fake138G ../adam_work136G ../bgps_dir_from_polychrome815G ../
Articles in the bgps category
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.
Defining Pointing Terminology
There has been a lot of confusion about pointing terminology.
CSO pointing model: the telescope pointing model used and written as a black box
- has already been corrected for aberration/nutation
- is in current epoch coordinates (e.g. J2007.34)
Instrument-specific correction to pointing model
- ??? also referred to as 't terms'
- is offset between CSO pointing model and real locations
- should be a function of alt (and maybe az)
- is recorded in "RPC" files
- is in units of distance on the sky: delta-RA and delta-DEC, or delta-ALT and delta-AZ will be in the same units, while if they were in coordinate units delta-RA and delta-AZ would have to be scaled by 1/cos(DEC) or 1/cos(ALT) respectively
FAZO and FZAO: Fixed Azimuth Offset and Fixed Zenith Angle Offset
- these are ambiguously defined in the pipeline code
- ???? FAZO/FZAO include both the functional instrument specific pointing offset and any manual changes made at the telescope [manual only relevant to 2007 observations]
- ???? or are these JUST fixed offsets, and the instrument specific corrections are not included? Either way, how can I separate out manually-applied fixed offsets from fitted-model offsets?
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
BOLOCAM PIPELINE BLOG
Guy pointed out in the CU meeting today that we need a better way to keep track of changes / problems / etc. The wiki's kind of a pain, and this will serve as something of a replacement for the e-mail-only conversations that have been going on with the Software Power Team.
« Page 20 / 20