Skip to content

Latest commit

 

History

History
47 lines (33 loc) · 3.2 KB

File metadata and controls

47 lines (33 loc) · 3.2 KB

dprt

This directory contains the Real Time Data Pipeline. This is the Java layer of the real time data pipeline, the C layer is in libdprt.

Directory Structure

  • images This contains a Dockerfile for building a Loci DpRt docker container. Rather than deploying the software as a series of jar's in a tarball, we create a docker container and export that to the control computer.
  • java This contains the source code for the Liverpool Telescope Java robotic layer, which receives commands from the instrument as serialsed Java objects. The commands result in calls, via JNI, to software located in the libdprt repository.
  • latex This contains LaTeX documentation pertaining to the data pipeline.
  • scripts This directory contains scripts to make indepenent deployments of both the data-pipeline and wcs_fit scripts, the wcs_fit script and associated sub-scripts.
  • test This directory contains the test program SendDpRtCommand, which can be used to manually send data-pipelining requests to the DpRt.

Dependencies / Prerequisites

  • The ngat repo/package must be installed: https://github.com/LivTel/ngat . The specific sub-packages required are urrently:
    • ngat_util_logging.jar
    • ngat_util.jar
    • ngat_net.jar
    • ngat_fits.jar
    • ngat_message_inst_dp.jar
    • ngat_message_base.jar
  • The software can only be built from within an LT development environment
  • The DpRt calls the underlying libdprt routines to do the actual data reduction, in the libdprt repository. Specifically, the following sub-module libraries must be present:
    • libdprt_jni_general.so
    • libdprt_object.so
    • libdprt_libfits.so
    • An instrument specific version of the ccd_dprt sub-module i.e. libloci_ccd_dprt.so
    • The instrument specific libdprt JNI interface between the instrument specific DpRtLibrary instance and the instrument specific ccd_dprt build i.e. libdprt_loci.so
  • libdprt depends on the lt_filenames repository for filename support.
  • libdprt uses CFITSIO for accessing FITS images. The same version of CFITSIO compiled against libdprt_libfits.so / ccd_dprt must be used.

Deployment

The data pipeline is usually deployed along with the instrument control software, and the deployment instructions can usually be found within the instrument deployment scripts. This is true of IO:O and Sprat for instance.

The real time data pipeline has been deployed independently in the past on it's own data reduction machine. See dprt_make_deployment for this deployment mechanism.

For LOCI we are trying to dockerise the DpRt into a docker container. See the images directory for details.

At times the wcs_fit script and associated sub-scripts have been deployed separately, see wcs_fit_make_deployment.

Command line test tools

There is a command line test tool to test invoking the real time data pipeline. The software is in the test directory.