1 / 12

FABRIC management

FABRIC management. Huib Jan van Langevelde. Reporting management data. FABRIC really started in March 2006 Had a kick-off meeting in Dwingeloo 2 nd meeting in Poznan in September Input from all partners on 6 month progress Management picture fairly complete

obannon
Download Presentation

FABRIC management

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. FABRICmanagement Huib Jan van Langevelde

  2. Reporting management data • FABRIC really started in March 2006 • Had a kick-off meeting in Dwingeloo • 2nd meeting in Poznan in September • Input from all partners on 6 month progress • Management picture fairly complete • But not very homogeneous, working on improvements • Not just for EC, also essential for good project management! • Work packages going from design to implementation • Not smoothly in all places, • DOW is really very sketchy and optimistic • Fortunately the milestones are not all completely crazy • And of course problems finding right people • Still project is progressing quite well • Several people were employed • Milestones are being passed • Collecting documents and minutes on the wiki huib 30/10/06

  3. Goal of the project • Develop: methods for high data rate e-VLBI using distributed correlation • High data rate eVLBI data acquisition and transport • Develop a scalable prototype for broadband data acquisition • Prototype acquisition system • Establish a transportation protocol for broadband e-VLBI • Build into prototype, establish interface normal system • Interface e-VLBI public networks with LOFAR and e-MERLIN dedicated networks • Correlate wide band Onsala data on eMERLIN • Demonstrate LOFAR connectivity • Distributed correlation • Setup data distribution over Grid • Workflow management tool • Develop a software correlator • Run a modest distributed eVLBI experiment • Produce: prototypes, demos, reports, meeting minutes • And spend the money in an accountable way… huib 30/10/06

  4. Part 1, original

  5. Part 1, updated

  6. Part 2, original

  7. Part 2, updated

  8. Manpower huib 30/10/06

  9. Money

  10. Conclusions on spending • MPI, ASTRON, not much started • Which is according to plan • Already spent travel budget • OSO still need a decision how to proceed • Implement for testing or iBOB engineering? • JBO does a lot of work, but is not spending • Which the EU will not see as a problem • But new engineer will join in December • Must keep FABRIC and SA2 bookkeeping seperate • Hour registration seems a bit ad-hoc • MRO is in full swing • Spending money and providing matching • PSNC has implemented FABRIC project • And has no problem spending hours and matching them • I hope I understand the matching hours correctly • I am learning a few tricks here… • JIVE has started but awaits the arrival of more staff • Postdoc will join later this year • Matching is quite OK with NWO supporting SCARIe • Would run project into 4th year! huib 30/10/06

  11. Deliverables first 18 months huib 30/10/06

  12. Some issues • This is a relatively tight show by my standards • But I don’t work at the EC… • Compared to RadioNet::ALBUS: easier to get material • Harder to reach decisions: a few more partners, a lot more noise! • Also multi-disciplinary, not just software • Really like to view this as an R+D project • Continuing European work on data acquisition • Playing with transport protocols • Exercising software correlators on the Grid But turning these into an operational system is quite a bit harder!! • Several concerns: • How to deal with depreciation of hardware • And how should this enter financial reporting • Everybody needs to find their role • Some level of self-organization is needed • But must be part of the greater scheme, interfaces, splinter meetings • Reporting is seen as a scary exercise (too often) • Reports to EC should all go through JIVE contact point • Homogenize reporting so it can be used for project management • Hope we can keep our own standards on doing R+D huib 30/10/06

More Related