<?xml version="1.0" encoding="UTF-8" ?>
<VOEvent role="prediction"
	ivorn="ivo://sot.lmsal.com/VOEvent#2016-06-11T10:43: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>2016-06-06T21:05:20.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>SOTSP</lmsal:Instrument>
		<lmsal:Tohbans>Hosoi</lmsal:Tohbans>
		<lmsal:ChiefPlanner>Brooks</lmsal:ChiefPlanner>
		<lmsal:ChiefObserver>Cruz (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>300</lmsal:OBS_NUM>
		<lmsal:JOP_ID>300</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>Observations @ W Limb</lmsal:OBSTITLE>
		<lmsal:SCI_OBJ>CR</lmsal:SCI_OBJ>     <!--  Scientific objectives -->
		<lmsal:SCI_OBS>CR</lmsal:SCI_OBS>     <!-- Objects being observed -->
		<lmsal:NOAA_NUM>N/A</lmsal:NOAA_NUM>
		<lmsal:TARGET>Limb</lmsal:TARGET>
		<lmsal:slotNumber>16</lmsal:slotNumber>
	</What>


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

		<ObservationLocation>
			<lmsal:xCen>872</lmsal:xCen>		<!-- xcen and ycen from FITS -->
			<lmsal:yCen>175</lmsal:yCen>
			<lmsal:xFov>0</lmsal:xFov>
			<lmsal:yFov>0</lmsal:yFov>
			<crd:AstroCoords coord_system_id="UTC-HGS-TOPO">
				<crd:Time>
					<crd:TimeInterval>2016-06-11T10:43:30.000Z 2016-06-11T11:48:00.000Z</crd:TimeInterval>
				</crd:Time>
				<crd:Position3D>872 175</crd:Position3D>
			</crd:AstroCoords>
		</ObservationLocation>

		<Group name="saaIntervals">
			<Param name="saaInterval" value="2016-06-11T15:42:30Z 2016-06-11T15:47:00Z" />
		</Group>
	</WhereWhen>


	<Why>
		<!-- Why was observation performed.  Initial scientific assessment, hypothesized mechanisms, classifications, ... -->
		<Concept>
			<lmsal:Goal>Coronal loop magnetic field determination and evolution through coronal rain tracing</lmsal:Goal>
			<lmsal:Purpose>Higher Res Fast Map, 164x164&quot; for near limb</lmsal:Purpose>
		</Concept>

		<Description>
			request to SOT SP and BFI with priority on SP: - SOT/SP: ~ 170 Mbits SP IQUV fast map scan of 123" x 123" FOV (~25 min) during the entire run. For one hour observing run SP is therefore expected to run 2 times.  If the target is too close to limb then it is ok not to run SP if it is not considered appropriate by the SOT team. However, it is good to point out that even in this case a signal from coronal rain may be obtained from off-limb structures, as has been obtained for HMI observations (Martand#237;nez-Oliveros 2014). A search for this signature could help establish the physical process behind this HMI emission.  If BFI is working then: Program number 04cd - Ca II H at a cadence around 10 sec with exposure times long (1.8s) - Half CCD for higher cadence - No 2x2 summing (we need high spatial resolution)  Note: if 1 hour results too heavy for telemetry then please perform 2x2 summing.
		</Description>
	</Why>

</VOEvent>
