Differences between revisions 4 and 5
Revision 4 as of 2008-03-06 06:52:01
Size: 4094
Editor: l4-m0
Comment:
Revision 5 as of 2008-03-11 08:25:27
Size: 5072
Editor: l4-m0
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
 . 10:30 '''''CCMC Capabilities and SDO''''', Peter Mac''''''Niece 10:30 '''''CCMC Capabilities and SDO''''', Peter Mac''''''Niece
Line 7: Line 7:
 . 10:45 '''''SDO Knowledge Base - Introduction''''', Karel Schrijver 10:45 '''''SDO Knowledge Base - Introduction''''', Karel Schrijver
Line 9: Line 9:
By about the end of 2008, SDO will give us over 2TB of data per day. That is too much for almost all of us to retrieve, store, or review on a routine basis. Finding data of interest within the vast archive of SDO data therefore requires a largely automated system to identify events, and an efficient system to find and retrieve the metadata on these events and, ultimately, link to the observations themselves. This discussion will introduce the rationale for a 'knowledge base',
demonstrate an early version, and discuss how 'knowledge' on solar
features and events can be derived, entered into the data base, and
extracted from it.
Line 11: Line 14:
As you hopefully know, we are developing a meta-data knowledge base (http://www.lmsal.com/helio-informatics/hpkb/) that contains information that describes what happened on the Sun. During the SDO teams meeting, we will demonstrate the developing system, and discuss with you, the user community, how the system should function, how it should present its findings in response to your queries, and what kinds of 'events' it should contain. And then, of course, we shall have to discuss which of the aspects that we would like to have are actually affordable and implementable within the coming year, and how we make optimal use with work done within the project and in the community.  . 20 min. Schrijver: General introduction of rationale and principles
 . 20 min. Cheung: Enabling science with a knowledge base
 . 20 min. Hurlburt: Using the HPKB: implementation, tests, validations, ...
 . 20 min. - All Discussion
 . 10 min. Schrijver: Tasks for following sessions
Line 13: Line 20:
Specifically: === The 'Heliophysics Knowledge Base': a tool to find the data that you need ===
Line 15: Line 22:
By about the end of 2008, SDO will give us over 2TB of data per day.
That is too much for almost all of us to retrieve, store, or review on
a routine basis. Finding data of interest within the vast archive of
SDO data therefore requires a largely automated system to identify
events, and an efficient system to find and retrieve the metadata on
these events and, ultimately, link to the observations themselves.
Line 16: Line 29:
 . In the morning of Wednesday, March 26, we will present our thoughts on the system (including how our initial system focused on the Sun can grow into a broad-reaching Heliophysics system and how it complements the Virtual Observatories), demonstrate its first incarnation, discuss how features and events may be found by the analysis of the data flowing into the archive, and start a discussion on the fundamentals of the system.
''' '''
----
=== Later Knowledge Base Sessions ===
As you hopefully know, we are developing a meta-data knowledge base
(http://www.lmsal.com/helio-informatics/hpkb/) that contains
information that describes what happened on the Sun. During the SDO
teams meeting, we will demonstrate the developing system, and discuss
with you, the user community, how the system should function, how it
should present its findings in response to your queries, and what
kinds of 'events' it should contain. And then, of course, we shall
have to discuss which of the aspects that we would like to have are
actually affordable and implementable within the coming year, and how
we make optimal use with work done within the project and in the
community. Specifically:
Line 21: Line 41:
'''Wednesday Afternoon''' During this '''introductory session''' in the morning of Wednesday, March 26, we will present our thoughts on the system (including how our initial system focused on the Sun can grow into a broad-reaching Heliophysics system and how it complements the Virtual Observatories), demonstrate its first incarnation, discuss how features and events may be found by the analysis of the data flowing into the archive, and start a discussion on the fundamentals of the system.
Line 23: Line 43:
Then four sessions follow in which we hope you will actively participate: On Wednesday afternoon four sessions follow in which we hope you will actively participate:
Line 25: Line 45:
 . '''Part 1 (starting at 2:30 on Wednesday)'''       * 1) One session on user and software interfaces with the system (led by Neal Hurlburt) will be followed by three parallel sessions on features and feature finding:  . The first session at 2:30 on Wednesday covers '''user and software interfaces''' with the system (led by Neal Hurlburt)
Line 28: Line 47:
 . '''Part 2 (starting at 4:15 on Wednesday)'''
     * 2a)
Photosphere-to-heliosphere events (such as active regions from AIA and HMI, sunspots, coronal holes, flares from AIA images and from EVE lightcurves, filaments and their eruptions, atmospheric wave phenomena, etc.); this session is chaired by Karel Schrijver; 
     * 2b) Events found from modeling efforts (open-field perimeters, active-region field energies and helicity, field topology, helioseismic events related to fields and flows, etc.); chaired by Mark Cheung, and 
     * 2c) Helioseismic events (far-side measurements, subsurface events including emerging regions, flare-induced oscillations, etc.) chaired by Sasha Kosovichev.
 . This will be followed by three parallel sessions starting at 4:15 on Wednesday on features and feature finding:
 .
  . -1
) '''Photosphere-to-heliosphere events''' (such as active regions from AIA and HMI, sunspots, coronal holes, flares from AIA images and from EVE lightcurves, filaments and their eruptions, atmospheric wave phenomena, etc.); this session is chaired by Karel Schrijver;

  . -
