https://mocks.cita.utoronto.ca/api.php?action=feedcontributions&feedformat=atom&user=Mlokken 2026-08-16T22:56:22Z User contributions MediaWiki 1.35.5 https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2079 2020-01-13T22:40:45Z

<p>Mlokken: /* Status update on the mocks */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below. These tend to peak 5-10 Mpc away from the center and then drop off further away. The peak values vary, which is probably due mostly to the variation in number of clusters included in each slice.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Ellipticity parameter ==<br /> After a fix with the definition of the ellipticity in COOP, about half of the cluster locations in the number density map have 0 &lt; e &lt; 1. The others are mostly within 1 and 10. There's a note in COOP that on saddle points, e can be &gt; 1, so the clusters for which e&gt;1 must be offset from peaks in the number density map. After some trial and error, I settled on an upper limit of e &lt; 2 because it seems to best enhance the oriented signal. I believe it's cutting out some of the clusters which are in more isolated regions of the map, which is useful. The same result might be better achieved by implementing a cut on the overdensity of the map at that point (as in, only clusters in denser regions would be included; I believe this is called 'nu' in the code). In the stacks shown in this post, I was using 0 &lt; e &lt; 2 and not implementing a lower limit. However, the e parameter should ideally be used for selecting on more elongated regions, which would mean raising the lower limit to something between 0 and 1. I will play around with finding the best value to enhance the oriented signal without eliminating too many clusters.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png | 600px]]<br /> <br /> The inclusion of Redmagic galaxies may not seem to make a major difference based on the above comparison, but when comparing the stacks, it's clear that they are needed. Remaking the combined stack shown as the 5th plot in this post with only CMASS galaxies for orientation yields the following image.<br /> <br /> [[File:1032 to 2032 Mpc stacked cmass 17pt8Mpc smth hess 5965cls.png | 400px]]<br /> This is clearly worse than the version which also uses Redmagic galaxies to orient.<br /> <br /> == Status update on the mocks ==<br /> With the current run of Peak Patch which I've been using, there appears to be too many high-mass halos in comparison with the clusters in RedMaPPer. When limiting the Peak Patch catalog and RedMaPPer catalog to the same region (ACT deep56), for each redshift slice I select all the RedMaPPer clusters with lambda (richness) &gt; 7. I select the same number of the most massive Peak Patch halos in that slice + region. I then convert each cluster's richness to halo mass using the relation in [[https://arxiv.org/pdf/1805.00039.pdf]] (&quot;Dark Energy Survey Year 1 results: weak lensing mass calibration of redMaPPer galaxy clusters&quot; McClinctock et al. 2019). Comparing the samples in every redshift slice always shows the Peak Patch halos at higher masses, e.g. the below graph (y-axis is shared):<br /> <br /> [[File:Mass comparison pp rm cls 1432 1632.png | 600 px]]<br /> <br /> This is probably attributable to the higher value of sigma-8 in the Planck CMB results than DES. This run of Peak Patch was done with Planck cosmological parameters, so I should do another run of the simulation with the DES value of sigma 8 to see how the samples compare.<br /> <br /> After the new simulation run is done, I'll dive into mocking Redmagic galaxies with Peak Patch. I plan to do that with the HOD rather than just with approximate halo mass matching as I was doing previously for CMASS.</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2078 2020-01-13T22:39:22Z

<p>Mlokken: /* Importance of including Redmagic galaxies */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below. These tend to peak 5-10 Mpc away from the center and then drop off further away. The peak values vary, which is probably due mostly to the variation in number of clusters included in each slice.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Ellipticity parameter ==<br /> After a fix with the definition of the ellipticity in COOP, about half of the cluster locations in the number density map have 0 &lt; e &lt; 1. The others are mostly within 1 and 10. There's a note in COOP that on saddle points, e can be &gt; 1, so the clusters for which e&gt;1 must be offset from peaks in the number density map. After some trial and error, I settled on an upper limit of e &lt; 2 because it seems to best enhance the oriented signal. I believe it's cutting out some of the clusters which are in more isolated regions of the map, which is useful. The same result might be better achieved by implementing a cut on the overdensity of the map at that point (as in, only clusters in denser regions would be included; I believe this is called 'nu' in the code). In the stacks shown in this post, I was using 0 &lt; e &lt; 2 and not implementing a lower limit. However, the e parameter should ideally be used for selecting on more elongated regions, which would mean raising the lower limit to something between 0 and 1. I will play around with finding the best value to enhance the oriented signal without eliminating too many clusters.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png | 600px]]<br /> <br /> The inclusion of Redmagic galaxies may not seem to make a major difference based on the above comparison, but when comparing the stacks, it's clear that they are needed. Remaking the combined stack shown as the 5th plot in this post with only CMASS galaxies for orientation yields the following image.<br /> <br /> [[File:1032 to 2032 Mpc stacked cmass 17pt8Mpc smth hess 5965cls.png | 400px]]<br /> This is clearly worse than the version which also uses Redmagic galaxies to orient.<br /> <br /> == Status update on the mocks ==<br /> With the current run of Peak Patch which I've been using, there appears to be too many high-mass halos in comparison with the clusters in RedMaPPer. When limiting the Peak Patch catalog and RedMaPPer catalog to the same region (ACT deep56), for each redshift slice I select all the RedMaPPer clusters with lambda (richness) &gt; 7. I select the same number of the most massive Peak Patch halos in that slice + region. I then convert each cluster's richness to halo mass using the relation in [[https://arxiv.org/pdf/1805.00039.pdf]] (&quot;Dark Energy Survey Year 1 results: weak lensing mass calibration of redMaPPer galaxy clusters&quot; McClinctock et al. 2019). Comparing the samples in every redshift slice always shows the Peak Patch halos at higher masses, e.g. the below graph (y-axis is shared):<br /> <br /> [[File:Mass comparison pp rm cls 1432 1632.png | 600 px]]<br /> <br /> This is probably attributable to the higher value of sigma-8 in the Planck CMB results than DES. This run of Peak Patch was done with Planck cosmological parameters, so I should do another run of the simulation with the DES value of sigma 8 to see how the samples compare then.<br /> <br /> After the new simulation run is done, I'll dive into mocking Redmagic galaxies with Peak Patch. I plan to do that with the HOD rather than just with approximate halo mass matching as I was doing previously for CMASS.</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2077 2020-01-13T22:36:53Z

