Volume 569, September 2014
|Number of page(s)||16|
|Published online||01 October 2014|
In Sect. 4.3 we discuss possible explanations of the jet widening (“tuning fork”), together with a decrease in surface brightness that appears to be stationary over the TANAMI monitoring period. The jet flow is likely to be disturbed by an obstacle. In the main text we conclude that a scenario including a red giant with a significant stellar wind is favored by our calculations and observations. In the following, we summarize the corresponding calculations when assuming the obstacle is a cloud.
The shock produced in the cloud by the interaction with the jet should propagate through it in a longer time than the penetration and crossing time if we expect the cloud to cross the whole jet diameter. Otherwise, the cloud would be disrupted by the shock when it has completely crossed it, and the bow-shock structure would have disappeared (Araudo et al. 2010; Bosch-Ramon et al. 2012). Knowing that the obstacle has been within the jet for at least ten years, hence a cloud shocking time of tcs> 3.1 × 108 s, we can therefore use Eq. (4) in Araudo et al. (2010) to give a lower limit of the density of the cloud: (A.1)where we have taken the distance to the core z = 1 pc = 3.1 × 1018 cm as a reference. Taking the aforementioned lower limit on time into account and taking as input data the obstacle radius Rc = 10-3 pc, the jet power from the literature (Lj ≃ 1044 erg s-1, Abdo et al. 2010), and the location of the “tuning fork” along the jet z ≃ 0.4 pc, we can give a limit on the cloud density: (A.2)
Rivers et al. (2011) report an occultation of the central core for 170 days owing to the passage of a discrete clump of material through the line of sight in the context of a clumpy torus model. We suggest that the eclipse is short because the angular size of the eclipsed region must be small. Interestingly, for the hypothetical clump, which is located at a similar distance to the core to what is reported for the location of the “tuning fork” (0.1...0.3 pc, adopting measurements by Meisenheimer et al. 2007), they obtain a central density of nclump = (1.8−3.0) × 107 cm-3 and a size of Rclump = (1.4−2.4) × 1015 cm. The size of the clump would agree with our result, but the density we obtain, as required for the cloud to survive the interaction for ten years, is three orders of magnitude higher. In addition, the cloud velocity estimated by Rivers et al. (2011) is one order of magnitude lower than the one we used for our calculations (vclump ≃ 1000 km s-1, Eq. (3)). Such a decrease in the velocity would have two effects: 1.) the crossing time would be increased by a factor of ten in Eq. (3), i.e., tj ≃ 6.2 × 109 s (approximately two hundred years); and 2.) owing to this increase in the crossing time, the lower limit in the cloud density obtained in Eq. (A.2) would be increased by a factor of 100, bringing it to nc> 1.5 × 1012 cm-3. Following the result of Rivers et al. (2011), we could thus conclude that the cloud scenario should be ruled out for the “tuning fork” because: 1) it is difficult to expect clumps with higher densities at greater distances from the nucleus; and 2) the shock crossing time of the cloud, given by Eq. (A.1), would be reduced by a factor 20 with the numbers given in that paper for the cloud density, thus giving tcs ≃ 3.4 × 107 s (about one year). This means that clumps of the size and density, such as those obtained by Rivers et al. (2011) for the case of a clumpy torus, would survive for about one year before being disrupted and mixed with the jet if they come to collide with it; i.e., they would be destroyed close to the jet boundary, provided that their tj is ~200 years. Therefore, this scenario cannot explain the steady situation that is observed at the “tuning fork”.
Modelfit parameters for individual jet components.
© ESO, 2014
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.