LROC TARGETING OPERATIONS Shane Thompson, Julie Stopar, Ernest Bowman-Cisneros, Mark Robinson

OUTLINE REACT, planning –Create a target request Region of Interest (ROI) Acquisition parameters –Time independent JMoon, targeting –SPICE –Queries target database –Creates observation request Questions for discussion

REACT OVERVIEW Submitting Target Requests Site Name –suggestions for formatting Rationale –importance, target info, common terminology Parameters

SUBMITTING TARGET REQUESTS A quick review Rectangle target: a basic box to click-and-drag over a ROI Line target: good for linear features (can only have two endpoints - no two lines sharing an endpoint) Closed polygon target: a series of lines connected by vertices. Each vertex is shared with two line segments. Currently can only have up to 16 vertices Open polygon target: visually, a series of lines with vertices, but first and last endpoints actually have a line between them thus behaving as a closed polygon. DO NOT USE! Make a single line or a long and narrow closed polygon. Dot target: Jmoon will “see” dot targets as 2.5 km east-west line

SITE NAME With an ever growing list of target requests, this name should be sufficiently unique. Should contain geographic info first, then your own identifier(s), and then the feature to be imaged examples: Flamsteed Crater III-185-H2 (central peak) Flamsteed Crater Robinson22 (stereo)

RATIONALE Describe the importance of the observation What and Where: name of associated feature, crater diameter (if applicable) and desired area of interest (i.e., crater rim, floor, or peak; scarp; etc.). If not directly associated with a known feature, indicate the approx. distance to one Why: compositional anomaly, enigmatic feature, volcanism, morphology, stratigraphy, contact relationships, structure or tectonic features, etc? Will targeting this ROI require any difficult observation conditions? photometric/geometric stereo, mosaic (preferred number of NAC-pairs), how much of ROI (# of pointings, or %), most important portion of ROI, incidence angle, etc. Include brief statement as to why.

RATIONALE (con’t) Common terminology Use the accepted geographic names from the “Quad Ancillary List” in REACT Rather than use “large crater” or “small crater,” indicate the diameter in km If you’re unsure of the surface type, prefix the interpretation with “possibly”

RATIONALE (con’t) References are okay to include, but the targeters will not have time to read them so put ALL necessary info into the rationale box. The ROI should clearly constrain the target of interest with support from the Rationale to adequately place the NAC observation(s).

PARAMETERS Investigator: name of person creating ROI (this field can accept text entry) Priority: NASA Request 2 (default) - LROC Mission Objectives (8 categories) 3 - Other Co-I Science Requests 4 - Outsider LROC Science Requests 5 - EPO, Public Requests

PARAMETERS (con’t) NAC: left, right, or both (default) Incidence Low: minimum incidence angle required for ROI (default=40) Incidence High: maximum incidence angle required for ROI (default=80) DowntrackResMin: minimum resolution required for ROI (default=100) DowntrackResMax: maximum resolution required for ROI (default=30) Summing: 1 (default) or 2 Photometric stereo: repeat nadir observations of the same area under different lighting conditions. Requires at least 3 observations. Geometric Stereo: repeat nadir and off-nadir imaging (with same lighting conditions)

PARAMETERS (con’t) Mosaic: blank (no) or 1 (yes). One or more NAC-pairs to be adjacent with some overlap for making a mosaic. MinNumberOfLines: minimum number of lines to acquire for satisfying ROI request Tolerance_percent_ROI: minimal amount, in percent, of ROI area covered by single or multiple NAC frames that would satisfy the ROI Tolerance_percent_footprint: minimal amount, in percent, of NAC footprint area that is required to overlap with an ROI Descriptors: a list of fields with predefined features found on the Moon. Select where appropriate. “Other” field is for your own entry if predefined lists are not applicable.

JMoon Issues that the ops team have run into when targeting ROIs for a series of LRO orbits Large ROIs Many ROIs in a region Mosaics Stereo “Filler” images

15 x4 9 x5 At 50% tolerance, >60 orbits with acceptable lighting conditions and position Mare Humorum At 50% tolerance, >45 orbits with acceptable lighting conditions and position Example of ROIs that may be too large? Q. What should be theoretical maximum number of NACs requested for a mosaic? NAC footprint (5x25 km)

Example of ROIs that may be too densely packed Q. How to target? Should we focus on satisfying one target first, then a second one, and so on… Or equally distribute targets, even if it means that none of the ROIs (50% mosaic) are completely satisfied?

Creating Mosaics: JMoon Example Large mosaic ROIs could get 2-3 images per day, but can’t guarantee they will be connected by later observations with similar lighting conditions.

Creating Stereo Images: JMoon Example Creating geometric stereo requires at least 1 off-nadir observation, possibly 2 (only permitted 3 per day Stereo observations difficult in low lattitudes, relatively easy at high lattitudes

More JMoon Notes More JMoon Notes Empty areas between REACT ROIs or areas without any ROIs will be filled in by small image (less than 50K lines, or single NAC) -targeters will attempt to target interesting features in these areas, but sometimes limited by surrounding ROIs Positioning limited by surrounding observations Read out time Small target to fill space Serendipitous observation where no ROIs previously selected

QUESTIONS FOR DISCUSSION Worth inserting images less than 10K lines? (Would still be 2.5 km x <5km, and provide opportunity to look for unique textures) priority list - make #s 3-5 for high, med, and low science? Questions to ask yourself when making an ROI Am I creating a realistic ROI? –If mosaic, can it realistically be filled by end of primary mission? –If stereo, can it be achieved by end of primary mission? (relevant anymore?) –If large, have enough NAC-pair frames been requested? for larger ROIs: if you only had one NAC-pair, where would you put it? –if you need more, say so (i.e., need more, would like more, more would be a bonus) How will targeters know where to target within your ROI? –describe the location the rationale box –make ROI tightly confined to the feature of interest –If several nearby areas are of interest, make a couple ROIs for each specific feature instead of one that encompasses all How will targeters choose between ROIs with same priority? if too many ROIs are in an area, it will decrease the chances of satisfying all of them.