<p>Mlokken: /* Ellipticity parameter */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below. These tend to peak 5-10 Mpc away from the center and then drop off further away. The peak values vary, which is probably due mostly to the variation in number of clusters included in each slice.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Ellipticity parameter ==<br /> After a fix with the definition of the ellipticity in COOP, about half of the cluster locations in the number density map have 0 &lt; e &lt; 1. The others are mostly within 1 and 10. There's a note in COOP that on saddle points, e can be &gt; 1, so the clusters for which e&gt;1 must be offset from peaks in the number density map. After some trial and error, I settled on an upper limit of e &lt; 2 because it seems to best enhance the oriented signal. I believe it's cutting out some of the clusters which are in more isolated regions of the map, which is useful. The same result might be better achieved by implementing a cut on the overdensity of the map at that point (as in, only clusters in denser regions would be included; I believe this is called 'nu' in the code). In the stacks shown in this post, I was using 0 &lt; e &lt; 2 and not implementing a lower limit. However, the e parameter should ideally be used for selecting on more elongated regions, which would mean raising the lower limit to something between 0 and 1. I will play around with finding the best value to enhance the oriented signal without eliminating too many clusters.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png | 600px]]<br /> <br /> The inclusion of Redmagic galaxies may not seem to make a major difference based on the above comparison, but when comparing the stacks, it's clear that they are needed. Remaking the combined stack shown as the 5th plot in this post with only CMASS galaxies for orientation yields the following image.<br /> <br /> [[File:1032 to 2032 Mpc stacked cmass 17pt8Mpc smth hess 5965cls.png | 400px]]<br /> This is clearly worse than the version which uses Redmagic galaxies to orient.<br /> <br /> == Status update on the mocks ==<br /> With the current run of Peak Patch which I've been using, there appears to be too many high-mass halos in comparison with the clusters in RedMaPPer. When limiting the Peak Patch catalog and RedMaPPer catalog to the same region (ACT deep56), for each redshift slice I select all the RedMaPPer clusters with lambda (richness) &gt; 7. I select the same number of the most massive Peak Patch halos in that slice + region. I then convert each cluster's richness to halo mass using the relation in [[https://arxiv.org/pdf/1805.00039.pdf]] (&quot;Dark Energy Survey Year 1 results: weak lensing mass calibration of redMaPPer galaxy clusters&quot; McClinctock et al. 2019). Comparing the samples in every redshift slice always shows the Peak Patch halos at higher masses, e.g. the below graph (y-axis is shared):<br /> <br /> [[File:Mass comparison pp rm cls 1432 1632.png | 600 px]]<br /> <br /> This is probably attributable to the higher value of sigma-8 in the Planck CMB results than DES. This run of Peak Patch was done with Planck cosmological parameters, so I should do another run of the simulation with the DES value of sigma 8 to see how the samples compare then.<br /> <br /> After the new simulation run is done, I'll dive into mocking Redmagic galaxies with Peak Patch. I plan to do that with the HOD rather than just with approximate halo mass matching as I was doing previously for CMASS.</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2076 2020-01-13T22:34:23Z

<p>Mlokken: /* Ellipticity parameter */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below. These tend to peak 5-10 Mpc away from the center and then drop off further away. The peak values vary, which is probably due mostly to the variation in number of clusters included in each slice.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Ellipticity parameter ==<br /> After a fix with the definition of the ellipticity in COOP, about half of the cluster locations in the number density map have 0 &lt; e &lt; 1. The others are mostly within 1 and 10. There's a note in COOP that on saddle points, e can be &gt; 1, so the clusters for which e&gt;1 must be offset from peaks in the number density map. After some trial and error, I settled on a 0 &lt; e &lt; 2 cut because it seems to best enhance the oriented signal. I believe it's cutting out some of the clusters which are in more isolated regions of the map, which is useful. The same result might be better achieved by implementing a cut on the overdensity of the map at that point (as in, only clusters in denser regions would be included). The e parameter should ideally be used for selecting on more elongated regions, which would mean raising the lower limit to &gt;0. I will play around with finding a good lower limit next, such that not too many clusters are eliminated.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png | 600px]]<br /> <br /> The inclusion of Redmagic galaxies may not seem to make a major difference based on the above comparison, but when comparing the stacks, it's clear that they are needed. Remaking the combined stack shown as the 5th plot in this post with only CMASS galaxies for orientation yields the following image.<br /> <br /> [[File:1032 to 2032 Mpc stacked cmass 17pt8Mpc smth hess 5965cls.png | 400px]]<br /> This is clearly worse than the version which uses Redmagic galaxies to orient.<br /> <br /> == Status update on the mocks ==<br /> With the current run of Peak Patch which I've been using, there appears to be too many high-mass halos in comparison with the clusters in RedMaPPer. When limiting the Peak Patch catalog and RedMaPPer catalog to the same region (ACT deep56), for each redshift slice I select all the RedMaPPer clusters with lambda (richness) &gt; 7. I select the same number of the most massive Peak Patch halos in that slice + region. I then convert each cluster's richness to halo mass using the relation in [[https://arxiv.org/pdf/1805.00039.pdf]] (&quot;Dark Energy Survey Year 1 results: weak lensing mass calibration of redMaPPer galaxy clusters&quot; McClinctock et al. 2019). Comparing the samples in every redshift slice always shows the Peak Patch halos at higher masses, e.g. the below graph (y-axis is shared):<br /> <br /> [[File:Mass comparison pp rm cls 1432 1632.png | 600 px]]<br /> <br /> This is probably attributable to the higher value of sigma-8 in the Planck CMB results than DES. This run of Peak Patch was done with Planck cosmological parameters, so I should do another run of the simulation with the DES value of sigma 8 to see how the samples compare then.<br /> <br /> After the new simulation run is done, I'll dive into mocking Redmagic galaxies with Peak Patch. I plan to do that with the HOD rather than just with approximate halo mass matching as I was doing previously for CMASS.</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2075 2020-01-13T22:27:45Z

<p>Mlokken: /* Radial profiles and looking at changes with redshift */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below. These tend to peak 5-10 Mpc away from the center and then drop off further away. The peak values vary, which is probably due mostly to the variation in number of clusters included in each slice.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Ellipticity parameter ==<br /> After a fix with the definition of the ellipticity in COOP, about half of the cluster locations in the number density map have 0 &lt; e &lt; 1. The others are mostly within 1 and 10. There's a note in COOP that on saddle points, e can be &gt; 1, so the clusters for which e&gt;1 must be offset from peaks in the number density map. After some trial and error, I settled on a 0 &lt; e &lt; 2 cut because it seems to best enhance the oriented signal. I believe it's cutting out some of the clusters which are in more isolated regions of the map, which is useful.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png | 600px]]<br /> <br /> The inclusion of Redmagic galaxies may not seem to make a major difference based on the above comparison, but when comparing the stacks, it's clear that they are needed. Remaking the combined stack shown as the 5th plot in this post with only CMASS galaxies for orientation yields the following image.<br /> <br /> [[File:1032 to 2032 Mpc stacked cmass 17pt8Mpc smth hess 5965cls.png | 400px]]<br /> This is clearly worse than the version which uses Redmagic galaxies to orient.<br /> <br /> == Status update on the mocks ==<br /> With the current run of Peak Patch which I've been using, there appears to be too many high-mass halos in comparison with the clusters in RedMaPPer. When limiting the Peak Patch catalog and RedMaPPer catalog to the same region (ACT deep56), for each redshift slice I select all the RedMaPPer clusters with lambda (richness) &gt; 7. I select the same number of the most massive Peak Patch halos in that slice + region. I then convert each cluster's richness to halo mass using the relation in [[https://arxiv.org/pdf/1805.00039.pdf]] (&quot;Dark Energy Survey Year 1 results: weak lensing mass calibration of redMaPPer galaxy clusters&quot; McClinctock et al. 2019). Comparing the samples in every redshift slice always shows the Peak Patch halos at higher masses, e.g. the below graph (y-axis is shared):<br /> <br /> [[File:Mass comparison pp rm cls 1432 1632.png | 600 px]]<br /> <br /> This is probably attributable to the higher value of sigma-8 in the Planck CMB results than DES. This run of Peak Patch was done with Planck cosmological parameters, so I should do another run of the simulation with the DES value of sigma 8 to see how the samples compare then.<br /> <br /> After the new simulation run is done, I'll dive into mocking Redmagic galaxies with Peak Patch. I plan to do that with the HOD rather than just with approximate halo mass matching as I was doing previously for CMASS.</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2074 2020-01-13T22:26:39Z