2) '''Events found from modeling efforts''' (open-field perimeters, active-region field energies and helicity, field topology, helioseismic events related to fields and flows, etc.); chaired by Mark Cheung, and

  . -3
) '''Helioseismic events''' (far-side measurements, subsurface events including emerging regions, flare-induced oscillations, etc.) chaired by Sasha Kosovichev.
Line 35: Line 57:
'''Friday Afternoon'''  . The final session on the knowledgebase (on Friday afternoon, starting at 1:30) will be very practical: what keywords do we need, how do we standardize them, what schema, which keys, what kind of IDs, etc. Ifyou are interested in providing events, working with events through the knowledgebase, or if you have catalogs and event finders that can be incorporated into the system, this is a session for you!
Line 37: Line 59:
The final session on the knowledgebase (on Friday afternoon, starting at 1:30) will be very practical: what keywords do we need, how do we standardize them, what schema, which keys, what kind of IDs, etc. If you are interested in providing events, working with events through the knowledgebase, or if you have catalogs and event finders that can be incorporated into the system, this is a session for you! _____________________________________________________________________

Session Agendas/Outlines

 . 1: Wed @10:30: Knowledge Base Introduction of the concept
 . 2) Wed @ 2:30: Using the Knowledge Base - browse, search and output
 . 3a) Wed @ 4:15: Knowledge Base Tools - input
 . 3b) Wed @ 4:15: Knowledge Base Tools - input
 . 3c) Wed @ 4:15: Knowledge Base Tools - input
 . 4) Fri @ 1:30: Metadata/Keys/ID

Wednesday @ 10:30 a.m.

SDO Knowledge Base

Leader: Karel Schrijver

10:30 CCMC Capabilities and SDO, Peter MacNiece

10:45 SDO Knowledge Base - Introduction, Karel Schrijver

This discussion will introduce the rationale for a 'knowledge base', demonstrate an early version, and discuss how 'knowledge' on solar features and events can be derived, entered into the data base, and extracted from it.

  • 20 min. Schrijver: General introduction of rationale and principles
  • 20 min. Cheung: Enabling science with a knowledge base
  • 20 min. Hurlburt: Using the HPKB: implementation, tests, validations, ...
  • 20 min. - All Discussion
  • 10 min. Schrijver: Tasks for following sessions

The 'Heliophysics Knowledge Base': a tool to find the data that you need

By about the end of 2008, SDO will give us over 2TB of data per day. That is too much for almost all of us to retrieve, store, or review on a routine basis. Finding data of interest within the vast archive of SDO data therefore requires a largely automated system to identify events, and an efficient system to find and retrieve the metadata on these events and, ultimately, link to the observations themselves.

As you hopefully know, we are developing a meta-data knowledge base (http://www.lmsal.com/helio-informatics/hpkb/) that contains information that describes what happened on the Sun. During the SDO teams meeting, we will demonstrate the developing system, and discuss with you, the user community, how the system should function, how it should present its findings in response to your queries, and what kinds of 'events' it should contain. And then, of course, we shall have to discuss which of the aspects that we would like to have are actually affordable and implementable within the coming year, and how we make optimal use with work done within the project and in the community. Specifically:

During this introductory session in the morning of Wednesday, March 26, we will present our thoughts on the system (including how our initial system focused on the Sun can grow into a broad-reaching Heliophysics system and how it complements the Virtual Observatories), demonstrate its first incarnation, discuss how features and events may be found by the analysis of the data flowing into the archive, and start a discussion on the fundamentals of the system.

On Wednesday afternoon four sessions follow in which we hope you will actively participate:

  • The first session at 2:30 on Wednesday covers user and software interfaces with the system (led by Neal Hurlburt)

  • This will be followed by three parallel sessions starting at 4:15 on Wednesday on features and feature finding:
    • -1) Photosphere-to-heliosphere events (such as active regions from AIA and HMI, sunspots, coronal holes, flares from AIA images and from EVE lightcurves, filaments and their eruptions, atmospheric wave phenomena, etc.); this session is chaired by Karel Schrijver;

    • -2) Events found from modeling efforts (open-field perimeters, active-region field energies and helicity, field topology, helioseismic events related to fields and flows, etc.); chaired by Mark Cheung, and

    • -3) Helioseismic events (far-side measurements, subsurface events including emerging regions, flare-induced oscillations, etc.) chaired by Sasha Kosovichev.

After the teams meeting, we need to have a prioritized list of which kinds of features we should plan the knowledge base to contain, and how these are to be parametrized by attributes. We also need to have assessments of 1) what it will take to 'find' all features (how much research work and funding, how much CPU time, what kind of data, 2) how much ancillary data is needed, 3) what software exists, 4) which methods need to be developed, etc.) And we need a plan to move forward, including concepts to validate the system, validate the feature-finding software, develop the software, meeting opportunities for working groups, etc. We hope you will give all this thought in preparation of the meeting.

  • The final session on the knowledgebase (on Friday afternoon, starting at 1:30) will be very practical: what keywords do we need, how do we standardize them, what schema, which keys, what kind of IDs, etc. Ifyou are interested in providing events, working with events through the knowledgebase, or if you have catalogs and event finders that can be incorporated into the system, this is a session for you!

_

Session Agendas/Outlines

  • 1: Wed @10:30: Knowledge Base Introduction of the concept
  • 2) Wed @ 2:30: Using the Knowledge Base - browse, search and output
  • 3a) Wed @ 4:15: Knowledge Base Tools - input
  • 3b) Wed @ 4:15: Knowledge Base Tools - input
  • 3c) Wed @ 4:15: Knowledge Base Tools - input
  • 4) Fri @ 1:30: Metadata/Keys/ID


  • Back to [:SDOTeamsMeeting:SDO Teams Meeting Agenda ]

JsocWiki: ParSess21 (last edited 2013-05-01 04:35:23 by localhost)