Extended source nb draft

[hiyoneda]

Thanks! Everything worked well in my environment. I think that we can move on to producing a data cube from the model and combining it with my notebook.

I want to share a few things I noticed.

• In the notebook, two different pixel orderings are used (RING for dwell_time_map and NESTED for m). Maybe it is better to set a default ordering scheme in the team.
• We need to calculate integrated flux in an energy band to produce the datacube. Related examples might be useful.
• I think that dwell_time_map in the last cell might be confusing. The dwell time map is an exposure time map on the sky in the local coordinate for a given source location under a given time duration and a given satellite attitude. So, dwell time maps for different source locations are basically used separately, not being added together. Also, I am wondering why the poles in the calculated dwell_time_map have a bit large values compared with the others.

[israelmcmc]

About @hiyoneda's first point, mhealpy was designed to be grid agnostic. If you keep track of the scheme when writing/reading file, then all should work just fine without modifying the code. That said, during this fluid stage of development, I've seen sometime the scheme is just assumed to be RING, since that' default in healpy and mhealpy. I suggest we stick to RING for now, but later work to make it independent of the scheme. There are some application where NESTED is more efficient, but I don't think it'll matter for most of the analyses we're doing.