- Updated pointings and observing strategy
- Data reduction
- Papers
- Work to do - from the budget discussion (suggested responsible)
- GitHub organization and repository
I have updated the pointing, target coordinates and detector offsets to optimize target depth in both imaging and IFU observations.
Basically a “look isn’t it pretty” paper, with line emission maps, moment maps (velocity, skewness, basic kinematics etc.) - nonparametric things.
Mapping of kinematics and ionization structure of the ISM in the Sunburst ASrc, based on line emission maps from the NIRSPec IFU observations. Primary goal is to try to identifu possible LyC escape paths and clues to their origin. Includes analysis of e.g. temperature, density, pressure, Mach number etc. to identifu supersonic flows and shocks.
Take over where Sonia Sharma left off, trying to create reliable source plane models of the nebular emission, working towards the end goal of the project, to balance the ionizing budget. This forward-modeling work might possibly become part of Suhyeons Ph.D. project instead, depending on her interests.
Using the kinematics and ionization etc. maps from paper 2 and the lensing correction maps from paper 3, along with SED and lensing models of stellar population (likely to be standalone work by someone else?) to try to account for all produced and all absorbed ionizing photons in the galaxy, seeing whether our working hypotheses of the ISM geometry and so on is approximately accurate, or something else entirely is going on. Will hopefully reveal something about modes of escape etc.
In short, try to continue the work that Eros started with his “Friggin’ Space Lasers!” paper, but with many more spectroscopic features available and no noisy atmosphere to bork them. This will be Suhyeons first project: It is reasonably easy on the technical side, has some quite interesting astrophysics going on, and the potential to create some attention once the paper is out. Only thing is we probably need to work a bit fast, to not be scooped once the data come out.
See the budget discussion here.
…But perhaps a pixelixed SED like LAXs would also be feasible and a good idea?
…This is a potentially really interesting project that it doesn’t seem like anyone is actually assigned to.
We have a GitHub repository under the bendy-extendy organization; this
repository is meant to share code and documentation and higher-level science
products.
Many places we end up using Google Docs for collaborative documents such as the budget discussion mentioned above. I propose we use the GitHub repository for this; most people are reasonably comfortable with Markdown, and it will keep everything in one place, easy to find, and neatly versioned.
In cases where Markdown doesn’t cut it, collaborative documents in the Github repository can still serve as an information hub, linking to external documents where needed.