FACT++  1.0
FACT++ Documentation

FACT++ - The FACT slow control software

Author
thoma.nosp@m.s.br.nosp@m.etz@p.nosp@m.hys..nosp@m.ethz..nosp@m.ch et al.

Table of contents

Installation

FACT++ can be downloaded from the svn by

   svn checkout https://www.fact-project.org/svn/trunk/FACT++ [localdir]

it includes a dim version which is automatically compiled.

For compilation use

   ./configure
   make

Check the ./configure options with –help. It might look confusing, but some features like FITS or QT4 can be switched off, if the necessary library is not at hand and the feature is not needed. For example, if the GUI is not needed its compilation can be switched off by disabling QT4 support with –without-qt4.

If you use a custom built root version on your system without QT support, but have a distribution packe (e.g. debian package) with QT support available, you can give the path to root executables, for example, with –with-rootsys=/usr/bin. All other paths are extracted from subsequent calls to root-config.

Running ./configure will take some time. It tries to really check carefully that everything needed is available on your system, so that you get errors before you start compilation.

If ./configure fails and you send a bug report please attach the file config.log.

If make fails and you send a bug report please attach the complete output of make V=1.

Reminder: These programs use shared libraries, i.e. whenever you re-compile part of the project some of them might be re-compiled as well. As a result already running programs might crash unexpectedly! This is not a bug.

In principle configure also supports

   make install

which would install the package and the libraries in your system, although at the moment this is not recommended

ROOT warnings during compilation

During compilation of the GUI you get some warning from root's TQtWidget.h. These warnings are completely harmless and can be ignored. However, it is sometimes advicable to get rid of them to get a clean compiler run which makes development easier.

Therefore replace

inline void resize(const QSize &size) { QPixmap newSize(size); *(QPixmap *)this = newSize; }

by

inline void resize(const QSize &sz) { QPixmap newSize(sz); *(QPixmap *)this = newSize; }

in TQtWidget.h

Required packages

The following section gives a list of packages which were necessary after a fresh Ubuntu 11.04 installation. In addition to all the development packages the corresponding package with the library is needed.

Note that a recent C++ compiler is needed supporting the latest C++0x standard.

Required (configure will fail without them)

  • subversion
  • gcc
  • g++
  • make
  • libreadline6-dev
  • libboost-all-dev
  • libx11-dev (needed for lesstif, qt4, root)

FITS file support (datalogger, event builder)

  • libccfits-dev

MySQL support (command line options, scheduler)

  • libmysqlclient-dev (optional for MySQL support)
  • libmysql++-dev (option for MySQL support)

If you want 'did'

  • lesstif2-dev

For JavaScrip support

  • libv8-dev

To compile the GUIs

  • libqt4-dev
  • root (see section about root, currently recommended versions 5.18/00b-5.26/00e)

To compile the raw data viewer

  • libglu1-mesa-dev

To compile smartfact with astronomy support and moon

  • libnova-dev

To compile tngweather

  • libsoprano-dev

To compile skypeclient

  • libdbus-1-dev
  • libdbus-glib-1-dev

To create your own documentation

  • graphviz
  • doxygen
  • help2man
  • groff
  • ps2pdf

To create JavaScript documentation

  • jsdoc-toolkit

For developers

  • autoconf
  • autoconf-archive
  • libtool
  • qt4-designer

If you intend to change only Makefile.am but not configure.ac the automake package instead of the autoconf package should be enough.

Some nice to have (FACT++)

  • colorgcc
  • colordiff

Some nice to have (system)

  • fte
  • efte
  • htop

Documentation (usually accessible through http://localhost/ for the tools above:

  • autoconf-doc
  • gcc-doc
  • graphviz-doc
  • libboost-doc
  • libmysql++-doc
  • libtool-doc
  • make-doc
  • qt4-dev-tools [qt4-assistant]
  • qt4-doc-html

How to install root 5.26/00 on Ubuntu 11.04 (natty)

  • install gpp4.4, gcc4.4, g++4.4 (root does not compile with gcc4.5)
  • make links to hidden X11 libraries:
    cd /usr/local
    sudo ln -s x86_64-linux-gnu/libX* .
    
  • in the root source directory
    ./configure --enable-qt --with-cc=gcc-4.4 --with-cxx=g++-4.4 --with-xrootd-opts=--syslibs=/usr/lib/x86_64-linux-gnu --prefix=/usr/local
    
  • make
  • sudo make install
  • pray
  • don't forget to set LD_LIBRARY_PATH correctly before you try to start the fact gui

Current demonstration programs

  • dserver2: A virtual board (A TCP/IP server). It is sending a "hello" message after accepting a communication and then in 3s intervals the current UTC time. The board can be set to state 1 or back to state 0 (just as a demonstration)
  • dclient5: A control program. It accesses two viratual boards (start them with 'dserver2 5000' and 'dserver2 4001') If both boards are connected the START command can be issued to get them to state 'Running'. In this state an asynchronous time stamp can be requested sending the TIME command. to get back from Running to Connected use STOP.
  • test3: a dim console which allows to control all dim servers by sending commands via the dim network.
  • Both, dclient5 and test3 accept the command line options -c0, -c1, -c2 to switch between different console types (or no console in the case of dclient5). In the console you get help with 'h' and the available command with 'c' You get the avilable command-line options with –help

First start the two dserver2s. Then start a dclient5 (if you want it with console use one of the -c options) and a test3 console (with one of the console options if you like) you can now control the hardware boards with the START, STOP and TIME commands or stop (Ctrl-C) and start one of the programs to see what's happening. In the test3 case you first have to cd to the server to which you want to talk by DATA_LOGGER. Don't forget to start dns if you want to control dclient5 from test3 via Dim.

Remarks about Dim usage

To be able to write all received data directly to the FITS files, padding has been disabled calling dic_diable_padding() and dis_disable_padding(). This is done in our own error handler DimErrorRedirecter. Since this should be one of the first objects created in any environment it is quite save. However, every Dim client or server in our network which does not use the DimErrorRedirecter must call these two functions as early as possible.

Blocking programs at startup

At startup most programs try to resolve the name of the dim-dns as well as their local IP address. After this Dim is initialized and tries to contact the dns. These are so far the only blocking operations. Be patient at program startup. They will usually timeout after a while and give you proper informations.

How to add a new tab in the gui?

Do the following steps in exactly this order:

  • Insert the new page from the context menu of the QTabWidget
  • Copy the QDockWidget from one of the other tabs to the clipboard
  • Paste the copied QDockWidget and add it to the new tab (only the tab should be highlited)
  • Now click on the context menu of the region in the tab (QWidget) and change the layout to grid layout

Documentation

Each program has an extensive help text (except the examples). This help text can be displayed with the –help option. For each program a man-page is automatically created (from the help-output), which (at the moment) can be accessed with man ./program.man (Don't forget the ./ before the filename). With make program.html and make program.pdf a HTML page and a pdf document can be created from the man-page.

With make doxygen-doc the HTML documentation as well as a pdf with the whole code documentation can be created.

Each documentation is also available with program –help or man ./program.man.

In alphabetic order:

References

General references

Boost references

FITS references

Available programs

  • dns: Dim's domain-name-server (needed for any communication between Dim servers and clients)
  • did: A simple graphical interface to analyse everything in a Dim network

Examples

There are a few example programs

  • ./argv: Example for usage of the class Configure (command line options, configuration file)
  • ./time: Example for the usage of the class Time (time input/output, conversion)
  • ./log, ./logtime: A simple Dim-Service/-Client combination using MessageDimRX/MessageDimTX

**/