4.0
4.0
No changes since 4.0rc1.
Changes since 3.1.1
frequency band logic change
the band determination logic has changed. Before all bands where split
into 1 MHz intervals and associated as such. With this release images
are put in the same band if their bandwidths overlap.
We added an option to limit the bandwidth used for band association
(#492). Limiting the bandwidth for an image is done by
setting bandwidth_max in job_params.cfg under the
persistence section. E.g.:
[persistence]
bandwidth_max = 0.0
Setting the value to 0.0 will use the bandwidth defined in the image
headers, a non 0.0 value will override this value.
added streaming telescope support
The internals of TraP have been rewritten to support streaming AARTFAAC
data (#483). There is now a new section in the job_params.cfg file
with a mode setting. Setting this to batch will keep the old TraP
behavior, but setting mode to streamwill enable switch TraP
to streaming mode. TraP will connect to a network port and process
images from the network until terminated.
The hosts and ports where to connect to is controlled with the hosts
and ports settings:
[pipeline]
mode = 'stream'
hosts = 'struis.science.uva.nl,struis.science.uva.nl'
ports = '6666,6667'
The batch mode should mostly be unaffected, only the order of actions
has changed. TraP will process the full dataset now in chunks grouped by
timestamp. The storing of images, quality checks and meta data
extraction is now run together with the source extraction and association
cycle, where before this was all done at the start of a TraP run.
This makes it more similar to how we process streaming data and enabled
other optimisations in the future (like keeping images in memory per
timestamp group).
Removal of MongoDB image store
If you enable the copy_images setting in your pipeline.cfg file
the images are now stored in the sql database (#534). This makes it
much easier to manage the files, for example delete them. Also the
images load faster in banana. This makes setting up and configuring
MongoDB obsolete.
Add command line option to delete dataset
It is now possible to delete a dataset and its associated images (#533)::
$ trap-manage.py deldataset 5 -y
dataset 5 has been deleted!
Make TraP more resilient against faulty data
TraP often crashed on faulty image data. On popular request TraP will
now try to continue, giving a warning. #522
Various other changes and bugfixes
- Fix Numpy 1.9+ compatibility #509
- TraP sourcefinder error on updated AARTFAAC images #505
- forced fits is not parallelised #526
- restructure logging, make less verbose. Also multiproc workers will
log to stdout. - fix multiprocess job cancelling problem (ctrl-c)