Workflow - the broad picture?

Or maybe why ‘I’ am interested in it.

• Scientific team leader at diamond in a group of 22ish people we have 9 EDNA Project Coordinator and previously DNA

• Responsible for delivering and supporting scientific software for all diamond beamlines, covering pre experiment, during and after, data management, formats, cluster computing….

• ‘diamond’ have decided that all scientific software tasks, especially driven from our work will be initiated ‘by’ an EDNA and main GUI framework will be Eclipse.

• Currently putting in about 1 FTE.

DNA 1.0 Workflow

EDNA MX V1

MOSFLM XDS

RADDOSE

BEST

MOSFLM XDS

Indexing

Integration

Strategy

EDNA Workflow direction?• Where does EDNA and EDNA workflow fit in with the

bigger picture?• Who is it for? User (beamline staff and visitors), software

developers, scientific technique developers?• ‘No GUI’• What is it for? Building workflows - Fire and forget or

interactive, logging and changing ‘on the fly’?• How integrated is it to rest of beamline activities?• Can we afford more than one workflow tool? • ‘We’ are the first in the steps to seriously think about it

(at least for DLS).– Low level EDNA or other– Middle, engine and record of workflow?– GUI?

• Workflow tools have been around for a while, and there are many solutions, why aren't we using them in the general scientific community?