<?xml version="1.0" encoding="UTF-8" ?>
<VOEvent role="prediction"
	ivorn="ivo://sot.lmsal.com/VOEvent#2025-07-16T20:07: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>2025-07-16T18:08:27.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>Enohi</lmsal:Tohbans>
		<lmsal:ChiefPlanner>Enohi</lmsal:ChiefPlanner>
		<lmsal:ChiefObserver>Nitta (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>507</lmsal:OBS_NUM>
		<lmsal:JOP_ID>507</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 14136</lmsal:OBSTITLE>
		<lmsal:SCI_OBJ>FIL</lmsal:SCI_OBJ>     <!--  Scientific objectives -->
		<lmsal:SCI_OBS>FIL</lmsal:SCI_OBS>     <!-- Objects being observed -->
		<lmsal:NOAA_NUM>14136</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>454</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>2025-07-16T20:07:30.000Z 2025-07-16T21:13:30.000Z</crd:TimeInterval>
				</crd:Time>
				<crd:Position3D>454 166</crd:Position3D>
			</crd:AstroCoords>
		</ObservationLocation>

		<Group name="saaIntervals">
			<Param name="saaInterval" value="2025-07-17T00:36:30Z 2025-07-17T00:48:30Z" />
		</Group>
	</WhereWhen>


	<Why>
		<!-- Why was observation performed.  Initial scientific assessment, hypothesized mechanisms, classifications, ... -->
		<Concept>
			<lmsal:Goal>To conduct coordinated observations of active regions (AR) that may launch off-limb CMEs.</lmsal:Goal>
			<lmsal:Purpose>SP Program for keeping SP AUTO (No SP map, FPP_NOOP)</lmsal:Purpose>
		</Concept>

		<Description>
			ASPIICS coronagraph offers unique capabilities to study the early evolution of (off-limb) CMEs. Thanks to its reach from below 1.1 to 3 solar radii, ASPIICS will fill the gap between the disk imagers (like SDO/AIA) and upper-corona observations by, for example, LASCO C2 (2 - 6 solar radii) and C3 (3.7 - 30 solar radii) coronagraphs. However, even with its reach, ASPIICS will not be able to observe the actual source regions of CMEs (AR or destabilized prominences/filaments) on the solar disk. To provide this missing piece of the puzzle of CME origin, we will conduct coordinated observations during (and prior to) several ASPIICS 6-hour-long observing windows. These coordinated observations will allow us to capture unique sequences of changing magnetic field topology before the CMEs are triggered (SOT) and study the response of the cool plasma (IRIS) and hot plasma (XRT, EIS) during and immediately after the CME onset.
		</Description>
	</Why>

</VOEvent>
