Experimental Facilities DivisionORNL - SNS June 22, 2004 SNS Update – Team Building Steve Miller...
-
date post
20-Dec-2015 -
Category
Documents
-
view
217 -
download
1
Transcript of Experimental Facilities DivisionORNL - SNS June 22, 2004 SNS Update – Team Building Steve Miller...
Experimental Facilities Division ORNL - SNSJune 22, 2004
SNS Update – Team Building
Steve Miller
June 22, 2004
DANSE Meeting at Caltech
Experimental Facilities Division ORNL - SNS2
June 22, 2004
SNS Instrument Suite – 3 on-line in 2006
PROTONSPROTONS
Engineering Diffractometer – BL 9Engineering Diffractometer – BL 9
Areas for User and Instrument Support Areas for User and Instrument Support
SANS – BL 6SANS – BL 6
Cold Neutron Chopper Spectrometer – BL 5Cold Neutron Chopper Spectrometer – BL 5
Magnetism – BL 4a Liquids – BL 4b Reflectometers
Magnetism – BL 4a Liquids – BL 4b Reflectometers
High Pressure Diffractometer – BL 3High Pressure Diffractometer – BL 3
Backscattering Spectrometer – BL 2Backscattering Spectrometer – BL 2
Disordered Materials Diffractometer – BL 1bDisordered Materials Diffractometer – BL 1b
Wide Angle Chopper Spectrometer – BL 18Wide Angle Chopper Spectrometer – BL 18
High Resolution Chopper Spectrometer – BL 17High Resolution Chopper Spectrometer – BL 17
Single Crystal Diffractometer – BL 12Single Crystal Diffractometer – BL 12
Fundamental Physics Beamline – BL 13Fundamental Physics Beamline – BL 13
Powder Diffractometer – BL 11aPowder Diffractometer – BL 11a
Software needs to be on-line to support BL 2, 4a, and 4b
Experimental Facilities Division ORNL - SNS3
June 22, 2004
Setting the Stage - Instrument Schedule
• 2006 – 3 instruments: 1 spectrometer and 2 refectometers
• 2007 – 5 instruments: 3 spectrometers and 2 diffractometers
• 2008 – 2 instruments: 1 spectrometer and 1 diffractometer
• 2009 – 1 instrument: 1 diffractometer
• 2010 – 1 instrument: 1 diffractometer
• 2011 – 1 instrument: 1 spectrometer
Experimental Facilities Division ORNL - SNS4
June 22, 2004
Instrument Scientists Eager to Know More
• Want to know what languages they can use.
• Some anxious to learn if they will be able to continue developing software.
• Some wondering if we can produce code that will be easy for their users to learn and use – wondering if they will “loose sleep” over users having difficulty with software.
• Will the learning curve be steep – for them, for their developers, for their users?
• How soon will they be able to begin?
• When will SNS start demonstrating some tangible results?
Experimental Facilities Division ORNL - SNS5
June 22, 2004
Working with Instrument Scientists
• They have data from various experiments and want to develop code that can be re-used as part of the new software hosted at SNS.
• Most desire to be an active part of the software development process – all appear to have opinions…
• Not really that interested in data management issues, distributed processing, networking and grids, etc. – just want software that “works”.
• However, very interested in the science, mathematical accuracy, visualization, and ease of development and use.
• As a fall back, most would write their own code to work with data, or would seek to use existing software packages (DAVE, MSLICE, ISAW, etc.).
Experimental Facilities Division ORNL - SNS6
June 22, 2004
Where to Start?
• Identify team members
• Develop a comprehensive software plan
• Produce software architecture documents
• Finalize functional requirements – move on to specifications
• Develop software plan for each instrument
• Consider and evaluate existing software options
Experimental Facilities Division ORNL - SNS7
June 22, 2004
Proposed Implementation Phases for SNS
• Phase 1 – now until 12/04
– Pull team members together
– Develop plans and architecture
– Prototype code
– Build infrastructure
• Phase 2 - 10/04 until 4/06
– First 3 instruments supported
• Phase 3 - 4/06 until ?
– Incorporate grid and/or network services
– Incorporate high performance computing
– Extend data management services
– Support additional instruments as they come on-line
Experimental Facilities Division ORNL - SNS8
June 22, 2004
Team Members
• DANSE Team
• ISIS – interested in contributing in data management area
• NIST – where can DAVE fit in?
• ANL – how can ISAW be utilized?
• KEK
• HFIR
• ORNL – CSM
• SNS
Team Issues• What can team members best contribute?
• Can we effectively pool resources?
• As they arise, how to manage competing ideas and methods?
• Can we develop consensus?
Experimental Facilities Division ORNL - SNS9
June 22, 2004
Logistics Questions
• When must the construction proposal be submitted? How does this affect the overall development process?
• How to coordinate DANSE construction effort in conjunction with SNS development? What shall the DANSE construction effort comprise?
• What work shall be performed under the DANSE design proposal?
• What collaboration tools shall we utilize? CVS, WIKI, eProject, etc.
• How do we involved the larger team comprised of the other facilities?
• The big picture – who sees it? How do we all achieve it?
Experimental Facilities Division ORNL - SNS10
June 22, 2004
Switching Gears - SNS Wants “Impact” Software
• From day 1, SNS wants to provide researchers with tools having capabilities not previously available to the Neutron Science Community.
• What can we do differently? Are there new technologies we should consider?
• How can/should DANSE contribute to producing impact?
• What is impact software? Nobody can say for sure, but people will know it when they see it.
• Potentially an ideal area for the DANSE team to concentrate.
Experimental Facilities Division ORNL - SNS11
June 22, 2004
What Risks Do We Face?
• Are we able to successfully produce collaborations?
• Can we agree on architecture issues should they arise?
• Are we able to obtain necessary resources?
• Are we able to move quickly enough as a collaboration team?
• Can we develop tools fast enough? Or should we investigate where we can use commercial software?
Experimental Facilities Division ORNL - SNS12
June 22, 2004
SUMMARY
• SNS Instrument Scientists need to be involved in software development.
• Need a composite and comprehensive software plan with software architecture.
• Day 1 software needs to have “impact”.
• The DANSE construction effort must be tightly integrated with SNS plans.
• How to manage this large collaboration – it remains to be seen how we all can work together.
• Need to develop software in phases to meet SNS needs.
• TEAM BUILDING – essential right now.