<?xml version="1.0" encoding="UTF-8" ?>
<VOEvent role="prediction"
	ivorn="ivo://sot.lmsal.com/VOEvent#2007-05-07T13:05:00Z"
	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>2007-05-05T14:43:46.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>Sakao</lmsal:Tohbans>
		<lmsal:ChiefPlanner>Sterling</lmsal:ChiefPlanner>
		<lmsal:ChiefObserver>Berger</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>0</lmsal:OBS_NUM>
		<lmsal:JOP_ID>0</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>AR evolution</lmsal:OBSTITLE>
		<lmsal:SCI_OBJ>Active region tracking</lmsal:SCI_OBJ>     <!--  Scientific objectives -->
		<lmsal:SCI_OBS>AR</lmsal:SCI_OBS>     <!-- Objects being observed -->
		<lmsal:NOAA_NUM>10953</lmsal:NOAA_NUM>
		<lmsal:TARGET>AR 10953</lmsal:TARGET>
		<lmsal:slotNumber>7</lmsal:slotNumber>
	</What>


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

		<ObservationLocation>
			<lmsal:xCen>909</lmsal:xCen>		<!-- xcen and ycen from FITS -->
			<lmsal:yCen>-166</lmsal:yCen>
			<lmsal:xFov>0</lmsal:xFov>
			<lmsal:yFov>0</lmsal:yFov>
			<crd:AstroCoords coord_system_id="UTC-HGS-TOPO">
				<crd:Time>
					<crd:TimeInterval>2007-05-07T13:05:00.000Z 2007-05-07T15:05:00.000Z</crd:TimeInterval>
				</crd:Time>
				<crd:Position3D>909 -166</crd:Position3D>
			</crd:AstroCoords>
		</ObservationLocation>

		<Group name="saaIntervals">
			<Param name="saaInterval" value="2007-05-07T14:49:30Z 2007-05-07T14:56:30Z" />
		</Group>
	</WhereWhen>


	<Why>
		<!-- Why was observation performed.  Initial scientific assessment, hypothesized mechanisms, classifications, ... -->
		<Concept>
			<lmsal:Goal>Active region tracking; AR; AR 10953</lmsal:Goal>
			<lmsal:Purpose>Fast map 164 arcsec</lmsal:Purpose>
		</Concept>

		<Description>
			SOT: Follow AR 10953.  XRT: Active Region Observations; STEREO campaign; SOHO/UCVS-Ulysses campaign, to start mid-day UT on 7 May.  EIS:  1) UVCS-Ulysses campaign: Abundances as function of height in AR (HOP7). EIS is requested to observe AR at the limb for a min of 4 hr 15 min per day on five days spanning west limb passage [7th May to disappearance of AR]  2) STEREO campaign. EIS will raster the slit across the active region on the disc and at the limb. (STEREO/SECCHI will complement with 75-second cadence 171 filtergrams, with other three wavelengths at 5-minute cadence.) [4th to 8th May]  3) Coronal dimming study. EIS will run coronal_wave_study to look for evidence of dimming following large events if activity looks likely. [As long as AR is visible]  4) After disappearance of the AR, EIS would like quiet Sun pointing near limb for: a) line broadening and diagnostics above limb  b) STEREO campaign 304 high-cadence co-observations of spicules c) UVCS campaign  If co-alignment program (2hr for N-limb, 2hr for E-limb) was not included in the May 5-7 weekend plan, please run this program soon after disappearance of the AR. andnbsp;This run will be important for calibrating absolute heliocentric coordinate for quiet sun. Also, this program may run once every a few days, depending on the satellite temperatures and science programs.
		</Description>
	</Why>

</VOEvent>