<p>Mlokken: /* Radial profiles and looking at changes with redshift */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below. These are all fairly consistent in behavior, with a rise 5-10 Mpc away from the center and then a dropoff. The peak values vary, which is probably due mostly to the variation in number of clusters included in each slice.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Ellipticity parameter ==<br /> After a fix with the definition of the ellipticity in COOP, about half of the cluster locations in the number density map have 0 &lt; e &lt; 1. The others are mostly within 1 and 10. There's a note in COOP that on saddle points, e can be &gt; 1, so the clusters for which e&gt;1 must be offset from peaks in the number density map. After some trial and error, I settled on a 0 &lt; e &lt; 2 cut because it seems to best enhance the oriented signal. I believe it's cutting out some of the clusters which are in more isolated regions of the map, which is useful.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png | 600px]]<br /> <br /> The inclusion of Redmagic galaxies may not seem to make a major difference based on the above comparison, but when comparing the stacks, it's clear that they are needed. Remaking the combined stack shown as the 5th plot in this post with only CMASS galaxies for orientation yields the following image.<br /> <br /> [[File:1032 to 2032 Mpc stacked cmass 17pt8Mpc smth hess 5965cls.png | 400px]]<br /> This is clearly worse than the version which uses Redmagic galaxies to orient.<br /> <br /> == Status update on the mocks ==<br /> With the current run of Peak Patch which I've been using, there appears to be too many high-mass halos in comparison with the clusters in RedMaPPer. When limiting the Peak Patch catalog and RedMaPPer catalog to the same region (ACT deep56), for each redshift slice I select all the RedMaPPer clusters with lambda (richness) &gt; 7. I select the same number of the most massive Peak Patch halos in that slice + region. I then convert each cluster's richness to halo mass using the relation in [[https://arxiv.org/pdf/1805.00039.pdf]] (&quot;Dark Energy Survey Year 1 results: weak lensing mass calibration of redMaPPer galaxy clusters&quot; McClinctock et al. 2019). Comparing the samples in every redshift slice always shows the Peak Patch halos at higher masses, e.g. the below graph (y-axis is shared):<br /> <br /> [[File:Mass comparison pp rm cls 1432 1632.png | 600 px]]<br /> <br /> This is probably attributable to the higher value of sigma-8 in the Planck CMB results than DES. This run of Peak Patch was done with Planck cosmological parameters, so I should do another run of the simulation with the DES value of sigma 8 to see how the samples compare then.<br /> <br /> After the new simulation run is done, I'll dive into mocking Redmagic galaxies with Peak Patch. I plan to do that with the HOD rather than just with approximate halo mass matching as I was doing previously for CMASS.</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2073 2020-01-13T22:22:20Z

<p>Mlokken: /* Ellipticity parameter */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below. These are all fairly consistent with a rise 5-10 Mpc away from the center and then a dropoff.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Ellipticity parameter ==<br /> After a fix with the definition of the ellipticity in COOP, about half of the cluster locations in the number density map have 0 &lt; e &lt; 1. The others are mostly within 1 and 10. There's a note in COOP that on saddle points, e can be &gt; 1, so the clusters for which e&gt;1 must be offset from peaks in the number density map. After some trial and error, I settled on a 0 &lt; e &lt; 2 cut because it seems to best enhance the oriented signal. I believe it's cutting out some of the clusters which are in more isolated regions of the map, which is useful.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png | 600px]]<br /> <br /> The inclusion of Redmagic galaxies may not seem to make a major difference based on the above comparison, but when comparing the stacks, it's clear that they are needed. Remaking the combined stack shown as the 5th plot in this post with only CMASS galaxies for orientation yields the following image.<br /> <br /> [[File:1032 to 2032 Mpc stacked cmass 17pt8Mpc smth hess 5965cls.png | 400px]]<br /> This is clearly worse than the version which uses Redmagic galaxies to orient.<br /> <br /> == Status update on the mocks ==<br /> With the current run of Peak Patch which I've been using, there appears to be too many high-mass halos in comparison with the clusters in RedMaPPer. When limiting the Peak Patch catalog and RedMaPPer catalog to the same region (ACT deep56), for each redshift slice I select all the RedMaPPer clusters with lambda (richness) &gt; 7. I select the same number of the most massive Peak Patch halos in that slice + region. I then convert each cluster's richness to halo mass using the relation in [[https://arxiv.org/pdf/1805.00039.pdf]] (&quot;Dark Energy Survey Year 1 results: weak lensing mass calibration of redMaPPer galaxy clusters&quot; McClinctock et al. 2019). Comparing the samples in every redshift slice always shows the Peak Patch halos at higher masses, e.g. the below graph (y-axis is shared):<br /> <br /> [[File:Mass comparison pp rm cls 1432 1632.png | 600 px]]<br /> <br /> This is probably attributable to the higher value of sigma-8 in the Planck CMB results than DES. This run of Peak Patch was done with Planck cosmological parameters, so I should do another run of the simulation with the DES value of sigma 8 to see how the samples compare then.<br /> <br /> After the new simulation run is done, I'll dive into mocking Redmagic galaxies with Peak Patch. I plan to do that with the HOD rather than just with approximate halo mass matching as I was doing previously for CMASS.</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2072 2020-01-13T22:19:29Z

