January 2009 ELabs Meeting

ELabs members will meet January 7-8 at the Adler Planetarium. As a first step to developing our agenda, we should first understand the priorities for the ELabs project. These have been added by the members of the technical telecon group.

Understanding Priorities

Our highest priority is to develop a plan and common understanding of what we need to do to meet the requirements of the NSF proposal. The developers of each e-Lab should fill in what tasks need to be done and what new or improved functionality is required to complete these tasks. If the task/functionality affects all e-Labs, then please enter this under General. Please enter any items related to evaluation such as finalizing/evaluating pretests/posttests. From this list, we should be able to develop an agenda for our meeting.


  • Settling on a technology learner outcome and understanding how to enhance e-Labs to allow students to satisfy it. (1) do we need such an LO? 2) do any of the e-Labs prepare students to achieve the current LO? 3) Could we define an optional Tech/Grid LO (perhaps the current one), with an optional study that does prepare students to achieve it? 4) Could we assign LOs to studies, rather than to e-Labs as a whole?)

  • Overall web portal design, from the front page, to how we direct both newcomers and seasoned veterans to where they want to go quickly and without confusion. How are the forums laid out? How are individual accounts managed? Is there one wiki for the whole site, or one wiki per e-Lab? How to we restrict access to teacher materials (should we restrict access to teacher materials? based on what criteria?)

CMS e-Lab

  • We have already mentioned that we would like to discuss face-to-face the new "drag and drop" interface for the OGRE. This can be listed as part of getting the CMS e-Lab ready for expert/peer review.
  • Integration of OGRE with e-Lab site software
  • Finalize nomenclature: suggested: one CMS e-Lab, with three data sets (Test Beam, Monte Carlo, Run data), and different studies targeted at different data sets
  • CMS full e-Lab LOs approved
  • Studies for MC and Run data written
  • pre/post test for CMS written
  • Workshop agenda, curriculum assembled

Cosmic e-Lab

  • Discuss the structural interaction between the Perl, jsp and Swift in order to understand how to create new analyses.
  • Finish the pre- and post-test and discuss process to roll out the new version.
  • Discuss searching data via a world map (i.e., search for data and display results on a map.)
  • Support plotting time-dependent data uploaded by user against flux and other time-dependent data available from Cosmic data.
  • Discuss using wildcards for data searches.

LIGO e-Lab

  • Interface between Bluestone (PHP) and the e-Lab site software (JSP)
  • Grid execution of a Bluestone analysis under Swift
  • Pre-test and post-test
  • Workshop agenda, curriculum assembled

Technology Infrastructure

  • IT survey - what is the environment like "out there" for our teachers, and for our students?

Wild Card (including new, interesting, and crazy ideas)

  • If it doesn't fit under another heading add it here!


This agenda was developed by Marge Bardeen with the help of Mihael Hategan and Liz Quigg. The focus of the section above on "Understanding Priorities" reflected the concerns of the technical telecon group. Marge folded in the agenda items that involved the larger collaboration including evaluation, advisory board group, i-Labs, etc. She talked with Jean Young and Elisabeth Roberts at length.

January 7

8:30 Coffee; sign up for special topic discussion groups

9:00 Go over & discuss e-Lab requirements

10:45 Break

11:00 Go over & discuss evaluation requirements

12:30 Lunch

1:30 Discuss special topics (plenary or parallel depending on interest)

Some of these are described in more detail in the first section on "Understanding Priorities".

  • Technology LO - this becomes the ComputingLO
  • Pre- post-test (supporting production/development versions, forcing post-test)
  • Web portal design (replacing current www.i2u2.org site with wiki-based version linked to other wikis)
  • Drag and drop data interfaces
  • IT survey (understanding our users' capabilities)
  • Grid execution for LIGO and CMS
  • Workshop development for LIGO and CMS
  • New cosmic features – analyses & yearend data blessing

5:00 Dinner

January 8

8:30 Present i-Lab classes & exhibit

9:45 Break

10:00 Create task list to achieve grant deliverables
  • e-Lab requirements: the RequirementsTable shows what's done or needs to be done for each e-Lab
  • Action Items: The list of tasks we need to do to meet NSF expectations is in the TaskListJan2009 page

10:30 Update status of tasks—general and by e/i-Lab

12:00 Lunch

1:00 Create project schedule

3:00 Discuss next steps –
  • Leadership
  • Communication
  • Ad Group membership & meeting
  • Other

4:00 Adjourn

Attached Documents

To view additional attachments to this page, click on the "Show attachments" link below.
Topic attachments
I Attachment Action Size Date Who Comment
I2U2Requirements2008-20012.v3.pdfpdf I2U2Requirements2008-20012.v3.pdf manage 89 K 2009-01-07 - 15:23 Main.UnknownUser  
I2U2_Jan_7thMorningNotes.docdoc I2U2_Jan_7thMorningNotes.doc manage 78 K 2009-01-15 - 20:14 Main.UnknownUser Notes from January 7th
I2u2-Eval-Toolkit-1-5-09.docdoc I2u2-Eval-Toolkit-1-5-09.doc manage 309 K 2009-01-06 - 19:11 Main.UnknownUser  
I2u2-Eval-Toolkit-1-5-09.pdfpdf I2u2-Eval-Toolkit-1-5-09.pdf manage 453 K 2009-01-06 - 19:17 Main.UnknownUser  
iLabPresentation.pdfpdf iLabPresentation.pdf manage 2 MB 2009-01-15 - 20:15 Main.UnknownUser  
requirements.pdfpdf requirements.pdf manage 26 K 2009-01-07 - 15:38 Main.UnknownUser  
requirements.xlsxls requirements.xls manage 28 K 2009-01-07 - 15:37 Main.UnknownUser  
Topic revision: r38 - 2019-05-22, AdminUser
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback