VOEvent used for solar knowledge base
Frederic V. Hessman
hessman at Astro.physik.Uni-Goettingen.de
Wed Jul 18 10:05:21 PDT 2007
>> I include a "simple" SOHO-EIT RTML document which covers the
>> corresponding content so that most of this <How> becomes unnecessary.
>
> I think this is a separate conversation between you and Elizabeth.
> I don't think the context of Elizabeth's message was looking for
> alternatives to the LMSAL schema for these packets, but it's great
> if RTML is general enough to support this usage. Different
> communities outside the traditional RTML bailiwick will likely
> already have their own instrument control/observation definition
> schema, that could most simply just be accepted as is. (I'd be
> deeply skeptical about permitting alternatives to STC, however.)
> The nature of the <How> element is to require some level of
> application specific expertise to use productively, in any case.
> The common scaffolding of VOEvent packet handling rests largely
> with the other elements.
I wasn't expecting LMSAL to throw out their schema (although I
wouldn't mind) - the point was to show that the conversion could be
easily made, so LMSAL could easily produce a filter which converts
their internal document to a public one so that they could publish
the details in a VOEvent-compatible format outside the trivially
generated but generally unparseable <Group>'s and <Param>'s. With
archival analyses of SOHO data, this is not very exciting, but when
STEREO starts to produce real-time events, it might be nice to be
able to parse the basic observational parameters like wavelengths of
filters without knowing all the different internal schemata.
>> Also, multi-telescope spacecraft may be better described using the
>> following construct (also not yet kosher):
>>
>> <Device type="spacecraft">
>> <Telescope name="EIT">
>> ...
>> </Telescope>
>> </Device>
>
> The ground-based equivalent in NOAO's data model would be "site".
> An observatory has multiple sites, a site has multiple telescopes,
> a telescope has multiple instruments, etc. Instruments are often
> shared between telescopes, so could be matrixed in a different way,
> but since the precise behavior of the instrument often changes due
> to f-ratio, etc., it is just as reasonable to regard Mosaic-I @
> Mayall (4m) as distinct from Mosaic-I @ WIYN-0.9m. Of course, with
> modern block scheduling a telescope is typically shared between
> multiple institutions, too. WIYN is in effect a time-share
> telescope between its partners, all the way down to the copyright
> of resulting data. And sites often host resources from multiple
> observatories. It's all very incestuous.
Hmmmm...... this would give us explicit structure, but I guess that
this information is generally not needed for ground-based
telescopes. With SOHO, the telescopes all have to look in the same
direction, so the organization via <Device> makes sense where as
<Observatory name="ESO">
<Site name="Cerro Paranal">
<Telescope name="Antu"/>
<Telescope name="Kueyen"/>
<Telescope name="Melipal"/>
<Telescope name="Yepun"/>
</Site>
</Observatory>
is formally correct but who cares, at least for RTML, VOEvent or HTN
purposes? Well, maybe but just maybe for VLTI purposes, but then
one could use
<Device name="VLTI" type="interferometer">
<Telescope name="Antu"/>
<Telescope name="Kueyen"/>
<Telescope name="Melipal"/>
<Telescope name="Yepun"/>
</Device>
which makes useful sense.
>> The current proto-proposal for an appropriate "Standard
>> Vocabulary" description fits easily and would be
>>
>> ucd="phys.magneticField;morphology.loop"
>
> Cool.
Looks like Andrea should be able to present SV at the next inter-
whatever meeting.
Rick
------------------------------------------------------------------------
------------------------
Dr. Frederic V. Hessman Hessman at Astro.physik.Uni-Goettingen.DE
Institut für Astrophysik Tel. +49-551-39-5052
Friedrich-Hund-Platz 1 Fax +49-551-39-5043
37077 Goettingen Room F04-133
http://www.Astro.physik.Uni-Goettingen.de/~hessman
------------------------------------------------------------------------
-------------------------
MONET: a MOnitoring NEtwork of Telescopes
http://monet.Uni-Goettingen.de
------------------------------------------------------------------------
-------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ivoa.net/pipermail/voevent/attachments/20070718/42ad2147/attachment-0001.html>
More information about the voevent
mailing list