<p>Mlokken: </p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below. These are all fairly consistent with a rise 5-10 Mpc away from the center and then a dropoff.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Ellipticity parameter ==<br /> After a fix with the definition of the ellipticity in COOP, about half of the cluster locations in the number density map have 0 &lt; e &lt; 1. The others are mostly within 1 and 10. There's a note in COOP that on saddle points, e can be &gt; 1, so the clusters for which e&gt;1 are probably offset from peaks in the number density map. I've been doing the 0 &lt; e &lt; 2 cut after some trial and error because it seems to enhance the oriented signal; I believe it's cutting out some of the clusters which are in more isolated regions of the map.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png | 600px]]<br /> <br /> The inclusion of Redmagic galaxies may not seem to make a major difference based on the above comparison, but when comparing the stacks, it's clear that they are needed. Remaking the combined stack shown as the 5th plot in this post with only CMASS galaxies for orientation yields the following image.<br /> <br /> [[File:1032 to 2032 Mpc stacked cmass 17pt8Mpc smth hess 5965cls.png | 400px]]<br /> This is clearly worse than the version which uses Redmagic galaxies to orient.<br /> <br /> == Status update on the mocks ==<br /> With the current run of Peak Patch which I've been using, there appears to be too many high-mass halos in comparison with the clusters in RedMaPPer. When limiting the Peak Patch catalog and RedMaPPer catalog to the same region (ACT deep56), for each redshift slice I select all the RedMaPPer clusters with lambda (richness) &gt; 7. I select the same number of the most massive Peak Patch halos in that slice + region. I then convert each cluster's richness to halo mass using the relation in [[https://arxiv.org/pdf/1805.00039.pdf]] (&quot;Dark Energy Survey Year 1 results: weak lensing mass calibration of redMaPPer galaxy clusters&quot; McClinctock et al. 2019). Comparing the samples in every redshift slice always shows the Peak Patch halos at higher masses, e.g. the below graph (y-axis is shared):<br /> <br /> [[File:Mass comparison pp rm cls 1432 1632.png | 600 px]]<br /> <br /> This is probably attributable to the higher value of sigma-8 in the Planck CMB results than DES. This run of Peak Patch was done with Planck cosmological parameters, so I should do another run of the simulation with the DES value of sigma 8 to see how the samples compare then.<br /> <br /> After the new simulation run is done, I'll dive into mocking Redmagic galaxies with Peak Patch. I plan to do that with the HOD rather than just with approximate halo mass matching as I was doing previously for CMASS.</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2071 2020-01-13T22:05:20Z

<p>Mlokken: /* Status update on the mocks */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below. These are all fairly consistent with a rise 5-10 Mpc away from the center and then a dropoff.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png | 600px]]<br /> <br /> The inclusion of Redmagic galaxies may not seem to make a major difference based on the above comparison, but when comparing the stacks, it's clear that they are needed. Remaking the combined stack shown as the 5th plot in this post with only CMASS galaxies for orientation yields the following image.<br /> <br /> [[File:1032 to 2032 Mpc stacked cmass 17pt8Mpc smth hess 5965cls.png | 400px]]<br /> This is clearly worse than the version which uses Redmagic galaxies to orient.<br /> <br /> == Status update on the mocks ==<br /> With the current run of Peak Patch which I've been using, there appears to be too many high-mass halos in comparison with the clusters in RedMaPPer. When limiting the Peak Patch catalog and RedMaPPer catalog to the same region (ACT deep56), for each redshift slice I select all the RedMaPPer clusters with lambda (richness) &gt; 7. I select the same number of the most massive Peak Patch halos in that slice + region. I then convert each cluster's richness to halo mass using the relation in [[https://arxiv.org/pdf/1805.00039.pdf]] (&quot;Dark Energy Survey Year 1 results: weak lensing mass calibration of redMaPPer galaxy clusters&quot; McClinctock et al. 2019). Comparing the samples in every redshift slice always shows the Peak Patch halos at higher masses, e.g. the below graph (y-axis is shared):<br /> <br /> [[File:Mass comparison pp rm cls 1432 1632.png | 600 px]]<br /> <br /> This is probably attributable to the higher value of sigma-8 in the Planck CMB results than DES. This run of Peak Patch was done with Planck cosmological parameters, so I should do another run of the simulation with the DES value of sigma 8 to see how the samples compare then.<br /> <br /> After the new simulation run is done, I'll dive into mocking Redmagic galaxies with Peak Patch. I plan to do that with the HOD rather than just with approximate halo mass matching as I was doing previously for CMASS.</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2070 2020-01-13T21:03:21Z

<p>Mlokken: </p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below. These are all fairly consistent with a rise 5-10 Mpc away from the center and then a dropoff.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png | 600px]]<br /> <br /> The inclusion of Redmagic galaxies may not seem to make a major difference based on the above comparison, but when comparing the stacks, it's clear that they are needed. Remaking the combined stack shown as the 5th plot in this post with only CMASS galaxies for orientation yields the following image.<br /> <br /> [[File:1032 to 2032 Mpc stacked cmass 17pt8Mpc smth hess 5965cls.png | 400px]]<br /> This is clearly worse than the version which uses Redmagic galaxies to orient.<br /> <br /> == Status update on the mocks ==<br /> With the current run of Peak Patch which I've been using, there appears to be too many high-mass halos in comparison with the clusters in RedMaPPer. When limiting the Peak Patch catalog and RedMaPPer catalog to the same region (ACT deep56), for each redshift slice I select all the RedMaPPer clusters with lambda (richness) &gt; 7. I select the same number of the most massive Peak Patch halos in that slice + region. I then convert each cluster's richness to halo mass using the relation in [[https://arxiv.org/pdf/1805.00039.pdf]] (&quot;Dark Energy Survey Year 1 results: weak lensing mass calibration of redMaPPer galaxy clusters&quot; McClinctock et al. 2019). Comparing the samples in every redshift slice always shows the Peak Patch halos at higher masses, e.g. the below graph (y-axis is shared):<br /> <br /> [[File:Mass comparison pp rm cls 1432 1632.png | 600 px]]</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2069 2020-01-13T20:56:41Z

<p>Mlokken: </p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below. These are all fairly consistent with a rise 5-10 Mpc away from the center and then a dropoff.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png | 600px]]<br /> <br /> The inclusion of Redmagic galaxies may not seem to make a major difference based on the above comparison, but when comparing the stacks, it's clear that they are needed. Remaking the combined stack shown as the 5th plot in this post with only CMASS galaxies for orientation yields the following image.<br /> <br /> [[File:1032 to 2032 Mpc stacked cmass 17pt8Mpc smth hess 5965cls.png | 400px]]<br /> This is clearly worse than the version which uses Redmagic galaxies to orient.<br /> <br /> == Status update on the mocks ==<br /> With the current run of Peak Patch which I've been using, there appears to be too many high-mass halos in comparison with the clusters in RedMaPPer. When limiting the Peak Patch catalog and RedMaPPer catalog to the same region (ACT deep56), for each redshift slice I select all the RedMaPPer clusters with lambda (richness) &gt; 7. I select the same number of the most massive Peak Patch halos in that slice + region. I then convert each cluster's richness to halo mass using the relation in [[https://arxiv.org/pdf/1805.00039.pdf]] (&quot;Dark Energy Survey Year 1 results: weak lensing mass calibration of redMaPPer galaxy clusters&quot; McClinctock et al. 2019). Comparing the samples in every redshift slice always shows the Peak Patch halos at higher masses, e.g.:<br /> <br /> [[File:Mass comparison pp rm cls 1432 1632.png]]</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=File:Mass_comparison_pp_rm_cls_1432_1632.png&diff=2068 2020-01-13T20:55:17Z

