Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:lofar_packages [2009-12-09 15:14] – Arno Schoenmakers | public:lofar_packages [2017-11-14 15:02] (current) – removed Arno Schoenmakers | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Available packages on the LOFAR offline clusternodes ====== | ||
| - | |||
| - | This page gives an overview of available packages, other than the ' | ||
| - | |||
| - | ===== Packages ===== | ||
| - | |||
| - | ^ Package ^ Description ^ Initialize^ Update frequency ^ Comments ^ | ||
| - | | [[#Casa]] | Browser, viewer | '' | ||
| - | | [[# | ||
| - | | grid | | | | | | ||
| - | | hdf5 | library | -- | infrequent | Used by other packs, now 1.8.2 | | ||
| - | | hdf5viewer | | -- | infrequent | | | ||
| - | | [[# | ||
| - | | pipeline | | | | | | ||
| - | | [[# | ||
| - | | wcslib | library | -- | infrequent | Used by other packs, now 4.3 | | ||
| - | |||
| - | \\ | ||
| - | ---- | ||
| - | \\ | ||
| - | |||
| - | ===== Descriptions of Packages ===== | ||
| - | |||
| - | ==== Casa ==== | ||
| - | |||
| - | This is the NRAO developped package that provides Graphical interfaces like those available in the old AIPS++ packages. It provides the following useful tools (see directory ''/ | ||
| - | |||
| - | * casabrowser -> A table browser (much like the old glish-based browser) | ||
| - | * casaplotms -> A tool to make 2-D plots of data in a MS | ||
| - | * casaviewer -> Visualizer | ||
| - | * casapy -> Casa's Python interface. | ||
| - | |||
| - | Extensive documentation can be found [[http:// | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | ==== LofIm ==== | ||
| - | |||
| - | The package LofIm (Lofar Imaging) consists of the following previously known subpackages: | ||
| - | * casacore | ||
| - | * casarest | ||
| - | * pyrap | ||
| - | * LOFAR | ||
| - | * ASKAPsoft | ||
| - | |||
| - | All these are build every night in a single go, with source code extracted from each package' | ||
| - | |||
| - | To activate it on commandline use: | ||
| - | > use LofIm | ||
| - | |||
| - | This will activate the version that was build last night. It will add all settings needed to use the subpackages toyour '' | ||
| - | |||
| - | As all of the individual subpackages are in a development phase, we **cannot** guarantee that each nightly build is bugfree, or even that is has succeeded. Therefore, we keep a '' | ||
| - | > use LofIm <day> (e.g., use LofIm Wed) | ||
| - | |||
| - | If the problem that caused a build to fail has not been solved in a week's time, you will not be able to use the package until it has been fixed. In due time we will implement a system with a release policy, that will enable you to use ' | ||
| - | |||
| - | ==== Pythonlibs ==== | ||
| - | |||
| - | We have made available several useful Python modules. These can be activated with a single command: | ||
| - | > use Pythonlibs | ||
| - | |||
| - | (see [[public: | ||
| - | |||
| - | * [[http:// | ||
| - | * [[http:// | ||
| - | * [[http:// | ||
| - | * [[http:// | ||
| - | * [[http:// | ||
| - | * [[http:// | ||
| - | * [[http:// | ||
| - | * [[http:// | ||
| - | |||
| - | |||
| - | |||