Table B.1.
3DB input parameters and characteristics of data cubes.
| Galaxy | Beam | Δv | σch | σtot | Rmax | ΔR | centre RA | centre DEC | Vsys | norm |
|---|---|---|---|---|---|---|---|---|---|---|
| (″) | ( km s−1) | (mJy beam−1) | (kpc) | (pc) | (hh mm ss.s) | (dd mm ss) | ( km s−1) | |||
| (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) | |
| DDO 154 | 21 × 21 | 2.6 | 1.366 | 6.3 | 8.3 | 412 | 12 54 6.35 | 27 09 0.5 | 375.2 | L |
| IC 2574 | 22 × 22 | 2.6 | 1.793 | 10 | 9.6 | 418 | 10 28 23.5 | 68 24 44 | 44.9 | L |
| NGC 0925 | 9 × 9 | 2.6 | 0.820 | 5.002 | 16.1 | 401 | 02 27 16.9 | 33 34 45 | 546.3 | L |
| NGC 2403 | 27 × 27 | 5.2 | 0.0326 | 0.154 | 19 | 413 | 07 36 51.4 | 65 36 09 | 133.2 | L |
| NGC 2841 | 6.06 × 5.79 | 5.2 | 0.3917 | 2.745 | 46.8 | 410 | 09 22 02.6 | 50 58 35 | 633.7 | A |
| NGC 2976 | 23 × 23 | 5.2 | 0.934 | 3.769 | 3.2 | 400 | 09 47 15.4 | 67 54 59 | 1.1 | L |
| NGC 3198 | 7.64 × 5.62 | 5.2 | 0.382 | 0.198 | 31.4 | 474 | 10 19 54.9 | 45 32 59 | 657 | A |
| NGC 4736 | 18 × 18 | 5.2 | 0.895 | 4.502 | 7.8 | 410 | 12 50 53.0 | 41 07 14 | 306.7 | L |
| NGC 5055 | 9 × 9 | 5.2 | 0.499 | 2.839 | 33.3 | 432 | 13 15 49.3 | 42 01 45 | 496.7 | L |
| NGC 6946 | 15 × 15 | 2.6 | 1.556 | 10.179 | 14.5 | 402 | 20 34 52.3 | 60 09 14 | 48.7 | L |
| NGC 7331 | 4.94 × 4.6 | 5.2 | 0.505 | 3.318 | 24.8 | 357 | 22 37 04.0 | 34 24 56 | 818.3 | A |
| NGC 7793 | 24 × 24 | 2.6 | 2.343 | 16.634 | 7.14 | 420 | 23 57 49.8 | −32 35 28 | 226.2 | A |
Notes. The table lists: (1) beam size of the data cube (NGC 2841, NGC 3198, and NGC 7331 are at the original resolution); (2) channel width; (3) noise in the channels; (4) noise in the total map; (5) outermost fitted radius; (6) sampling radius; (7,8) centre coordinate; (9) systemic velocity; and (10) normalisation method (L=local, A=azimuthal).
Current usage metrics show cumulative count of Article Views (full-text article views including HTML views, PDF and ePub downloads, according to the available data) and Abstracts Views on Vision4Press platform.
Data correspond to usage on the plateform after 2015. The current usage metrics is available 48-96 hours after online publication and is updated daily on week days.
Initial download of the metrics may take a while.