Getting Started

Documentation

Glish

Learn More

Programming

Contact Us

Version 1.9 Build 1556

News	FAQ
Search	Home

Global objectives

The term interoperability is used here to imply the availability of means to access AIPS data, algorithms or the command line interface (POPS) from within AIPS++ applications or the AIPS++ command line environment (Glish). A complete definition of interoperability in this context however requires a clear specification of the extent to which such access will be enabled. This needs to be determined by weighing the scientific advantages of such an effort against the cost of implementation. The benefits of interoperability during the transition include:

• Simplified user environment: The availability of some AIPS functionality from within the AIPS++ command line interface (CLI), such as the capacity to launch AIPS tasks acting on AIPS data, will provide a simplified interactive interface during the transition period, which has certain benefits for scientific productivity.

• Improved bridging utilities: Targeted access to the AIPS data representation and algorithms from within AIPS++ applications will significantly simplify the development of bridging utilities for use during the transition period. These may include data conversion tasks or simple calibration conversion utilities to translate certain forms of AIPS data to the equivalent AIPS++ representation. This will have certain restrictions due to the different data representations but should nonetheless be useful in allowing smoother transition points from one package to the other in the data reduction sequence.

• Coordinated development: Interoperability will improve the likelihood that development priorities can be coordinated between the two packages.

• Improved programmability: Access to certain types of AIPS methods and data from the AIPS++ CLI will improve the programmability available to the users and provide scientific incentives to use AIPS++. There are clear scientific benefits to being able to access and manipulate both AIPS and AIPS++ data in the AIPS++ CLI.

• Code re-use and testing: Interoperability has some internal uses within the AIPS++ project in allowing re-use of well-established AIPS code in inter-comparison tests between the two systems. This will speed up development and testing of new AIPS++ applications and provide some important information on reliability and accuracy to the user community.

The disadvantages or pitfalls to be considered in implementing interoperability are:

• Cost: The resources required to implement interoperability need to be considered carefully in deciding how far to take this process. The development of native AIPS++ applications is a high priority.

• Design implications: Interoperability should not impact the design or functioning of AIPS or AIPS++ when considered as separate stand-alone packages.