SoFiA (inactive)

Duplicate of #102 which will be closed as it is less detailed. There is one significant issue here, which is a cube where the restoring beam varies from channel to...

Filtering based on the total number of pixels and the overall filling factor has been implemented (see d53414d3a96fc9b2d0bc3bc261fee92c46e6afb6). New parameter settings are available to control this: `linker.minPixels`, `linker.maxPixels`, `linker.minFill` and...

As discussed at our source finding meeting, the cube needs to be inverted for the algorithms in SoFiA to work correctly, including parameterisation and moment map generation. However, as discussed,...

Why would this result in non-deterministic behaviour? I would have thought that when you run the same code on the same data on the same machine with the same settings,...

Thank you for reporting the flux issue. My understanding is that you are changing the region size (parameter `input.region`) while leaving all of the other settings the same. Small variations...

As a first step towards this goal I have modified the code that generates integrated spectra to include another column that lists the number of spatial pixels contributing to the...

Thank you for reporting this problem. Indeed, SoFiA currently only checks for `Jy/beam` and common misspellings such as `JY/BEAM` or `Jy/Beam`, as this is the standard format used by most...

@spectram: Thank you for clarifying the w20 and w50 issue. If I understand this correctly, then the line widths are still correct, but specified in channels rather than physical frequency...

We discussed this issue at our recent SoFiA developer‘s meeting this week and have decided to implement a check for a few additional strings that correspond to the same unit...

Thanks for that suggestion. In principle one could retain the third axis with a size of just 1 pixel and then keep all of the 3rd-axis header information, although this...