<p>Mlokken: </p> <hr /> <div></div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2067 2020-01-13T20:54:40Z

<p>Mlokken: </p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below. These are all fairly consistent with a rise 5-10 Mpc away from the center and then a dropoff.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png | 600px]]<br /> <br /> The inclusion of Redmagic galaxies may not seem to make a major difference based on the above comparison, but when comparing the stacks, it's clear that they are needed. Remaking the combined stack shown as the 5th plot in this post with only CMASS galaxies for orientation yields the following image.<br /> <br /> [[File:1032 to 2032 Mpc stacked cmass 17pt8Mpc smth hess 5965cls.png | 400px]]<br /> This is clearly worse than the version which uses Redmagic galaxies to orient.<br /> <br /> == Status update on the mocks ==<br /> With the current run of Peak Patch which I've been using, there appears to be too many high-mass halos in comparison with the clusters in RedMaPPer. When limiting the Peak Patch catalog and RedMaPPer catalog to the same region (ACT deep56), for each redshift slice I select all the RedMaPPer clusters with lambda (richness) &gt; 7. I select the same number of the most massive Peak Patch halos in that slice + region. I then convert each cluster's richness to halo mass using the relation in [[https://arxiv.org/pdf/1805.00039.pdf]] (&quot;Dark Energy Survey Year 1 results: weak lensing mass calibration of redMaPPer galaxy clusters&quot; McClinctock et al. 2019). Comparing the samples in every redshift slice always shows the Peak Patch halos at higher masses:</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2066 2020-01-13T20:46:16Z

<p>Mlokken: /* Radial profiles and looking at changes with redshift */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below. These are all fairly consistent with a rise 5-10 Mpc away from the center and then a dropoff.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png | 600px]]<br /> <br /> The inclusion of Redmagic galaxies may not seem to make a major difference based on the above comparison, but when comparing the stacks, it's clear that they are needed. Remaking the combined stack shown as the 5th plot in this post with only CMASS galaxies for orientation yields the following image.<br /> <br /> [[File:1032 to 2032 Mpc stacked cmass 17pt8Mpc smth hess 5965cls.png | 400px]]<br /> This is clearly worse than the version which uses Redmagic galaxies to orient.</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2065 2020-01-13T09:14:16Z

<p>Mlokken: </p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png | 600px]]<br /> <br /> The inclusion of Redmagic galaxies may not seem to make a major difference based on the above comparison, but when comparing the stacks, it's clear that they are needed. Remaking the combined stack shown as the 5th plot in this post with only CMASS galaxies for orientation yields the following image.<br /> <br /> [[File:1032 to 2032 Mpc stacked cmass 17pt8Mpc smth hess 5965cls.png | 400px]]<br /> This is clearly worse than the version which uses Redmagic galaxies to orient.</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2064 2020-01-13T09:13:13Z

<p>Mlokken: </p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png | 600px]]<br /> <br /> The inclusion of Redmagic galaxies may not seem to make a major difference based on the above comparison, but when comparing the stacks, it's clear that they are needed. Remaking the combined stack shown as the first plot in this post with only CMASS galaxies for orientation yields the following image.<br /> <br /> [[File:1032 to 2032 Mpc stacked cmass 17pt8Mpc smth hess 5965cls.png | 400px]]<br /> This is clearly worse than the first plot, so including Redmagic is necessary.</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2063 2020-01-13T09:11:43Z

<p>Mlokken: /* Importance of including Redmagic galaxies */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png | 600px]]<br /> <br /> The inclusion of Redmagic galaxies may not seem to make a major difference based on the above comparison, but when comparing the stacks, it's clear that they are needed. Remaking the combined stack shown as the first plot in this post with only CMASS galaxies for orientation yields the following image. This is <br /> <br /> [[File:1032 to 2032 Mpc stacked cmass 17pt8Mpc smth hess 5965cls.png | 400px]]</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=File:1032_to_2032_Mpc_stacked_cmass_17pt8Mpc_smth_hess_5965cls.png&diff=2062 2020-01-13T09:09:49Z

<p>Mlokken: </p> <hr /> <div></div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2061 2020-01-13T09:09:07Z

<p>Mlokken: </p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png]]<br /> <br /> The inclusion of Redmagic galaxies may not seem to make a major difference based on the above comparison, but when comparing the stacks, it's clear that they are needed. Remaking the combined stack shown as the first plot in this post with only CMASS galaxies for orientation yields the following image, with no clear extended signal:<br /> <br /> [[File:1032 to 2232 Mpc stacked cmassonly 17pt8Mpc smth hess 6102cls.png | 400px]]</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2060 2020-01-13T09:03:21Z

<p>Mlokken: /* Importance of including Redmagic galaxies */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png]]<br /> <br /> The inclusion of Redmagic galaxies may not seem to make a major difference based on the above comparison, but when comparing the stacks, it's clear that they are needed. Remaking the combined stack shown as the first plot in this post with only CMASS galaxies for orientation yields the following image, with no clear extended signal:<br /> <br /> [[File:1032 to 2232 Mpc stacked cmassonly 17pt8Mpc smth hess 6102cls.png]]</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=File:1032_to_2232_Mpc_stacked_cmassonly_17pt8Mpc_smth_hess_6102cls.png&diff=2059 2020-01-13T09:00:32Z

<p>Mlokken: </p> <hr /> <div></div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2058 2020-01-13T08:59:20Z

<p>Mlokken: /* Importance of including Redmagic galaxies */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png]]<br /> <br /> The inclusion of Redmagic galaxies may not seem to make a major difference based on the above comparison, but when comparing the stacks, it's clear that they are needed. Remaking the combined stack shown as the first plot in this post with only CMASS galaxies for orientation yields the following:<br /> <br /> [[File:Example.jpg]]</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2057 2020-01-13T08:57:33Z

<p>Mlokken: /* Importance of including Redmagic galaxies */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png]]<br /> <br /> The inclusion of Redmagic galaxies may not seem to make a major difference based on the above comparison, but when comparing the stacks, it's clear that they are needed.</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2056 2020-01-13T08:54:03Z

