Table 5.
Stellar parameters predicted by the FUNS code and from the HR diagram analysis of the OCs for the stars in the sample.
Star | Cluster | Mstar | Mbol | [M/H] | TDU | Mcore | Mto | Mfinal | log (age) |
---|---|---|---|---|---|---|---|---|---|
(M⊙) | (mag) | (dex) | (M⊙) | (M⊙) | (M⊙) | (a) | |||
Case 63 | Berkeley 9 | 1.80 | −4.67 | −0.10 | 3 | 0.585 | 1.75±0.25 | 0.620 | 9.25±0.19 |
HD 292921 | Berkeley 34 | 1.50 | −4.54 | −0.19 | 2 | 0.578 | 1.65±0.35 | 0.630 | 9.33±0.23 |
Case 473 | Berkeley 53 | 1.50 | −4.75 | 0.12 | 7 | 0.590 | 1.50±0.20 | 0.632 | 9.51±0.04 |
Case 121 | Berkeley 72 | 2.00 | −4.70 | −0.18 | 4 | 0.587 | 2.25±0.25 | 0.634 | 8.97±0.10 |
Case 588 | Dias 2 | 1.30 | −4.80 | −0.90 | 5 | 0.600 | 1.30±0.20 | 0.635 | 9.52±0.04 |
IRAS 19582+2907 | FSR 0172 | 3.00 | −5.10 | 0.00 | 7 | 0.625 | 3.25±0.75 | 0.723 | 8.59±0.30 |
HD 11800 | NGC 743 | 5.00 | −4.51 | 0.00 | e-AGB | 0.635 | 5.00±1.00 | 0.873 | 8.06±0.23 |
[D75b] Star30 | NGC 1798 | 2.50 | −4.70 | 0.00 | 4 | 0.616 | 2.00±0.50 | 0.628 | 9.21±0.23 |
BD +60 2534 | NGC 7654 | 6.00 | −4.50 | 0.00 | e-AGB | 0.707 | 5.00±1.00 | 0.873 | 8.06±0.23 |
MSB 75 | NGC 7789 | 1.50 | −4.80 | −0.27 | 4 | 0.590 | 1.75±0.25 | 0.635 | 9.25±0.15 |
C* 908 | Ruprecht 37 | 1.30 | −4.63 | −0.40 | 2 | 0.590 | 1.40±0.10 | 0.632 | 9.47±0.10 |
CSS 0291 | Tombaugh 1 | 2.00 | −4.50 | −0.17 | 2 | 0.582 | 1.75±0.25 | 0.631 | 9.31±0.25 |
Notes. Mcore is the current core mass at the specified luminosity. The theoretical Mbol and [M/H] values should be compared with those determined observationally in Table 4 (column 5) and Table 3 (column 4), respectively. Column 6 indicates the number of TDUs episodes in the theoretical model during the TP-AGB phase for which we find agreement between the observed and predicted abundances according to the FRUITY database (see text).
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.