{"id":8814,"date":"2018-11-08T04:42:06","date_gmt":"2018-11-08T14:42:06","guid":{"rendered":"http:\/\/www.eaobservatory.org\/jcmt\/?p=8814"},"modified":"2020-12-29T11:02:58","modified_gmt":"2020-12-29T21:02:58","slug":"pol-2-beware-of-using-mapvaryes-at-step-1","status":"publish","type":"post","link":"https:\/\/www.eaobservatory.org\/jcmt\/2018\/11\/pol-2-beware-of-using-mapvaryes-at-step-1\/","title":{"rendered":"POL-2: Beware of using ‘mapvar=yes’ at ‘step 1’"},"content":{"rendered":"

Summary<\/strong>: Do not use mapvar=yes<\/span>\u00a0on step 1 of a POL-2 reduction as it can cause negative bowling around bright sources in the I map created at step 2.<\/p>\n

Production of polarisation maps from POL-2 data is usually performed using the pol2map<\/span> command within the Starlink SMURF package, as described in the\u00a0POL-2 Data Reduction cookbook – SC22<\/a>. An option is available to create the final I, Q and U variances based on the spread of pixel values in a set of maps created from different individual observations. This option is selected by running\u00a0pol2map<\/span> with the parameter setting mapvar=yes<\/span>. Without this option, output variances are calculated using simple error propagation from the variance values stored within the maps made from individual observations.<\/p>\n

\"\"<\/a><\/p>\n

When creating POL-2 polarisation maps, it is usual first to run pol2map<\/span> in ”auto-masking” mode to create an initial map of total intensity (I). This initial map is used simply to define a mask outlining the areas on the sky where bright emission is expected. This mask is then used in subsequent runs of pol2map to (amongst other things) exclude bright bolometer samples from the estimation of the COM, PCA and FLT background levels – including bright samples would bias these estimates.\u00a0The first run of pol2map<\/span> is usually referred to as “step 1”, with subsequent runs being “step 2” and “step 3”.\u00a0 The I map created by step 1 is first converted from total intensity (in pW) into a map of signal-to-noise ratio (SNR). This is done by dividing the pixel data values by the square root of the pixel variance values. This SNR map is then thresholded at a specific value to define the mask containing the source areas.<\/p>\n

But the size of the pixel variance values, and consequently the SNR values and the resulting mask,\u00a0 depends on whether the mapvar=yes<\/span> option was used when running pol2map. <\/span> In general, using mapvar=yes\u00a0<\/span>causes the variances to be higher, meaning that the SNR values are lower. So there are fewer source pixels above the SNR threshold value. Thus, the mask is less effective at excluding bright bolometer samples from the various background estimates. This means the background is over estimated in the vicinity of bright sources, resulting in negative bowling around bright sources when the background is removed.\u00a0 For obvious reasons this effect is worse for brighter sources than for weaker sources.<\/p>\n

Below are examples of the the externally masked I map created at step 2, based on step 1 I maps created using mapvar=yes<\/span>\u00a0(left) and mapvar=no<\/span>\u00a0(right). The negative bowling in the centre of the left image is obvious (images provided by Kate Pattle).<\/p>\n

\"\"<\/a>\"\"<\/a><\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: Do not use mapvar=yes\u00a0on step 1 of a POL-2 reduction as it can cause negative bowling around bright sources in the I map created at step 2. Production of polarisation maps from POL-2 data is usually performed using the pol2map command within the Starlink SMURF package, as described in\u2026 Continue reading<\/a><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[36],"tags":[37],"_links":{"self":[{"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/posts\/8814"}],"collection":[{"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/comments?post=8814"}],"version-history":[{"count":13,"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/posts\/8814\/revisions"}],"predecessor-version":[{"id":8893,"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/posts\/8814\/revisions\/8893"}],"wp:attachment":[{"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/media?parent=8814"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/categories?post=8814"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/tags?post=8814"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}