PDD Format
Transcript of PDD Format
-
8/9/2019 PDD Format
1/22
PPRROOJJEECCTT:: EEXXPPLLOOIITTAATTIIOONN OOFFSSWWIITTCCHHEEDDLL IIGGHHTTPPAATTHHSS FFOORREE--SSCCIIEENNCCEE
AAPPPPLLIICCAATTIIOONNSS((EESSLLEEAA))
TTAASSKK :: EE11--HHIIGGHHPPEERRFFOORRMMAANNCCEEDDAATTAATTRRAANNSSFFEERRUUSSIINNGG
SSWWIITTCCHHEEDDLL IIGGHHTTPPAATTHHSS
AACCTTIIVVIITTYY:: VVEERRYYLLOONNGGBBAASSEELLIINNEEIINNTTEERRFFEERROOMMEETTRRYY((VVLLBBII))
TTEEAAMM :: PP EETTEERRCCLLAARRKKEE
RRAALLPPHHSSPPEENNCCEERR
RRII CCHHAARRDDHHUUGGHHEESS--JJOONNEESS
ProjectDefinitionDocument
VV55..00
Delivering the Potentialof Optical Networkingwith UKLight
-
8/9/2019 PDD Format
2/22
ESLEA Task E1: VLBIProject Definition Document v 5.0
DDoocc uumm eenn tt CCoonn tt rroo ll
Document Reference: ESLEA Project Task E1: VLBIDocument Type: Project Definition DocumentRevision Date: 9th February 2007
REVISION HISTORYRevision date Version Summary of Key Changes24/03/05 1.0 First Version
04/04/05r 1.1 RES additions
04/04/05 1.11 Incorporate CG amendments
04/05/05 2.0 Updated during E1: VLBI team meeting
12/05/05 2.1 Update organisation chart
01/06/05 2.2 Update following project planning meeting (JBO)
17/06/05 2.3 Risk analysis
05/07/05 2.4 5th July operations meeting feedback02/08/05 2.41 Feedback from Paul Burgess and Arpad Szomoru
05/10/05 2.5 Feedback from 4thOctober operations meeting
28/11/05 3.0 Update following project planning meeting at JBO
27/01/06 4.0 Update following project planning meeting at JBO
07/03/06 4.1 Update following operations meeting on 7th March 2006
04/04/06 4.2 Update following operations meeting on 4th April 2006
02/05/06 4.3 Update following operations meeting on 2nd May
19/05/06 4.4 Update following planning meeting on 19th May 2006
15/06/06 4.41 Update Appendix A
04/07/06 4.5 Update following operations telecon on 4th July 2006
23/07/06 4.51 Update Appendix A
01/08/06 4.6 Update following planning meeting on 1st August 2006
07/11/06 4.7 Update following planning meeting on 7th November 2006
09/02/07 5.0 Update following planning meeting on 9th February 2007
COLLABORATION LIST
Name Instituti on E-mailPeter Clarke NeSC [email protected]
Colin Greenwood NeSC [email protected]
Ralph Spencer University of Manchester [email protected]
Richard Hughes-Jones University of Manchester [email protected]
Simon Casey University of Manchester [email protected]
Stephen Kershaw University of Manchester [email protected]
-
8/9/2019 PDD Format
3/22
ESLEA Task E1: VLBIProject Definition Document v 5.0
TTaabb ll ee oo ff CCoonn tt eenn tt ssDocument Control ........................................................................................................................................................2
REVISIONHISTORY...........................................................................................................................................................2COLLABORATIONLIST....................................................................................................................................................... 2DISTRIBUTIONLIST...........................................................................................................................................................2
Table of Content s .........................................................................................................................................................3
1. PURPOSE...................... ...................... ...................... ...................... ...................... .................... ...................... .......... 4
2. BACKGROUND.................... ...................... ..................... ...................... ..................... ....................... ...................... .. 4
3. PROJECT DEFINITION...................... ..................... ...................... ..................... ....................... ...................... .......... 5
3.1 TASKE1OVERVIEW................................................................................................................................................... 53.2 VLBIOVERVIEW........................................................................................................................................................ 53.3 VLBIOBJECTIVES...................................................................................................................................................... 6
3.4 SCOPE...................................................................................................................................................................... 63.5 USERSREQUIREMENTS............................................................................................................................................. 63.6 PROJECTDELIVERABLES............................................................................................................................................ 73.7 PROJECTMILESTONES............................................................................................................................................... 73.8 RISKMANAGEMENT................................................................................................................................................... 83.9 CONSTRAINTS,ASSUMPTIONS&DEPENDENCIES.......................................................................................................... 8
3.9.1 Constraints ..................... ...................... ...................... ....................... ...................... ..................... ................. 83.9.2 Assumptions...................... ....................... ...................... ....................... ..................... ...................... ............. 83.9.3 Dependencies .................... ...................... ....................... ....................... ..................... ..................... ............. 8
4. ORGANISATION & RESPONSIBILITY.....................................................................................................................9
4.1 PROJECTROLES........................................................................................................................................................ 94.1.1 Peter Clarke - ESLEA Principal Investigator ...............................................................................................94.1.2 Ralph Spencer - Activity Lead ..................... ....................... ...................... ....................... ...................... ...... 94.1.3 Richard Hughes-Jones - Senior Researcher................ ....................... ....................... ................... ............ 104.1.4 Colin Greenwood - Project Manager ...................... ...................... ...................... ..................... ................... 104.1.5 Simon Casey - Post-Graduate Research Student......... ...................... ...................... ...................... ........... 114.1.6 Stephen Kershaw - Research Associate.... ...................... ....................... ....................... ....................... .... 11
4.2 REPORTINGREVIEWMECHANISMS........................................................................................................................... 11
5. QUALITY SYSTEMS ................... ...................... ...................... ...................... ...................... ..................... ............... 12
5.1 CHANGECONTROLS................................................................................................................................................ 125.2 PROBLEMREPORTING&CORRECTIVEACTION.......................................................................................................... 125.3 TOOLS .................................................................................................................................................................... 12
APPENDIX A: Organisational Chart .........................................................................................................................13
-
8/9/2019 PDD Format
4/22
-
8/9/2019 PDD Format
5/22
ESLEA Task E1: VLBIProject Definition Document v 5.0
33 .. PPRROOJJ EECCTT DDEEFFIINN II TT IIOONN 3.1 TASK E1OVERVIEW
This task brings two of the most network-intensive application areas, High Energy Physics (HEP) and VeryLong Baseline Interferometry (VBLI), onto the switched optical network. The demonstration of benefits tothese two applications would represent a major success in UKLight exploitation.
Two HEP application areas are involved in Task E1: Collider Detector at Fermilab (CDF) and A Toroidal
LHC ApparatuS (ATLAS). The next generation of collider experiments will produce datasets measured inPetabytes per year that can only be processed and analysed by globally distributed computing resources.High-bandwidth data transport between federated processing centres is therefore an essential componentof the reconstruction and analysis chain.
CDF is a particle physics experiment trying to elucidate the fundamental nature of matter. It is presentlytaking data from proton anti-proton collisions at the worlds highest energy colliding beam facility, theTevatron at Fermilab, Chicago. This data is being analysed by almost 800 physicists located at 61
institutions in 13 countries in three continents. In order to effectively utilise the distributed computingfacilities of this network, it is necessary to have high speed point to point connections, particularly to andfrom Fermilab. To this end, as part of the ESLEA project, the use of a dedicated switched light path toprovide guaranteed high bandwidth from Fermilab (using the US Starlight network) to UCL in the UK(using the UKLight network) is being investigated.
ATLAS is one of four detectors being built at the Large Hadron Collider (LHC), CERN. As part ofpreparations the start of physics collisions at the LHC in 2007, ATLAS scientists are planning to generateand transfer increasing amounts of data. The ESLEA project aims to demonstrate high-bandwidthtransfers of data between CERN and the UK via UKLight and the NetherLight direct connection to CERN.
VLBI is used by radio astronomers to obtain detailed images of cosmic radio sources. The UK is currentlyparticipating in European VLBI experiments as a member of the European VLBI Network (EVN); data arecorrelated using the EVN data processor at the Joint Institute for VLBI in Europe (JIVE), located atDwingeloo, Netherlands. Transports of data to and from the UK at rates of 1Gbps are required to fullyexploit the data rates of current instruments. An overview of VLBI is provided in Section 3.2.
3.2 VLBIOVERVIEW
Very Long Baseline Interferometry (VLBI) is used by radio astronomers to obtain detailed images ofcosmic radio sources. The UK is currently participating in European VLBI experiments as a member ofthe European VLBI Network (EVN), with data being correlated using the EVN data processor at the JointInstitute for VLBI in Europe (JIVE [JIV03]), Dwingeloo, Netherlands. Demonstration transports of data toand from the UK at 500 Mbps have been performed using UDP but effective data rates of 1Gbps are
-
8/9/2019 PDD Format
6/22
ESLEA Task E1: VLBIProject Definition Document v 5.0
VLBI in Europe is run by the European VLBI Network (EVN) and its board of directors have asked the
Joint Institute for VLBI in Europe (JIVE) to coordinate efforts in the development of e-VLBI. VLBI onlyworks by close collaboration between observatories, and any development is necessarily a group activity.For example many of the deliverables listed below in section 3.6 require collaboration with colleagues atJIVE. The availability of several resources (manpower and correlator) are therefore not under the directcontrol of ESLEA, and this has to be reflected in flexibility within the work programme.
In addition, there are a number of radio telescopes in the USA taking data suitable for VLBI analysis. USVLBI data could, in principle, be brought to JIVE for correlation with data from telescopes in the UK andthe rest of Europe, providing a transatlantic separation of detectors and therefore an increased resolution.Such a transfer would require a high-bandwidth link from the East Coast of the US to Chicago, and thenconnected to the UKLight transatlantic link. Similarly, UK VLBI data could be contributed to experimentsat the Haystack correlator at MIT to join US eVLBI experiments. Further background information aboutVLBI is included in Appendix B.
3.3 VLBIOBJECTIVES
The objectives of VLBI activities within the ESLEA project are:
Objective Deadline
Demonstrate advantages of VLBI data transport on UKLight over that available viaproduction networks
April 2006
Formulate methodologies for optimum use of switched light paths for VLBI Jan 2007
Bring eVLBI to the user April 2007
3.4 SCOPE
The following are considered to be within the scope of the ESLEA project:
Hardware architecture: networks, test PCs
Software architecture: network test programmes using existing protocols, analysis and displaysoftware
Novel software implementations testing new protocols
See project deliverables for more detailed information regarding elements of work considered in scope.
The following are considered out of scope of the ESLEA project:
VLBI hardware, VLBI operational software, VLBI observing schedules.
3.5 USERSREQUIREMENTS
The requirements for Task E1 are as follows:
-
8/9/2019 PDD Format
7/22
ESLEA Task E1: VLBIProject Definition Document v 5.0
o Test PCs Amsterdam, London and USA
o 2 fast Mark 5 PCso Laptop computer for staff
Softwareo UDPMon, IPerf, BWCTLo Web100 with multiple TCP stacks, Fast TCP, tsunami, RTP, VSI-E, etc.o Analysis and display: Excel, Word, PowerPoint, C, MatLab, IDL, Java, Perl, MRTG
3.6 PROJECT DELIVERABLES
The deliverables of Task E1: VLBI activities are: Working paper on TCP and UDP VLBI data transfer in Europe, including correlation tests Report on recommended set ups for routine eVLBI, including experiences with European/US
eVLBI data transfer. Report on comparison of UKLight vs Production networks using simulated and physical tests eVLBI experiments during the project at times to be determined by negotiation with the VLBI
community Papers at national ESLEA conferences Journal papers, including papers the 8th EVN Symposium 2006 Final report on optimal use of networks for high data rated transmission
3.7 PROJECT MILESTONES
The following milestones apply to Task E1: VLBI:
# Descript ion Date Status
1 End points in IT and POL connected 14/06/05 Completed
2 GEANT 2 launch 14/06/05 Completed
3 Rank Prize 22/08/05 Completed
4 New VLBI RA appointed 29/08/05 Completed
5 e-Science AHM2005 19/09/05 Completed
6 iGrid2005 26/09/05 Completed
7iGrid Demo: data transport over UKLight-to HaystackObservatory at 0.5 Gbit/s sustained over 2-6 hours
26/09/05 Completed
8 SC2005 12/11/05 Completed9 512 Mbit/s VLBI data transmission JBO-JIVE achieved 28/02/06 Completed
10Final version of working paper on eVLBI set up, European and UStests to date
28/02/06 Completed
11
Sustained data transport (12-24hrs) achieved over UKLight-NetherLight at up to 1 Gbit/s
31/03/06 CompletedSustained at 128 Mbit/s but
further work will be carried out toreach 256 or 512 Mbit/s
-
8/9/2019 PDD Format
8/22
ESLEA Task E1: VLBIProject Definition Document v 5.0
Appendix C includes a breakdown of the Task E1: VLBI milestones as recorded in the Full Description of
Tasks proposal document; these are included for comparative purposes to ensure that the above projectmilestones reflect the original thinking.
See Appendix D for a full breakdown of the project plan, including tasks, start and end dates, milestones,dependencies and resource allocation.
3.8 RISK MANAGEMENT
Risks within this project will be continuously monitored. An initial risk assessment has been undertakenand detailed in Appendix E. This will be updated as new risks are identified or the status of existing riskschange during the course of this project.
Each risk is categorised according to its probability of occurrence and the likely impact if it did occur. Italso gives a management summary of the risk, a recommended containment and ownership of the risk.
The Project Manager will be responsible for the maintenance of the risk log.
3.9 CONSTRAINTS,ASSUMPTIONS & DEPENDENCIES
3.9.1CONSTRAINTS
Availability of network connectivity
Availability of connection into Dwingeloo Availability of test PCs
Constraints set externally by VLBI operations
3.9.2ASSUMPTIONS
We will be able to obtain observing time when the link is available
Correlator will be available for correlation tests for negotiated time slots
3.9.3DEPENDENCIES
Cooperation of staff at JIVE
Cooperation of staff at NRENs and Dante
Cooperation of staff at Haystack
Cooperation of VLBI operations staff at JBO
-
8/9/2019 PDD Format
9/22
ESLEA Task E1: VLBIProject Definition Document v 5.0
44 .. OORRGGAANN IISSAATT IIOONN && RREESSPPOONNSSIIBB II LL II TTYY
4.1 PROJECT ROLES
4.1.1 PETER CLARKE - ESLEAPRINCIPAL INVESTIGATOR
Professor Peter Clarke is Deputy Director, National e-Science Centre; Chair of e-Science, Universityof Edinburgh; member of the Global Grid Forum Steering Committee and co-Director of the Data Areawithin the GGF; responsible for HEP networking in the UK on behalf of PPARC and sits on variousstrategic networking bodies.
Peter is qualified with a PhD in Particle Physics from Oxford University and a B.Sc. in ElectronicEngineering from Southampton University. Research interests include Experimental Particle Physicsand High Performance Global Computing and Networks for Science.
In the field of Particle Physics, he has collaborated in the ATLAS experiment at the CERN LargeHadron Collider; he has worked in the Electroweak sector at LEP and in the Computing sector of theLHC project.
In the field of networking, he has been a principal member of the DataGRID, DataTAG and MB-NGprojects, which address issues on the boundary between Grids and the Network (including Quality ofService, high performance data transport and optical networking).
Project responsibilities include: Chair of Project Management Board.
Strategic decision making
Awareness raising and (human) networking activities
ESLEA time commitments: 10-20% spread over all ESLEA Tasks
4.1.2 RALPH SPENCER - ACTIVITY LEAD
Dr Ralph Spencer is Reader in Radio Astronomy at the University of Manchester. He has worked on the
development of interferometers for radio astronomy since the 1970s. Work on phase stableinterferometers led to the development of the MERLIN array. His interest in VLBI started in the late1970s and was responsible for running VLBI operations at Jodrell Bank Observatory until the mid1990s, when the National Facility took over. European development of the 1 Gbps MkIV VLBI systemwas led by him until 2001. Since then he has worked on fibre-optic data communication systems for theALMA mm-wave instrument and e-MERLIN, and has developed use of the internet for e-VLBI.
-
8/9/2019 PDD Format
10/22
ESLEA Task E1: VLBIProject Definition Document v 5.0
4.1.3 RICHARD HUGHES-JONES - SENIOR RESEARCHER
Richard leads the e-science and Trigger and Data Acquisition development in the Particle Physicsgroup at Manchester University. He has a PhD in Particle Physics and has worked on DataAcquisition and Network projects.
Richard is a member of the Trigger/DAQ group of the ATLAS experiment in the LHC programme,focusing on Gigabit Ethernet and protocol performance. He is also responsible for the High
performance, High Throughput network investigations in the European Union DataGrid and DataTAGprojects, the UK e-Science MB-NG, GridPP and ESLEA projects. He is secretary of the ParticlePhysics Network Coordinating Group which supports networking for UK PPARC researchers. Richardis a co-chair of the Network Measurements Working Group of the Global Grid Forum, a co-chair ofPFLDnet 2005, and a member of the UKLight Technical Committee.
Relevant skills include: knowledge of high throughput protocols, including TCP, UDP; end host h/wand s/w design issues relevant to high performance computing; disk sub-system performance
Project responsibilities include:
Ensure users get the high performance required on links that they want to use
Debugging of the network
Dissemination of methodologies and results
Liaison between VLBI protocol requirements and Task C2: Protocol Development
Key interface between the VLBI project and ESLEA Project Manager on all technical issues.
Technically review and approve specifications to ensure that they are in line with ESLEA projectrequirements.
ESLEA time commitments: 15% on Task E1: VLBI, 10% on Task E1: ATLAS and 15% on Task:C2.
4.1.4 COLIN GREENWOOD -PROJECT MANAGER
Colin is ESLEA Project Manager based at the National e-Science Centre (NeSC), EdinburghUniversity; research background includes a management of technology project, StrathclydeUniversity; 1996-97; MBA, Durham University, 1991.
3 years project management experience at Logical Ai, leading applications integration projects formulti-national clients. Other roles have included small business advisor, marketing consultant andgeologist. Relevant skills include: basic web development; Chartered Marketer; MS Project and Visio.
Project responsibilities include:
Key interfacebetween theTaskE1project teamandotherESLEAstakeholders
-
8/9/2019 PDD Format
11/22
ESLEA Task E1: VLBIProject Definition Document v 5.0
4.1.5 SIMON CASEY -POST-GRADUATE RESEARCH STUDENT
Based at Jodrell Bank Observatory, Simon is undertaking a PhD in the development of eVLBI, lookingto complete September 2007.
Relevant skills and qualifications include: MPhys. in Technological Physics, several years workingwith Linux and programming in C & C++, active interest in computer networking.
Project responsibilities include: Provide technical radio astronomy and application software development support to the project.
ESLEA time commitments: Not funded by ESLEA but contributing to activities as part of his PhDresearch
4.1.6 STEPHEN KERSHAW - RESEARCH ASSOCIATE
Stephen is a Research Assistant at The University of Manchester. He has recently completed hisMPhys. degree there, which included work to attain high data transfer rates for eVLBI (with particular
emphasis on evaluating the suitability of TCP).
Stephens skills of relevance to ESLEA include: Knowledge and experience of using TCP and UDPprotocols, working with and configuring Linux systems to attain high data rates, as well as softwareanalysis and design with C++.
Project responsibilities include:
Evaluate implementations of different current TCP stacks
Evaluate how different protocols (TCP, UDP, DCCP) affect ESLEA applications, for example:o is TCP a suitable protocol for VLBI and, if not, then why not?o is UDP a suitable protocol for VLBI?o what is the affect of TCP on distributed storage elements for ATLASo affect of protocols on ATLAS remote farms
Investigate performance of protocols at high bandwidth
Carry out a detailed user investigation of DCCP
Attend conferences, meeting, ESLEA operations and engineers telecons
Report and paper writing ESLEA time commitments: 100% on Task C2.
4.2 REPORTING REVIEW MECHANISMS
Operational review meetings will be held at regular intervals; these will be chaired & minuted by theESLEAProject Manager Eachmeetingwill address the following but will not belimitedto:
-
8/9/2019 PDD Format
12/22
ESLEA Task E1: VLBIProject Definition Document v 5.0
55 .. QQUUAALL II TTYY SSYYSSTTEEMMSS
5.1 CHANGE CONTROLS
All Change Control will be undertaken in accordance with the following procedures:1. Project Lead informs ESLEA Project Manager (or vice versa) of a change to project specification
in writing.
2. ESLEA Project Manager reviews the change and evaluates the impact.3. The change is documented and minor changes can be agreed at this level.4. Changes that have implications for timescales or budgets will require escalation to the Project
Management Board for approval.5. Project team members should not work on any unapproved changes until written confirmation of
approval is received by the Project Lead.
Specifications governed by change control include project objectives, scope, requirements, tasks,
timescales, milestones, deliverables and all other aspects that impact timely completion of the project. Allapproved changes will be recorded by the Project Manager in the Project Definition Document.
The Project Definition Document is a working document that is open to review and alteration by projectstakeholders. The process for checking and approval of changes to this document is:
1. Document revisions sent to Project Manager by stakeholder.2. Changes checked by Project Manager.3. Revised version of document distributed to team members by Project Manager.
5.2 PROBLEM REPORTING &CORRECTIVEACTION
If problems or issues occur during the project lifecycle, they must be reported to the ESLEA ProjectManager at the first opportunity. All issues will be recorded in the project Issue Log.
It will be the responsibility of the Project Manager to inform the parties concerned and establish with themthe correct course of action to take to ensure that the project is kept on schedule.
Should the impact effect the project timescales, a plan must be created to ensure that these are kept to aminimum or in some cases realistic alternative solutions may be considered to minimise disruption to theproject.
Escalation will be undertaken in accordance with the project organisation structure.
-
8/9/2019 PDD Format
13/22
ESLEA Task E1: VLBIProject Definition Document v 5.0
AAPPPPEENNDDIIXX AA :: OOrrggaann ii ssaa tt ii oonnaa ll CChhaa rrtt
Task C1Network Integration, EngineeringSupport and Resource Allocation
Name Role Time Activity
Clive Davenhall(NeSC)
Software /NetworkEngineer
100%Control PlaneSoftware
Lihaio Liang(NeSC)
NetworkEngineer
100%Systems /Applicationssupport
Task C2Protocol Development
Name Role Time Activity
Mark Handley(UCL)
ActivityLead
10%
Andrea Bittau(UCL) Research
Associate100%
New protocolresearch
RichardHughes-Jones(MAN)
SeniorResearcher
15%
StephenKershaw(MAN)
ResearchAssociate
100%
Existing protocolresearch;New protocoldeployment;supportapplications
CAPABILITY DEVELOPMENT
T k E3
Task E1High Energy Physics
Very Long Baseline InterferometryName Role Time Activity
Roger Jones(LAN)
ActivityLead
20%
Brian Davies
(LAN)
ResearchAssociate
100%
Barney Garrett(ED)
NetworkEngineer
33%
RichardHughes-Jones(MAN)
SeniorResearcher
10%
HEP:ATLASexperiment
Mark Lancaster(UCL)
ActivityLead
5-20%
Task E2High Performance Computing
Name Role Time Activity
Peter Coveney(UCL)
ActivityLead
15%
GiovanniGiupponi (UCL)
ResearchAssociate
100%
RealityGridexperiment -UCL
Stephen Pickles(MAN)
ActivityLead
10%
Robin Pinning(MAN)
ResearchAssociate
100%
RealityGridexperiment -MAN
EXPLOITATION
-
8/9/2019 PDD Format
14/22
ESLEA Task E1: VLBIProject Definition Document v 5.0
AAPPPPEENNDDIIXX BB AAdddd ii tt ii oonnaa ll II nn ffoo rrmm aatt ii oonn VLBI achieves the highest resolution images of any astronomical instrument and provides astronomerswith their clearest view of the most energetic phenomena in the universe. VLBI experiments invert theParticle Physics model by bringing data from a network of distributed but co-ordinated instruments to acentral point in order to correlate the signals from individual telescopes, resulting in enhanced sensitivityand resolution.
The combination of simultaneously acquired signals from two or more widely separated radio telescopes
can effectively create a single coherent instrument with a resolving power proportional to their spatialseparation. Such instruments can achieve a resolution of milliarcseconds, which exceeds the resolution ofoptical telescopes.
Traditional VLBI experiments record data at separate sites with high-precisions timestamps and then eachsite ships the tapes or disks holding this data to a central site where correlation is performed. Datatransfer rates are typically 256 Mbps, although 512 Mbps data rates are possible. Existing physicaltransports of data cannot be scaled to the data rates of which the instruments are capable, and the move
to data transfer over high-speed networks would allow transfer of telescope data to the correlator either inreal-time, or in quasi-real time after local buffering be a great advance. Like Particle Physics, VLBI needslong-duration high-bandwidth connections between sites both within Europe and across the Atlantic,although the data is transferred as continual streams in (quasi-) real-time, with more stringentrequirements on delay and re-ordering.
Advantages of eVLBI over traditional approaches:
Faster turnaround of results, reduced from days or weeks to hours or minutes, which greatly
increases the opportunities to study transient events, such as supernovae or gamma-ray bursts. Improved sensitivity, increasing as the square root of data rates. Many of the telescopes are
already at practical and economic limits of physical size and theoretical noise levels, and soincreased data rates are the simplest route to higher sensitivity. Data transports with multi-Gbpsthroughput will increase the data rate of VLBI experiments over and above that possible withphysical data transport.
Lower cost through the elimination of costly tape and disk pools, and allowing higher degrees ofreliability and automation.
Easier to perform data quality checks with a live connection to ensure that bad data is nottaken over an extended period; this can often only be determined by the combination with datarecorded at another telescope.
Major culture change resulting from permanent connections via fibre and real-time VLBI willfacilitate:o Regular and frequent monitoring observations of variable radio sourceso Move away from three sessions a year to regular VLBI intervals
-
8/9/2019 PDD Format
15/22
ESLEA Task E1: VLBIProject Definition Document v 5.0
AAPPPPEENNDDIIXX CC:: TTaass kk EE11 MM ii ll ee ss tt oonneess
The following project milestones, as outlined in the Full Description of Tasks proposal document, arepertinent to ESLEA Task E1; those of direct relevance to VLBI activities are highlighted in bold. It shouldbe noted that these milestones are included for comparative purposes only to ensure that the projectmilestones outlined in Section 3.7 reflect the original thinking that went into the proposal document.
Ref # Milestone Deadline
E1.1 Demonstrate data transport achieved over UKLight-StarLight link for one
FNAL HEP experiment at 1 Gbps sustained over 1224 hours.
05Q3
E1.2 Demonstrate data transport over UKLight-NetherLight link for eVLBI
experiment at JIVE at 12.5Gbps level for 1224 hours.
05Q4
E1.3 Perform a sustained programme of scheduled repeated and overlappingtransports as above for multiple HEP experiments and eVLBI, as part ofexperimental programmes.
06Q1
E1.4 Perform extended transport at 1-2.5Gbps level switched across
either/both of:i) NetherLight to CERN for LHC Data challengesii) Haystack
06Q2
E1.5 Demonstrate application use of resource allocation mechanismsaccessed through Grid services from application layer.
06Q3
E1.6 Final report on experience and applicability of layer-2 lightpath switchingto HEP experiments and eVLBI experiments..
07Q1
-
8/9/2019 PDD Format
16/22
ESLEA Task E1: VLBIProject Definition Document v 5.0
AAPPPPEENNDDIIXX DD:: VVLLBB II PPrroojj ee cc tt PPll aann
The table below is a summary of the tasks, durations and resource allocation for project. Gantt charts forthe project are also provided.
ID Task Start Date End Date Resource / Status1 2005 ACTIVITIES
2 European Network Tests
3 Tests with dummy data using UDP andTCP to test PC at JIVE
Thu 02/06/05 Fri 11/11/05 Completed
4 Create GEANT2 demo based oniGrid2002 s/w
Thu 05/05/05 Tue 14/06/05 Completed
5 Est and maintain end points in Italy andPoland
Wed 15/06/05 Fri 29/07/05 Completed
6 End points in IT and POL connected Tue 14/06/05 MILESTONE Completed7 GEANT 2 launch Tue 14/06/05 MILESTONE Completed8 Modify GEANT2 demo s/w to transmit
sustained data to IT and POLWed 15/06/05 Fri 29/07/05 Completed
9 Sustained data tests to Italy and Poland Wed 15/06/05 Fri 29/07/05 Completed10 European End System Tests (Mk5a)
11 Planning for iGrid demo (telescopes, etc) Wed 01/06/05 Fri 23/09/05 Completed12 Prepare demo for iGrid Mon 19/09/05 Fri 23/09/05 Completed13 iGrid 2005 Mon 26/09/05 MILESTONE Completed14 Set up and run s/w for SC2005 Mon 03/10/05 Fri 11/11/05 Completed15 SC 2005 Sat 12/11/05 MILESTONE Completed16 USA Tests
17 European-US connectivity tests foriGRID2005 and SC2005
Wed 01/06/05 Fri 18/11/05 Completed
18 Tests with dummy data using UDP andTCP to test PC at Haystack
Mon 29/08/05 Fri 23/09/05 Completed
19 iGrid Demo: data transport over UKLight-to Haystack Observatory at 0.5 Gbit/ssustained over 2-6 hours
Mon 26/09/05 MILESTONE Completed
20 Support Activities
21 New VLBI RA appointed Mon 29/08/05 MILESTONE Completed22 Preparation (presentation) for Rank Prize Wed 01/06/05 Fri 19/08/05 Completed23 Rank Prize Mon 22/08/05 MILESTONE Completed
24 Preparation (paper) for AHM2005 Wed 01/06/05 Fri 01/07/05 Completed25 e-Science AHM2005 Mon 19/09/05 MILESTONE Completed26 2006-07 ACTIVITIES
27 Mark 5a performance tests Mon 05/12/05 Tue 28/02/06 Completed
28 512 Mbit/s VLBI data transmission JBO-JIVEachieved
Tue 28/02/06 MILESTONE Completed
29 Write working paper on eVLBI set up,E d US t t t d t
Mon 28/11/05 Tue 28/02/06 Completed
-
8/9/2019 PDD Format
17/22
ESLEA Task E1: VLBIProject Definition Document v 5.0
41 ESLEA-VLBI working paper completed Fri 30/06/06 MILESTONE Completed
42 Investigate optimisation needed at individualobservatory sites in EVN for the highestpossible data rate transmission to JIVE
Mon 05/06/06 Tue 31/07/07 RS,RHJ,PB
43 Write paper for the 5th Annual e-VLBIConference at Haystack
Tue 01/08/06 Wed 16/08/06 Completed
44 Present paper at the 5th Annual e-VLBIConference
Wed 20/09/06 MILESTONE Completed
45 Network simulation assessment Mon 02/04/07 Mon 30/04/07 SC
46 Use resource allocation mechanismsaccessed through Grid services fromapplication layer (use of CPS)
Mon 12/03/07 Wed 14/03/07 RS,RHJ,ACD
47 Higher bandwidth tests
48 10Gbit/s Ethernet connection JBO-Manchester
Fri 11/05/07 MILESTONE
49 Mk 5b tests Mon 14/05/07 Tue 31/07/07 RS,RHJ,SC,PB
50 VLBI UDP tests to Haystack Mon 19/02/07 Fri 01/06/07 RHJ,SC,RS,AR
51 Network protocol tests
52 Evaluate standard TCP delay Mon 03/07/06 Fri 18/08/06 Completed
53 Review TCP Delay data and completeoutstanding tests
Mon 22/01/07 Fri 09/02/07 SK
54 Write TCP paper and presentation for ESLEAconference Mon 12/02/07 Fri 02/03/07 SK
55 TCP Delay preparations for ESLEAconference completed
Fri 02/03/07 MILESTONE
56 CPU usage Wed 01/11/06 Fri 27/04/07 RHJ,RS,SK
57 Forward error correction Wed 01/11/06 Fri 27/04/07 RHJ,RS,SK
58 Evaluate DCCP performance working paper Mon 16/10/06 Fri 27/10/06 Completed59 Implement UDPMon over DCCP Mon 30/10/06 Fri 24/11/06 Completed60 Investigate observed instability in DCCP at
ManchesterMon 22/01/07 Fri 02/03/07 RHJ
61 Observed instabilities resolved Fri 02/03/07 MILESTONE62 Investigate VLBI protocol requirements into
DCCPMon 30/10/06 Fri 22/12/06 Completed
63 Linux implementation of CCID-VLBIcompleted [ready for use by VLBI]
Fri 01/06/07 MILESTONE
64 Work with C2 Protocols team to implementVLBI s/w over DCCP
Mon 04/06/07 Wed 13/06/07 RHJ,RS
65 Refine and modify DCCP following VLBIdeployment experience
Mon 04/06/07 Wed 13/06/07 AB
66 DCCP patch available for VLBI application Wed 13/06/07 MILESTONE
67 Joint report/paper on DCCP deploymentexperience with VLBI
Mon 04/06/07 Tue 31/07/07 AB,RHJ,RS
68 Joint paper/report completed Tue 31/07/07 MILESTONE69 Bring eVLBI to the User
70 High speed data transfer discussions (viabimonthly Bits 'n ' Bytes meetings)
Fri 21/04/06 Tue 29/05/07 RS,RHJ
71 Interaction with e-VLBI community, e.g. Mon 01/01/07 Tue 31/07/07 RS,PB,RHJ,SC
-
8/9/2019 PDD Format
18/22
09/02/2007 Page 18 of 22
-
8/9/2019 PDD Format
19/22
09/02/2007 Page 19 of 22
-
8/9/2019 PDD Format
20/22
09/02/2007 Page 20 of 22
AAPPPPEENNDDIIXX EE:: VVLLBB II RRIISSKK AASSSSEESSSSMMEENNTT
This assessment outlines the risks associated with Task E1: VLBI of the ESLEA Project. A risk is any factor that may potentially interfere with successful completion of theproject, i.e. satisfying requirements and achieving milestones/deliverables within scheduled timescales. A risk is not a problem - a problem has already occurred; a risk is thepossibility that a problem might occur.
The scoring system rates each identified risk, i.e. High, Medium or Low risk. This rating is based on the likelihood of the risk event occurring (probability) and the effect on the
projects successful completion if it occurs (impact). The default rating/scoring system is as follows:Impact Score can be rated as 1, 3, 5, 7, or 9 (1 = Very Low, 9 = Very High).Probability can be rated as 0.1, 0.3, 0.5, 0.7 or 0.9 (0.1 = Very Low, 0.9 = Very High).
Risk Score is defined as Impact Score x Probability and is shown in the following chart. Priority is based on Risk Score. It is a subjective evaluation based on the experienceof those in the project team. This is a working document and will be updated when new risks are identified, when the status of a risk changes or when a risk is no longer validand should be removed from the log.
0.9 0.9 2.7 4.5 6.3 8.10.7 0.7 2.1 3.5 4.9 6.3
0.5 0.5 1.5 2.5 3.5 4.5
0.3 0.3 0.9 1.5 2.1 2.7PROBABILITY
0.1 0.1 0.3 0.5 0.7 0.9
1 3 5 7 9
IMPACT
Red (High) risks will severely delay / kill the project or means of resolution is unknown.Amber(Medium) risks may delay but will require more manpower and/or equipment to resolve.Green (Low) risks will not delay the project.
Containment strategies mayinclude, but not restricted to: Prevent Reduce Accept Transfer Contingency Control
-
8/9/2019 PDD Format
21/22
09/02/2007 Page 21 of 22
PROJECT: ESLEA TASK: E1: VLBI DATE: 9 FEBRUARY 2007
ID Rank Risk Description Probability Impact Strategy Owner Action
1 Green Failure of UKLight infrastructure, e.g. fibres 0.3 1 Accept PC Political pressure for quick fix of problem
2 Amber Circuit availability, i.e. lightpath congestion 0.5 7 ReducePC/RHJ/RS/
User
Joint planning with other ESLEA pilot applications,.e.g use an ESLEA booking system to scheduleconnections
High level UKERNA negotiations for more capacity
3 GreenLack of onward connectivity to observatory sitesin Europe
0.1 5 Accept RS
Reduce the number of telescopes used thiscompromises the science
Effelsberg (Germany) is unlikely to be connectedwithin the life of the ESLEA project.
The loss of connectivity with telescopes alreadyconnected is a possibility.
4 Green Lack of onward connection to JIVE 0.1 9 Control RHJ Lobbying of SurfNet to apply political pressure
5 Amber Lack of onward to connection to Haystack 0.3 5 Control RS Negotiation with appropriate agencies, e.g. HOPI.
Ensure all stakeholders are aware of ESLEA
project objectives, benefits of support, etc
6 GreenLack of availability of telescopes and Mark 5equipment
0.1 3 Accept RS/RHJ
Reduce scope of project
Keep up to date with the EVN timetable (maindriver for JBO) Requests to change test times canbe made, although the sessions are less flexible.
7 GreenUnable to understand and resolve networkperformance limitations.
0.1 7 Control RHJ Conduct more tests
Add more resources
8 Amber
Unable to understand and resolve equipment
performance limitations (e.g. Mark 5aequipment). 0.3 7 Control RHJ
Torun (Poland) and Medicini (Italy) are still unable
to achieve 512 Mbit/s Conduct more tests / add more resources
9 GreenUnable to understand and resolve performancelimitations of existing protocols.
0.1 7 Control RHJ Conduct more tests
Add more resources
10 Green Lack of availability of the correlator 0.1 5 Reduce RSAdvance scheduling provide as much notice aspossible of usage requirements
11 Green Slow responses from external stakeholders, 0.3 3 Reduce RS/RHJ Ensure open communications channels are maintained
-
8/9/2019 PDD Format
22/22
09/02/2007 Page 22 of 22
e.g. due to resource limitations, time zones, etc. so that project objectives, drivers, deadlines etc are
understood by all stakeholders
12 AmberSoftware modifications/development notcompleted within required timescales.
0.7 5 Control RS/RHJ Reduce scope of work or push back deadlines
13 AmberESLEA project activities adversely affect routineobservations (e.g. Mark 5 failure)
0.3 7 Reduce RS/RHJPre-try new equipment [but unable to buy spares inadvance] but little can be done to mitigate this risk
14 GreenLack of availability of working control planesoftware and new protocols
0.3 5 Reduce RHJKeep communication channels open to ensurerequirements are understood by ESLEA capabilitydevelopment teams