<p>Mlokken: /* Importance of including Redmagic galaxies */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. An example for the 1600-1800Mpc slice is shown below. White headless vectors show the orientation directions, centered on cluster positions (I haven't plotted the cluster positions themselves, to be able to see the arrows better).<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png]]</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2055 2020-01-13T08:51:30Z

<p>Mlokken: /* Importance of including Redmagic galaxies */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. For example,<br /> <br /> [[File:Galfield compare 1632to1832Mpc rmlambda7to200 ndmap h vectors 25a.png | ]]</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=File:Galfield_compare_1632to1832Mpc_rmlambda7to200_ndmap_h_vectors_25a.png&diff=2054 2020-01-13T08:49:33Z

<p>Mlokken: </p> <hr /> <div></div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2053 2020-01-13T08:48:56Z

<p>Mlokken: /* Importance of including Redmagic galaxies */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. I tested this by making stacks of the same clusters oriented using a number-density field of just the CMASS galaxies, and comparing those with the same stacks when oriented using the CMASS+Redmagic field. For example,</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2052 2020-01-13T06:08:58Z

<p>Mlokken: /* Radial profiles and looking at changes with redshift */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> For all the stacks which went into the above combined stack, we can decompose them into multipoles. The variation of the m=2 component with the radial coordinate, when phi=0, is shown below.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. So, I tested stacks at various smoothing scales</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2051 2020-01-13T06:01:42Z

<p>Mlokken: /* Radial profiles and looking at changes with redshift */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> The radial profiles of the m=2 component of all the stacks which went into the above stack are shown below.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range shown above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. So, say we were interested in the evolution from 2000 Mpc away until 1000 Mpc away (z~.52 to ~.24) we'd need to limit all slices to only 600 clusters per slice. Would probably want to do some random re-sampling of the clusters in each slice to get bootstrap errors.<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. So, I tested stacks at various smoothing scales</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2050 2020-01-13T05:46:58Z

<p>Mlokken: /* Radial profiles and looking at changes with redshift */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> The radial profiles of the m=2 component of all the stacks which went into the above stack are shown below.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range quoted above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. We'd have to limit all slices to the lower numbers, i.e. ~600 per stack. Could just choose the right number randomly out of the ones currently being used, but given the relatively<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. So, I tested stacks at various smoothing scales</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2049 2020-01-13T05:39:29Z

<p>Mlokken: /* Radial profiles and looking at changes with redshift */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> The radial profiles of the m=2 component of all the stacks which went into the above stack are shown below.<br /> <br /> [[File:Actplanck rmlambda7to200 HESSIANon54a cmassredmagic 1032to1232Mpc meq2 e0to2on54a 570pts.png | frame|none|alt=Alt text | 1032 to 1232 Mpc, 570 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon46a cmassredmagic 1232to1432Mpc meq2 e0to2on46a 579pts.png | frame|none|alt=Alt text | 1232 to 1432 Mpc, 579 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon40a cmassredmagic 1432to1632Mpc meq2 e0to2on40a 851pts.png | frame|none|alt=Alt text | 1432 to 1632 Mpc, 851 points ]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon35a cmassredmagic 1632to1832Mpc meq2 e0to2on35a 1038pts.png | frame|none|alt=Alt text | 1632 to 1832 Mpc, 1038 points]]<br /> [[File:Actplanck rmlambda7to200 HESSIANon32a cmassredmagic 1832to2032Mpc meq2 e0to2on32a 1202pts.png | frame|none|alt=Alt text | 1832 to 2032 Mpc, 1202 points]]<br /> <br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range quoted above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. We'd have to limit all slices to the lower numbers, i.e. ~600 per stack. Could just choose the right number randomly out of the ones currently being used, but given the relatively<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. So, I tested stacks at various smoothing scales</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=File:Actplanck_rmlambda7to200_HESSIANon32a_cmassredmagic_1832to2032Mpc_meq2_e0to2on32a_1202pts.png&diff=2048 2020-01-13T05:31:55Z

<p>Mlokken: </p> <hr /> <div></div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=File:Actplanck_rmlambda7to200_HESSIANon35a_cmassredmagic_1632to1832Mpc_meq2_e0to2on35a_1038pts.png&diff=2047 2020-01-13T05:31:30Z

<p>Mlokken: </p> <hr /> <div></div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=File:Actplanck_rmlambda7to200_HESSIANon40a_cmassredmagic_1432to1632Mpc_meq2_e0to2on40a_851pts.png&diff=2046 2020-01-13T05:31:06Z

<p>Mlokken: </p> <hr /> <div></div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=File:Actplanck_rmlambda7to200_HESSIANon46a_cmassredmagic_1232to1432Mpc_meq2_e0to2on46a_579pts.png&diff=2045 2020-01-13T05:30:31Z

<p>Mlokken: </p> <hr /> <div></div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=File:Actplanck_rmlambda7to200_HESSIANon54a_cmassredmagic_1032to1232Mpc_meq2_e0to2on54a_570pts.png&diff=2044 2020-01-13T05:29:56Z

<p>Mlokken: </p> <hr /> <div></div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2043 2020-01-13T05:28:46Z

<p>Mlokken: </p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Radial profiles and looking at changes with redshift ==<br /> <br /> The radial profiles of the m=2 component of all the stacks which went into the above stack are shown below.<br /> <br /> <br /> It would be interesting to make some measure of how the filamentary structure changes with redshift, e.g. in the distance range quoted above. I don't know if this is possible given the SNR of the stacks, and I'm not sure about the best way to do this. We would want to compare stacks of the same number of clusters in each redshift slice. Currently, there are ~600 clusters in the 1000-1200 Mpc slice, and that number goes up with each slice to about 1200 in the 1800-2000 Mpc slice. We'd have to limit all slices to the lower numbers, i.e. ~600 per stack. Could just choose the right number randomly out of the ones currently being used, but given the relatively<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. So, I tested stacks at various smoothing scales</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2042 2020-01-13T03:59:43Z

<p>Mlokken: /* Combining stacks of different redshifts */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later). In order, left to right and up to down, the images below start at the 1000-1200 Mpc slice, then add and average the successive 200 Mpc stacks until the final image is the average of 5 stacks in the 1000-2000 Mpc range.<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. So, I tested stacks at various smoothing scales</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2041 2020-01-13T03:56:36Z

<p>Mlokken: /* Combining stacks of different redshifts */</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later).<br /> <br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 570cls bins1.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1140cls bins12.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 1710cls bins123.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2280cls bins1234.png|400px]]<br /> [[File: 1032 to 2232 Mpc stacked cmassredmagic 17pt8Mpc smth hess 2850cls bins12345.png|400px]]<br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. So, I tested stacks at various smoothing scales</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=File:1032_to_2232_Mpc_stacked_cmassredmagic_17pt8Mpc_smth_hess_2850cls_bins12345.png&diff=2040 2020-01-13T03:51:27Z

<p>Mlokken: </p> <hr /> <div></div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=File:1032_to_2232_Mpc_stacked_cmassredmagic_17pt8Mpc_smth_hess_2280cls_bins1234.png&diff=2039 2020-01-13T03:51:12Z

<p>Mlokken: </p> <hr /> <div></div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=File:1032_to_2232_Mpc_stacked_cmassredmagic_17pt8Mpc_smth_hess_1710cls_bins123.png&diff=2038 2020-01-13T03:51:00Z

<p>Mlokken: </p> <hr /> <div></div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=File:1032_to_2232_Mpc_stacked_cmassredmagic_17pt8Mpc_smth_hess_1140cls_bins12.png&diff=2037 2020-01-13T03:50:46Z

