Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| public:docker [2017-02-08 15:36] – created Jan David Mol | public:docker [2018-06-07 06:52] (current) – [Development (extending the software)] Jan David Mol | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| We offer the LOFAR software as Docker images, allowing anyone to run our software using the same configuration, | We offer the LOFAR software as Docker images, allowing anyone to run our software using the same configuration, | ||
| - | ====== LOFAR Pipeline | + | ====== LOFAR Interferometry Post-Processing |
| To run the lofar pipeline software, you need to: | To run the lofar pipeline software, you need to: | ||
| - | | + | |
| - | | + | |
| - | | + | docker run -it --rm -u $UID -e USER -e HOME -v $HOME:$HOME lofar/ |
| + | </ | ||
| + | | ||
| you@3617438dfc63:/ | you@3617438dfc63:/ | ||
| Usage: DPPP [-v] [parsetfile] [parsetkeys...] | Usage: DPPP [-v] [parsetfile] [parsetkeys...] | ||
| parsetfile: a file containing one parset key=value pair per line | parsetfile: a file containing one parset key=value pair per line | ||
| parsetkeys: any number of parset key=value pairs, e.g. msin=my.MS | parsetkeys: any number of parset key=value pairs, e.g. msin=my.MS | ||
| - | </ | + | </ |
| + | you@3617438dfc63:/ | ||
| + | / | ||
| + | Usage: / | ||
| + | Results: | ||
| + | </ | ||
| you@3617438dfc63:/ | you@3617438dfc63:/ | ||
| AOFlagger 2.8.0 (2016-06-21) command line application | AOFlagger 2.8.0 (2016-06-21) command line application | ||
| Line 26: | Line 33: | ||
| </ | </ | ||
| + | ====== LOFAR Pulsar Post-Processing Software ====== | ||
| - | Once you have the above up and running, you will need some data to work on, and likely a parset with configuration settings. If you've put both in your home directory, they' | + | To run the lofar pipeline software, you need to: |
| + | - Install and configure [[https:// | ||
| + | - Download and start the LOFAR image by running: < | ||
| + | docker run -it --rm -u $UID -e USER -e HOME -v $HOME:$HOME lofar/ | ||
| + | </ | ||
| + | - You now have the LOFAR pulp software available at your finger tips, and your home directory available. You can run for example: < | ||
| + | you@3617438dfc63:/ | ||
| + | Usage: pulp.py <--id ObsID> [-h|--help] [OPTIONS] | ||
| + | </ | ||
| + | |||
| + | ====== Q&A ====== | ||
| + | |||
| + | ===== Installation ===== | ||
| + | |||
| + | === Q: Where can I find a list of available LOFAR software versions? === | ||
| + | |||
| + | A: For '' | ||
| + | |||
| + | === Q: What is included in the image? === | ||
| + | |||
| + | We put the following in our '' | ||
| + | |||
| + | * LOFAR Pipeline Framework & Recipes | ||
| + | * NDPPP | ||
| + | * AWImager | ||
| + | * AOFlagger | ||
| + | * DAL2 | ||
| + | * Casacore + casarest + python-casacore | ||
| + | |||
| + | ===== Running the software ===== | ||
| + | |||
| + | === Q: I can't see my data or parset? === | ||
| + | |||
| + | Once you have the Docker image up and running, you will need some data to work on, and likely a parset with configuration settings. If you've put both in your home directory, they' | ||
| + | |||
| + | === Q: I get " | ||
| + | |||
| + | A: The LOFAR software is compiled for a 2015-era processor (Intel Xeon E5-2603v3 to be exact) for performance reasons, and uses CPU instructions not available on older machines. Please run our images on a newer machine, or [[# | ||
| + | |||
| + | ===== Development (extending the software) ===== | ||
| + | |||
| + | === Q: How do I obtain your Dockerfiles? | ||
| + | |||
| + | A: By running: | ||
| + | |||
| + | < | ||
| + | svn co -N https:// | ||
| + | cd LOFAR-Release-2_19 | ||
| + | svn up CMake | ||
| + | mkdir -p build/ | ||
| + | |||
| + | cmake ../.. -DBUILD_PACKAGES=Docker -DUSE_LOG4CPLUS=OFF -DUSE_CASACORE=OFF && make -j 16 install | ||
| + | </ | ||
| + | |||
| + | which will put the Dockerfiles in subdirectories in '' | ||
| + | |||
| + | === Q: How do I build your Docker images from scratch? === | ||
| + | |||
| + | A: By obtaining the Dockerfiles (see above), and running: | ||
| + | |||
| + | < | ||
| + | # load LOFAR environment variables, used to determine tags etc | ||
| + | source installed/ | ||
| + | # build all LOFAR images, in the order required by their interdependencies | ||
| + | docker-build-all.sh | ||
| + | </ | ||
| + | |||
| + | === Q: How do I add files/ | ||
| + | |||
| + | A: The best way to add stuff to our images is by creating a new image based on ours. To do so, create a directory containing the files you want to add. Add to this directory a '' | ||
| + | |||
| + | < | ||
| + | FROM lofar-pipeline: | ||
| + | |||
| + | COPY my_extension / | ||
| + | </ | ||
| + | |||
| + | Finally, you run < | ||
| + | |||
| + | === Q: How do I add initialisation stuff? (PYTHONPATH, | ||
| + | |||
| + | A: Our Docker images execute ''/ | ||
| + | |||
| + | Note: if you add eggs to the image, you need to put the egg // | ||