CPL Status

1
CPL - Status Plans
Klaus Banse
2
CPL - Status Plans

• CPL
• the past
• the present
• the future

3
CPL the past

• CPL project started in Sept. 2001
• first release of library, CPL 1.0, in Dec. 2003
• since then one major and one patch release per
  year
• CPL was developed to provide the basic, commonly
• needed components for VLT/VLTI instrument
  pipelines,
• to be used by ESO and instrument consortia

4
CPL the past

• advantages for ESO, consortia
• standardize process of building pipelines
• speed up development of pipelines
• reduce maintenance load
• further advantages for consortia
• standardized interface to the DFS environment
• start with existing, tested basic framework for
  pipelines
• get pipelines with same look and feel

5
CPL the present

• Library written in C
• using an object oriented design
• installation following the Linux standard
• Supported on
• Linux (from glibc 2.1 on)
• HP-UX 11
• Solaris 8
• Pipeline applications (recipes) written as
  plugins
• integrated as shared libraries for a general
• execution module
• Gasgano (GUI), EsoRex (command line tool)

6
CPL the present
7
CPL the present

CPL
libcplgasgano
cpldfs
cpldrs
cplui
cplcore
8
CPL the present
ref. page for CPL documentation, download,
links, contacts
www.eso.org/observing/cpl

9
CPL the present

• releases of CPL are synchronized with the
  pipeline releases
• (in October), patch releases produced as needed
• current version CPL 3.1 (released in March
  2007)
• mature, stable library
• supports 14 pipelines (on Paranal, La Silla)
• AMBER, CRIRES, GIRAFFE, ISAAC, NACO
• MIDI, SINFONI, SOFI, VIMOS, VISIR, UVES
• FORS 1/2, FLAMES-UVES

10
CPL the future

• Next release will be CPL 4.0 in October 2007
• planned new features
• switch from QFITS to CFITSIO as FITS I/O library
• include sub-library for WCS (from VISTA, based on
  wcslib)
• additional support for
• e.g. error handling, strings, data cubes,
  data type conversion
• internal improvements (efficiency, speed)

11
CPL the future

• Planned evolution of CPL
• keep CPL stable
• predictable release cycle
• avoid API changes as much as possible
• continue work on portability to other platforms
• Mac OS, Linux on 64 bit architectures
• CPL, (some) pipelines already running
• Support (for above) currently discussed
  internally in ESO

12
CPL the future

• Planned evolution of CPL (cont)
• include new functionality if needed commonly by
• VLT/VLTI instrument pipelines
• internal mechanism to migrate new functionality
• into CPL
• mainly (but not limited to)
• cpldfs
• cpldrs

13
CPL the future

• Planned evolution of CPL (cont)
• No interactive data analysis and reduction system
• for the general user
• no display, graphics capabilities
• No attempt to replace existing scientific
  libraries
• Only core imaging functions

14
CPL the future

• Planned evolution of CPL (cont)
• No interactive data analysis and reduction system
• for the general user
• no display, graphics capabilities
• No attempt to replace existing scientific
  libraries
• Only core imaging functions