VOEvent used for solar knowledge base
Elizabeth Auden
eca at mssl.ucl.ac.uk
Tue Jul 17 10:58:43 PDT 2007
Hi everyone,
I'd like to highlight a new solar use case for the VOEvent schema.
Lockheed Martin is building a heliophysics features and event knowledge
base (http://www.lmsal.com/helio-informatics/hpkb/). The knowledgebase is
built up as solar events are identified, described as VOEvent packets
with the addition of <lmsal:*> tags, and submitted to the knowledgebase.
The VOEvent schema already imports the IVOA's STC schema - can additional
schemas be imported as well so that VOEvent packets can include customized
elements like the <lmsal:*> tags while still conforming to the VOEvent
schema?
I've attached a sample XML file (describing a coronal loop) generated by
the SolarSoft vobs/ontology module's struct4export and export_event
procedures. You may notice a <Group> placed inside <WhereWhen> that
describes the loop's placement on the Sun. The Lockheed group is amenable
to moving such groups to <What>.
I've copied six of the HPKB scientists to this discussion, and I would be
interested to hear the VOEvent group's thoughts.
Elizabeth
--
Elizabeth Auden, MSSL
Holmbury St. Mary, Dorking RH5 6NT
Tel: +44 (0)1483 204 276
eSDO Technical Lead, AstroGrid Developer
-------------- next part --------------
<?xml version="1.0" encoding="UTF-8" ?>
<voe:VOEvent ivorn="Reserved for KB archivist: KB entry identifier" role="observation" version="1.1" xmlns:voe="http://www.ivoa.net/xml/VOEvent/v1.1" xmlns:lmsal="http://sot.lmsal.com/solarb/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ivoa.net/xml/VOEvent/v1.1 http://www.ivoa.net/xml/VOEvent/VOEvent-v1.1.xsd">
<Who>
<!-- Data pertaining to curation -->
<Name>Reserved for KB archivist: KB entry made by</Name>
<AuthorIVORN>Reserved for KB archivist: URL to suppl. info.</AuthorIVORN>
<Date>2007/6/19 3:26:24</Date>
</Who>
<What>
<!-- Data about what was measured/observed. -->
<Group name="Loop_required">
<Param name="EVENT_NPIXELS" value="59"/>
<Param name="EVENT_PIXELUNIT" value="0.5 arcseconds"/>
</Group>
</What>
<WhereWhen>
<!-- Data pertaining to when and where something occured -->
<ObservationLocation id="EIT">
<AstroCoords coord_system_id="UTC-HPC-TOPO">
<Time>
<TimeInterval>1999-07-19T13:48:10.092,1999-07-19T13:48:23.596</TimeInterval>
</Time>
<Position2D unit="arcsec">
<Value2>
<C1>460.000</C1>
<C2>955.000</C2>
</Value2>
<Error2>
<C1>-1.00000</C1>
<C2>-1.00000</C2>
</Error2>
</Position2D>
<SpatialRegion>
<Region>Box</Region>
<!-- Coordinates of lower-left corner of bounding box -->
<Value2>
<C1>451.000</C1>
<C2>939.000</C2>
</Value2>
<!-- Coordinates of upper-right corner of bounding box -->
<Value2>
<C1>460.000</C1>
<C2>955.000</C2>
</Value2>
</SpatialRegion>
</AstroCoords>
</ObservationLocation>
<Group name="Loop_required">
<Param name="CHAINCODETYPE" value="unknown"/>
<Param name="SKEL_CHAINCODE" value="unknown"/>
<Param name="SKEL_CURVATURE" value="-1.00000"/>
<Param name="SKEL_NSTEPS" value="-1"/>
<Param name="SKEL_STARTC1" value="-1.00000"/>
<Param name="SKEL_STARTC2" value="-1.00000"/>
</Group>
</WhereWhen>
<How>
<!-- Data pertaining to how the feature/event detection was performed -->
<lmsal:data>
<lmsal:OBS_ChannelID>EIT 195</lmsal:OBS_ChannelID>
<lmsal:OBS_Instrument>EIT</lmsal:OBS_Instrument>
<lmsal:OBS_MeanWavel>195.000</lmsal:OBS_MeanWavel>
<lmsal:OBS_WavelUnit>Angstroms</lmsal:OBS_WavelUnit>
</lmsal:data>
<lmsal:method>
<lmsal:FRM_Contact>ms2 at mssl.ucl.ac.uk</lmsal:FRM_Contact>
<lmsal:FRM_DateRun>2007/6/19 3:26:24</lmsal:FRM_DateRun>
<lmsal:FRM_HumanFlag>no</lmsal:FRM_HumanFlag>
<lmsal:FRM_Identifier>Mike Smith</lmsal:FRM_Identifier>
<lmsal:FRM_Institute>MSSL</lmsal:FRM_Institute>
<lmsal:FRM_Name>LoopRecog</lmsal:FRM_Name>
<lmsal:FRM_ParamSet>inputFile, sigma, minimumContourPoints, OutputFile</lmsal:FRM_ParamSet>
</lmsal:method>
</How>
<Why>
<Inference probability="Inf"/>
<Concept>Loop</Concept>
<lmsal:EVENT_TYPE>LP: Loop</lmsal:EVENT_TYPE>
</Why>
<Reference name="FRM_URL" uri="http://www.mssl.ucl.ac.uk/twiki/bin/view/SDO/CoronalLoopDeployment"/>
</voe:VOEvent>
More information about the voevent
mailing list