<?xml version="1.0" encoding="UTF-8" ?>
<VOEvent role="prediction"
	ivorn="ivo://sot.lmsal.com/VOEvent#2010-07-30T18:51:30Z"
	version="1.11"
	xmlns="http://www.ivoa.net/xml/VOEvent/v1.11"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:lmsal="http://sot.lmsal.com/lmsal"
	xmlns:crd="urn:nvo-coords"
	xsi:schemaLocation="http://www.ivoa.net/xml/VOEvent/VOEvent-v1.1.xsd">


	<Who>
		<!-- Data pertaining to curation: observer, telescope, instrument, planner, tohbans, ... -->
		<Date>2010-07-28T23:20:41.000Z</Date>    <!-- Time VOEvent was generated. -->
		<PublisherID>http://sot.lmsal.com</PublisherID>

		<Contact>
			<Name>Ted Tarbell</Name>
			<Institution>LMSAL</Institution>
			<Communication>
				<Uri>http://lmsal.com</Uri>
				<AddressLine>3251 Hanover Rd, O/ADBS, B/252, Palo Alto, CA, 94304</AddressLine>
				<Telephone>+1-650-424-2400</Telephone>
				<Email>tarbell@lmsal.com</Email>
			</Communication>		</Contact>

		<lmsal:Telescope>Hinode</lmsal:Telescope>
		<lmsal:Instrument>SOT</lmsal:Instrument>
		<lmsal:Tohbans>Yasuda</lmsal:Tohbans>
		<lmsal:ChiefPlanner>Imada</lmsal:ChiefPlanner>
		<lmsal:ChiefObserver>Myers(RCO)</lmsal:ChiefObserver>
	</Who>


	<What>
		<!-- Data pertaining to what was observed, measured, ...   Some of these tags might move into Who section. -->
		<lmsal:obsId></lmsal:obsId>
		<lmsal:OBS_NUM>77</lmsal:OBS_NUM>
		<lmsal:JOP_ID>77</lmsal:JOP_ID>
		<lmsal:JOP></lmsal:JOP>
		<lmsal:JOIN_SB>null</lmsal:JOIN_SB>    <!-- S=SOT, X=XRT, E=EIS, SX=SOT+XRT, EX=EIS+XRT -->
		<lmsal:OBSTITLE>SUMI Rocket Flight Support</lmsal:OBSTITLE>
		<lmsal:SCI_OBJ>AR</lmsal:SCI_OBJ>     <!--  Scientific objectives -->
		<lmsal:SCI_OBS>AR</lmsal:SCI_OBS>     <!-- Objects being observed -->
		<lmsal:NOAA_NUM></lmsal:NOAA_NUM>
		<lmsal:TARGET>Active Region</lmsal:TARGET>
		<lmsal:slotNumber>16</lmsal:slotNumber>
	</What>


	<WhereWhen>
		<!-- Space and Time Coordinates. -->
		<ObservatoryLocation ID="Hinode" />

		<ObservationLocation>
			<lmsal:xCen>-709</lmsal:xCen>		<!-- xcen and ycen from FITS -->
			<lmsal:yCen>161</lmsal:yCen>
			<lmsal:xFov>0</lmsal:xFov>
			<lmsal:yFov>0</lmsal:yFov>
			<crd:AstroCoords coord_system_id="UTC-HGS-TOPO">
				<crd:Time>
					<crd:TimeInterval>2010-07-30T18:51:30.000Z 2010-07-30T20:05:00.000Z</crd:TimeInterval>
				</crd:Time>
				<crd:Position3D>-709 161</crd:Position3D>
			</crd:AstroCoords>
		</ObservationLocation>

		<Group name="saaIntervals">
			<Param name="saaInterval" value="2010-07-30T18:51:30Z 2010-07-30T19:04:00Z" />
			<Param name="saaInterval" value="2010-07-30T20:18:00Z 2010-07-30T20:30:00Z" />
		</Group>
	</WhereWhen>


	<Why>
		<!-- Why was observation performed.  Initial scientific assessment, hypothesized mechanisms, classifications, ... -->
		<Concept>
			<lmsal:Goal>Support of SUMI rocket flight</lmsal:Goal>
			<lmsal:Purpose>SUMI, H-alpha, Ca, hi cadence, Mg b IVDG</lmsal:Purpose>
		</Concept>

		<Description>
			Request to SOT HOP Number 0077   1. High resolution SP-scan of whole AR until 20 minutes before scheduled launch time (SLT). At the end of this scan, we would like BFI/Ca and G-band images and NFI/Mg IV for a FOV that covers the whole AR.  2. From 20 minutes before SLT until 3 hours SLT:    NFI: Mg IV Dopplergram sequence at 25-30 s cadence (wavelength scan      before or after for calibration)    BFI: Ca images at 25-30 s cadence    SP: fast map at 1 min cadence, covering 10-15 arcsec      Ted said he would look into possibly doing a sparse fast map      by summing x2 and exposing at every other slit position. This      would be to increase the region scanned in E-W and the odds of      co-pointing with SUMI.  To reduce telemetry issues, we can reduce the FOV of these high-cadence programs significantly (SUMI has a slit of 512 arcseconds long, so copointing in the S-N direction won't be an issue).     FOV NFI: 384x768 (30x61 arcsec).    FOV BFI: 512x1024 (26x51 arcsec).    FOV SP : 10-15x60 arcsec.  3. 3 hours after SLT: another high-resolution SP-scan of whole AR. At the beginning of this scan, we again would like BFI/Ca and G-band images and NFI/Mg IV for a FOV that covers the whole AR.   Other Instruments:  SUMI, TRACE   Scientific Objectives:  SUMI will obtain 5 minutes of Mg II and C IV spectra and slit-jaw images, as well as Stokes information in those lines. The spatial resolution will be of order 1 arcsec. Targeting will be an active region if it is present, and TBD by Jonathan and colleagues if it isn't. These unique measurements provide an excellent opportunity to study the connection between the chromosphere and TR (along the lines of what IRIS and/or Solar C plan B would do), as well as study the magnetic field properties in the upper chromosphere and low TR. SUMI will have a launch window between 10 and 2 pm local time (White Sands) [i.e., 16-20 UTC], but with a launch time that will be known to 5-10 minutes precision two to fours days in advance. Pointing knowledge and precision will be of order 2-4 arcseconds. Launch is scheduled for Sep 10 or thereabouts. SUMI will attempt to avoid the time periods that Hinode and TRACE pass through the SAA.
		</Description>
	</Why>

</VOEvent>
