Because very much with the requirements and needs for the LOPES experiment in mind, the old version was at its limits and not capable to step up to the task of processing the amounts of data we will be dealing with in LOFAR.
The CR-Tools have to be installed from source; for instructions how to do this and what you need, see the installation page.
In a nut-shell, this is what you have to do:
Even if you are not actively developing new code for the CR-Tools, you surely will be interesting in getting access to new functionality and fixes to known problems; therefore you should be updating your installed version in regular intervals.
The basic steps are:
svn up
from the top-level directory of the code tree.
→ this is something Andreas should be commenting on
There might be three different answers to this question:
implement
directory constitute the library (libcr.a
) which then in turn can be used for writing application programs. implement |-- Analysis |-- ApplicationSupport |-- Calibration |-- Coordinates |-- Data |-- Display |-- IO |-- Imaging |-- LopesLegacy |-- LopesStar |-- Math |-- Observation `-- Utilities
The whole code are is set up such, new functionality can be added in a straight-forward manner.
At the moment (30 Jan 2008) the work on the Skymapper has been frozen in favor of connecting our routines to the expected LOFAR time-series datasets. Most of the classes in the Analysis module are no longer using components of the old Skymap module (which contained the C++ classes used from the Glish scripts), but the connection to the new module (Imaging) has not yet been completed.
At the moment not proper handling of the polarization information is implemented within the CR-Tools.
You probably didn't set the needed optional build parameters when calling cmake
. (Glish requires CR_WITH_GLISH
and the LOPES-Star applications currently require CR_WITH_PYTHON
)
Python bindings for the most basic parts of the library required to read in data are under way. Whereas of course on the longer run we plan to make the full functionality of the library available from the Python prompt, the initial phase will provide the means to open datasets in order to inspect the data; for this bindings to classes in IO
and Data
are generated.