Adam Ginsburg added pyflagger to software  about 11 years ago

Commit id: 21d0bc7e10b05ea37759da4079d4a6a5e938fbaa

deletions | additions      

       

allowed some signal-processing features to be added to the BGPS pipeline that  could not be included in the original Bolocam pipeline.   \subsection{Pyflagger}  \url{http://agpy.googlecode.com/svn/trunk/agpy/pyflagger.py}\\  Pyflagger was originally intended as an interactive data-flagger for Bolocam  data, and was used as such, but it ended up being a complete data visualization  tool as well, implementing nearly the entire pipeline process within itself so  that each step could be easily visualized. Much of the pipeline debugging and  methodology development was performed using pyflagger. The interactive  flagging involves key and mouse commands to the \texttt{matplotlib} GUI.  Pyflagger uses the \texttt{idlsave} package to read IDL save files.  \section{PySpecKit}  \url{http://pyspeckit.readthedocs.org/} \\  PySpecKit was written in collaboration with Jordan Mirocha \citep{Ginsburg2011c}.         

emission peaks are observed at 500 \um or 1.1 mm. This is an indication that  any star formation, if present, is weak - no clusters are presently forming  from this cloud. It resembles, in that respect, the California molecular  cloud. However, it is much smaller, with $M\approx8.3\ee{3}\pm3.2\ee{3} \msun$  compared to California's $\sim10^5$.  \Figure{figures_chH2CO/W49_RGB_aplpy.png} \Figure{figures_chH2CO/W49_RGB_40kms_aplpy.png}  {The G43 40 \kms cloud. The background image shows Herschel SPIRE 70 \um (red),  Spitzer MIPS 24 \um (green), and Spitzer IRAC 8 \um (blue) in the background with  the \thirteenco integrated image from $v=36 \kms$ to $v=43 \kms$ at contour levels of