Hi Chin-Lin,
Your plan sounds good. A couple comments:
- Your 1) and 2) are the same thing except for deprojection being on/off. That's fine, but I just want to point out that doing deprojection is just a matter of running reduc_coaddpairmaps multiple times per realization (to do dp=0000, dp=0100, dp=0111, etc.) as opposed to just once (dp=0000). Once you've done the simulation and have your pairmaps, as long as you set mapopt.deproj=true, you pretty much get dprojected and undeprojected maps for free.
- We talked about this on the telecon, but unless we have a way to turn off A/B offsets, what we're going to see is leakage from A/B offsets and nothing more. After deprojection we will see residual leakage from A/B offsets and nothing more. It will still be interesting to add noise to the beam maps and see what happens, and once you proceed to real beam maps, it is possible we will see more than just residual A/B offsets, which would imply an undeprojected residual that is strong enough to affect us. If we don't see anything, we can be glad that undeprojected residuals are below what we care about.
And it might be interesting to be able to see beamwidth / ellipticity deprojection do something when you simulate real beam maps.
I'm in favor doing one more sim, which is with beam maps that have no A/B centroid mismatch, and running with simopt.diffpoint='ideal'. I don't see the downside to doing this and I think it gives is more information about our beams. Without doing it, even if there are weak undeprojected residuals in our beams that we have a shot at seeing via these sims, we'd make ourselves blind to them by always including A/B offsets. Yes, the fact that we'd be blind to them would mean that they're so weak we don't care about them, but if they're there it'd be nice to know.
What do people think? It seemed to me like you guys were opposed.
-Chris