1 / 9

Status of Tasks Emerging from the February Core/Grid Workshop

Status of Tasks Emerging from the February Core/Grid Workshop. David Malon malon@anl.gov Second ATLAS Core/Grid Workshop 6 May 2002. First US ATLAS Core/Grid Workshop. Motivation was to bring US ATLAS core and grid software developers together

danae
Download Presentation

Status of Tasks Emerging from the February Core/Grid Workshop

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Status of Tasks Emerging from the February Core/Grid Workshop David Malon malon@anl.gov Second ATLAS Core/Grid Workshop 6 May 2002

  2. First US ATLAS Core/Grid Workshop • Motivation was to bring US ATLAS core and grid software developers together • Ensure coherence between core (control framework, data management) and grid middleware • Input specification and output registration are two examples

  3. Discussions leading to tasks • Discussed how to get virtual data into Phase II of Data Challenge 1 • Walked through much of what needs to happen to make this possible • Since this is what we did in the last portion of the workshop, many of our tasks are strongly related to this

  4. Sample tasks • Build a small transformation catalog • Sufficient to describe DC1 event generation • Appropriately parameterized • Get transformation parameters into job options • Emit EDG JDL • LFN generation from transformation parameters • LFNoutstream specification • Background: find out what’s real, what isn’t, in the way of EDG Testbed1 services • …

  5. Task status • Build transformation catalog • Get transformation parameters into job options Status: See Pavel’s talk on Sasha Vaniachine’s prototyping for Phase I DC1 • Emit EDG JDL, with job options in input sandbox Status: No progress(?)

  6. Task status • What’s available and what works in EDG Testbed1 release Status: • Jerry Gieraltowski joined ATLAS EDG validation team to gain early access • Some of our February questions have been answered in principle (e.g., how to find the particular file instance identified by the WP1 scheduler corresponding to an input LFN)

  7. Task status • Initiate file vs. object replication discussions Status: proposed and initiated by Ed Frank, no responses reported to date • Reconcile database architecture and grid and hybrid event store ideas Status: several discussions to date; see later talks • Initiate discussions to coordinate GriPhyN/PPDG/EDG request planner, scheduler Status: Discussions underway (Ruth, Mike, Jenny, Mirco, …)

  8. Task status • Initiate further discussions to specify Event Collection Services Status: In ATLAS database architecture, user interacts with event collection services to specify input • identification of corresponding LFNs and selection of physical file instances is transparent to user Queryable event collections are expected to be a product of LHC-wide common project on persistence

  9. Task status • Coordinate ATLAS PPDG/GriPhyN/iVDGL plans Status: see Rob’s and Torre’s material

More Related