<p>Mlokken: </p> <hr /> <div></div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=File:1032_to_2232_Mpc_stacked_cmassredmagic_17pt8Mpc_smth_hess_570cls_bins1.png&diff=2036 2020-01-13T03:50:23Z

<p>Mlokken: </p> <hr /> <div></div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Jan_13,_2020&diff=2035 2020-01-13T03:48:46Z

<p>Mlokken: Created page with &quot;== Combining stacks of different redshifts == I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and...&quot;</p> <hr /> <div>== Combining stacks of different redshifts ==<br /> <br /> I've written a program to take the stacks of clusters in different 200Mpc slices, resize them all to the same physical size, and stack them. Below are plots showing the stack from one slice, then adding the stacks from each successively more distant slice. This combination helps to bring out the signal. These were all done using the combined CMASS and Redmagic galaxy maps for orientation, at an ~18 Mpc smoothing scale, with the ellipticity 0 &lt; e &lt; 2 (more written on the ellipticity later).<br /> <br /> [[File:|1000px]]<br /> <br /> <br /> <br /> == Importance of including Redmagic galaxies ==<br /> <br /> Given Bhuvnesh's warning about how the Redmagic galaxy sample is difficult to mock, we had been wondering if it is possible to do this project with orientations given by the CMASS galaxy field alone. So, I tested stacks at various smoothing scales</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Martine_Logbook&diff=2034 2020-01-13T01:51:45Z

<p>Mlokken: </p> <hr /> <div>[[October 1st, 2018]]<br /> <br /> [[November 26th, 2018]]<br /> <br /> [[January 23, 2019]]<br /> <br /> [[April 12, 2019]]<br /> <br /> [[April 29, 2019]]<br /> <br /> [[June 28, 2019]]<br /> <br /> [[Nov 3, 2019]]<br /> <br /> [[Jan 13, 2020]]</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Martine_Logbook&diff=2005 2019-11-20T22:36:13Z

<p>Mlokken: </p> <hr /> <div>[[October 1st, 2018]]<br /> <br /> [[November 26th, 2018]]<br /> <br /> [[January 23, 2019]]<br /> <br /> [[April 12, 2019]]<br /> <br /> [[April 29, 2019]]<br /> <br /> [[June 28, 2019]]<br /> <br /> [[Nov 3, 2019]]</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Martine_Logbook&diff=2004 2019-11-20T22:36:05Z

<p>Mlokken: </p> <hr /> <div>[[October 1st, 2018]]<br /> <br /> [[November 26th, 2018]]<br /> <br /> [[January 23, 2019]]<br /> <br /> [[April 12, 2019]]<br /> <br /> [[April 29, 2019]]<br /> <br /> [[June 28, 2019]]<br /> <br /> [[Nov 20, 2019]]</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Nov_3,_2019&diff=2003 2019-11-20T22:34:47Z

<p>Mlokken: /* Data Stacks */</p> <hr /> <div>== Data Updates ==<br /> <br /> I am now incorporating the DES redMaGiC galaxy catalogue of luminous red galaxies. The number density maps will be made up of CMASS and redMaGiC galaxies. Figure 1 shows a ~200 Mpc slice at z~.55 with CMASS galaxies plotted in blue and redMaGiC in gray. The redMaPPer clusters which will be stacked are plotted in larger red circles. As expected, the clusters trace the redMaGiC galaxy distribution because the two samples are run with the same algorithm.<br /> <br /> [[File:Cls and gals 200mpc zpt55.png|1000px]]<br /> <br /> I also got the ACT SZ cluster catalog from Mat, so that I can incorporate clusters in the BOSS region. I need to learn more about this catalog, since many of the clusters have redshifts given for them but I don't know this is done with SZ / how the errors work.<br /> <br /> == Data Stacks ==<br /> The following plots are various versions of stacks on cluster locations in the number density map with different versions of orientation on various smoothing scales. Some also have eccentricity cuts. Warning: the axes are not scaled the same, because most of these stacks contain different numbers of clusters and so it makes more sense to look at the comparative intensity of the 'bowtie' vs the center than to scale all axes the same.<br /> <br /> These are all done for the 1600-1800 Mpc slice.<br /> &quot;a&quot; means arcminutes in all of the captions.<br /> <br /> [[File:Cmassredmagic9a rmlgt7 HESSIANon10a cmassredmagic 1632to1832Mpc egt100on10a stack 1387pts.png|frame|none|alt=Alt text | 1387 clusters, e &gt; 100 on 10a, Hessian orientation on 10a.]]<br /> <br /> [[File:Cmassredmagic9a rmlgt7 HESSIANon15a cmassredmagic 1632to1832Mpc stack 1411pts.png|frame|none|alt=Alt text | 1411 clusters, no e cut, Hessian orientation on 15a.]]<br /> <br /> [[File:Cmassredmagic9a rmlgt7 HESSIANon20a cmassredmagic 1632to1832Mpc stack 1411pts.png|frame|none|alt=Alt text | 1411 clusters, no e cut, Hessian orientation on 20a.]]<br /> <br /> [[File:Cmassredmagic9a rmlgt7 HESSIANon20a cmassredmagic 1632to1832Mpc egt100on20a stack 1275pts.png|frame|none|alt=Alt text | 1275 clusters, e &gt; 100 on 20a, Hessian orientation on 20a.]]<br /> <br /> [[File:Cmassredmagic9a rmlgt7 HESSIANon20a cmassredmagic 1632to1832Mpc egt300on20a stack 1010pts.png|frame|none|alt=Alt text | 1010 clusters, e &gt; 300 on 20a, Hessian orientation on 20a.]]<br /> <br /> [[File:Cmassredmagic9a rmlgt7 HESSIANon20a cmassredmagic 1632to1832Mpc egt300on20a XUPon20a stack 1010pts.png|frame|none|alt=Alt text | 1010 clusters, e &gt; 300 on 20a, Hessian orientation on 20a, Symmetry-broken X-UP.]]<br /> <br /> [[File:Cmassredmagic9a rmlgt7 HESSIANon29a cmassredmagic 1632to1832Mpc egt300on29a stack 482pts.png|frame|none|alt=Alt text | 482 clusters, e &gt; 300 on 29a, Hessian orientation on 29a]]<br /> <br /> [[File:Cmassredmagic9a rmlgt7 QUon9a cmassredmagic 1632to1832Mpc egtpt2on9a stack 727pts.png|frame|none|alt=Alt text | 727 clusters, e &gt; 0.2 on 9a, QU orientation on 9a]]<br /> <br /> [[File:Cmassredmagic9a rmlgt7 QUon15a cmassredmagic 1632to1832Mpc egtpt2on15a stack 728pts.png|frame|none|alt=Alt text | 728 clusters, e &gt; 0.2 on 15a, QU orientation on 15a]]<br /> <br /> == Sims ==<br /> Trying eccentricity cuts.<br /> Start with lambda &gt; 10 clusters (from Redmapper lambda-halo mass relation), 200 Mpc slice ~ z=0.55. Hessian orientation on 30 arcminutes of the full number density map from Peak Patch.<br /> <br /> [[File:PkptSZ halo HESSIAN allpkphalo 1832to2032Mpc 30a stack 2258pts.png|frame|none|alt=Alt text | 2258 clusters, no e cut.]]<br /> <br /> <br /> [[File:PkptSZ halolgt10 HESSIAN egt500 allpkphalo 1832to2032Mpc 30a stack 1075pts.png|frame|none|alt=Alt text | 1075 clusters, e &gt; 500 at 30a.]]<br /> <br /> [[File:PkptSZ halolgt10 HESSIANon30a egt700on30a allpkphalo 1832to2032Mpc stack 735pts.png|frame|none|alt=Alt text | 735 clusters, e &gt; 700 at 30a.]]<br /> <br /> [[File:PkptSZ halolgt10 HESSIANon30a egt800on30a allpkphalo 1832to2032Mpc stack 596pts.png|frame|none|alt=Alt text | 596 clusters, e &gt; 800 at 30a.]]<br /> <br /> [[File:PkptSZ halolgt10 HESSIANon30a XUPon30a egt800on30a allpkphalo 1832to2032Mpc stack matched cbar 596pts.png|frame|none|alt=Alt text | 596 clusters, e &gt; 800, X-UP at 30a.]]</div>

Mlokken https://mocks.cita.utoronto.ca/index.php?title=Nov_3,_2019&diff=2002 2019-11-20T22:31:48Z

<p>Mlokken: /* Data Stacks */</p> <hr /> <div>== Data Updates ==<br /> <br /> I am now incorporating the DES redMaGiC galaxy catalogue of luminous red galaxies. The number density maps will be made up of CMASS and redMaGiC galaxies. Figure 1 shows a ~200 Mpc slice at z~.55 with CMASS galaxies plotted in blue and redMaGiC in gray. The redMaPPer clusters which will be stacked are plotted in larger red circles. As expected, the clusters trace the redMaGiC galaxy distribution because the two samples are run with the same algorithm.<br /> <br /> [[File:Cls and gals 200mpc zpt55.png|1000px]]<br /> <br /> I also got the ACT SZ cluster catalog from Mat, so that I can incorporate clusters in the BOSS region. I need to learn more about this catalog, since many of the clusters have redshifts given for them but I don't know this is done with SZ / how the errors work.<br /> <br /> == Data Stacks ==<br /> The following plots are various versions of stacks on cluster locations in the number density map with different versions of orientation on various smoothing scales. Some also have eccentricity cuts.<br /> <br /> These are all done for the 1600-1800 Mpc slice.<br /> &quot;a&quot; means arcminutes in all of the captions.<br /> <br /> [[File:Cmassredmagic9a rmlgt7 HESSIANon10a cmassredmagic 1632to1832Mpc egt100on10a stack 1387pts.png|frame|none|alt=Alt text | 1387 clusters, e &gt; 100 on 10a, Hessian orientation on 10a.]]<br /> <br /> [[File:Cmassredmagic9a rmlgt7 HESSIANon15a cmassredmagic 1632to1832Mpc stack 1411pts.png|frame|none|alt=Alt text | 1411 clusters, no e cut, Hessian orientation on 15a.]]<br /> <br /> [[File:Cmassredmagic9a rmlgt7 HESSIANon20a cmassredmagic 1632to1832Mpc stack 1411pts.png|frame|none|alt=Alt text | 1411 clusters, no e cut, Hessian orientation on 20a.]]<br /> <br /> [[File:Cmassredmagic9a rmlgt7 HESSIANon20a cmassredmagic 1632to1832Mpc egt100on20a stack 1275pts.png|frame|none|alt=Alt text | 1275 clusters, e &gt; 100 on 20a, Hessian orientation on 20a.]]<br /> <br /> [[File:Cmassredmagic9a rmlgt7 HESSIANon20a cmassredmagic 1632to1832Mpc egt300on20a stack 1010pts.png|frame|none|alt=Alt text | 1010 clusters, e &gt; 300 on 20a, Hessian orientation on 20a.]]<br /> <br /> [[File:Cmassredmagic9a rmlgt7 HESSIANon20a cmassredmagic 1632to1832Mpc egt300on20a XUPon20a stack 1010pts.png|frame|none|alt=Alt text | 1010 clusters, e &gt; 300 on 20a, Hessian orientation on 20a, Symmetry-broken X-UP.]]<br /> <br /> [[File:Cmassredmagic9a rmlgt7 HESSIANon29a cmassredmagic 1632to1832Mpc egt300on29a stack 482pts.png|frame|none|alt=Alt text | 482 clusters, e &gt; 300 on 29a, Hessian orientation on 29a]]<br /> <br /> [[File:Cmassredmagic9a rmlgt7 QUon9a cmassredmagic 1632to1832Mpc egtpt2on9a stack 727pts.png|frame|none|alt=Alt text | 727 clusters, e &gt; 0.2 on 9a, QU orientation on 9a]]<br /> <br /> [[File:Cmassredmagic9a rmlgt7 QUon15a cmassredmagic 1632to1832Mpc egtpt2on15a stack 728pts.png|frame|none|alt=Alt text | 728 clusters, e &gt; 0.2 on 15a, QU orientation on 15a]]<br /> <br /> == Sims ==<br /> Trying eccentricity cuts.<br /> Start with lambda &gt; 10 clusters (from Redmapper lambda-halo mass relation), 200 Mpc slice ~ z=0.55. Hessian orientation on 30 arcminutes of the full number density map from Peak Patch.<br /> <br /> [[File:PkptSZ halo HESSIAN allpkphalo 1832to2032Mpc 30a stack 2258pts.png|frame|none|alt=Alt text | 2258 clusters, no e cut.]]<br /> <br /> <br /> [[File:PkptSZ halolgt10 HESSIAN egt500 allpkphalo 1832to2032Mpc 30a stack 1075pts.png|frame|none|alt=Alt text | 1075 clusters, e &gt; 500 at 30a.]]<br /> <br /> [[File:PkptSZ halolgt10 HESSIANon30a egt700on30a allpkphalo 1832to2032Mpc stack 735pts.png|frame|none|alt=Alt text | 735 clusters, e &gt; 700 at 30a.]]<br /> <br /> [[File:PkptSZ halolgt10 HESSIANon30a egt800on30a allpkphalo 1832to2032Mpc stack 596pts.png|frame|none|alt=Alt text | 596 clusters, e &gt; 800 at 30a.]]<br /> <br /> [[File:PkptSZ halolgt10 HESSIANon30a XUPon30a egt800on30a allpkphalo 1832to2032Mpc stack matched cbar 596pts.png|frame|none|alt=Alt text | 596 clusters, e &gt; 800, X-UP at 30a.]]</div>

Mlokken