2019A&A...632A.110Y


Query : 2019A&A...632A.110Y

2019A&A...632A.110Y - Astronomy and Astrophysics, volume 632A, 110-110 (2019/12-0)

The star formation timescale of elliptical galaxies. Fitting [Mg/Fe] and total metallicity simultaneously.

YAN Z., JERABKOVA T. and KROUPA P.

Abstract (from CDS):

The alpha element to iron peak element ratio, for example [Mg/Fe], is a commonly applied indicator of the galaxy star formation timescale (SFT) since the two groups of elements are mainly produced by different types of supernovae that explode over different timescales. However, it is insufficient to consider only [Mg/Fe] when estimating the SFT. The [Mg/Fe] yield of a stellar population depends on its metallicity. Therefore, it is possible for galaxies with different SFTs and at the same time different total metallicity to have the same [Mg/Fe]. This effect has not been properly taken into consideration in previous studies. In this study, we assume the galaxy-wide stellar initial mass function (gwIMF) to be canonical and invariant. We demonstrate that our computation code reproduces the SFT estimations of previous studies, where only the [Mg/Fe] observational constraint is applied. We then demonstrate that once both metallicity and [Mg/Fe] observations are considered, a more severe "downsizing relation" is required. This means that either low-mass ellipticals have longer SFTs (>4Gyr for galaxies with mass below 1010M) or massive ellipticals have shorter SFTs (~=200Myr for galaxies more massive than 1011M) than previously thought. This modification increases the difficulty in reconciling such SFTs with other observational constraints. We show that applying different stellar yield modifications does not relieve this formation timescale problem. The quite unrealistically short SFT required by [Mg/Fe] and total metallicity would be prolonged if a variable stellar gwIMF were assumed. Since a systematically varying gwIMF has been suggested by various observations this could present a natural solution to this problem.

Abstract Copyright: © ESO 2019

Journal keyword(s): galaxies: formation - galaxies: abundances - galaxies: evolution - galaxies: elliptical and lenticular, cD - galaxies: star formation - galaxies: stellar content

Simbad objects: 1

goto Full paper

goto View the references in ADS

Number of rows : 1
N Identifier Otype ICRS (J2000)
RA
ICRS (J2000)
DEC
Mag U Mag B Mag V Mag R Mag I Sp type #ref
1850 - 2024
#notes
1 NAME DGSAT I G 01 17 35.590 +33 31 42.37           ~ 32 0

Query : 2019A&A...632A.110Y

Basic data :
NAME DGSAT I -- Galaxy
Origin of the objects types :

(Ref) Object type as listed in the reference "Ref"
(acronym) Object type linked to the acronym according to the original reference
() Anterior to 2007, before we can link the objet type to a reference, or given by the CDS team in some particular cases

Other object types:
G (2016AJ)
Syntax of coordinates is : "ra dec (wtype) [error ellipse] quality bibcode" :
  • ra dec : right ascension and declination (unit and frame defined according to your Output Options)
    Grey values are increasing the original precision due to the computation of frame transformations
  • (wtype) : wavelength class for the origin of the coordinates (Rad, mm, IR, Optical, UV, Xray, Gam)
  • [error ellipse] : measurement uncertainty, on (ra,dec) if the positional angle is 90 degrees, on (majaxis,minaxis) otherwise (in mas at defined epoch in the original catalogue),
    position angle (in degrees North celestial pole to East)
  • quality : flag of quality
    • E ≥ 10"
    • D : 1-10" (and some old data)
    • C : 0.1-1"
    • B : 0.01-0.1" + 2MASS, Tyc
    • A : VLBI, Hipparcos
  • bibcode : bibcode of the coordinates reference
ICRS coord. (ep=J2000) :
01 17 35.590 +33 31 42.37 [ ] D 2016AJ....151...96M
Syntax of coordinates is : "ra dec (wtype) [error ellipse] quality bibcode" :
  • ra dec : right ascension and declination (unit and frame defined according to your Output Options)
    Grey values are increasing the original precision due to the computation of frame transformations
  • (wtype) : wavelength class for the origin of the coordinates (Rad, mm, IR, Optical, UV, Xray, Gam)
  • [error ellipse] : measurement uncertainty, on (ra,dec) if the positional angle is 90 degrees, on (majaxis,minaxis) otherwise (in mas at defined epoch in the original catalogue),
    position angle (in degrees North celestial pole to East)
  • quality : flag of quality
    • E ≥ 10"
    • D : 1-10" (and some old data)
    • C : 0.1-1"
    • B : 0.01-0.1" + 2MASS, Tyc
    • A : VLBI, Hipparcos
  • bibcode : bibcode of the coordinates reference
FK4 coord. (ep=B1950 eq=1950) :
01 14 47.458 +33 15 55.15 [ ]
Syntax of coordinates is : "ra dec (wtype) [error ellipse] quality bibcode" :
  • ra dec : right ascension and declination (unit and frame defined according to your Output Options)
    Grey values are increasing the original precision due to the computation of frame transformations
  • (wtype) : wavelength class for the origin of the coordinates (Rad, mm, IR, Optical, UV, Xray, Gam)
  • [error ellipse] : measurement uncertainty, on (ra,dec) if the positional angle is 90 degrees, on (majaxis,minaxis) otherwise (in mas at defined epoch in the original catalogue),
    position angle (in degrees North celestial pole to East)
  • quality : flag of quality
    • E ≥ 10"
    • D : 1-10" (and some old data)
    • C : 0.1-1"
    • B : 0.01-0.1" + 2MASS, Tyc
    • A : VLBI, Hipparcos
  • bibcode : bibcode of the coordinates reference
Gal coord. (ep=J2000) :
129.164522 -29.026586 [ ]
Syntax of radial velocity (or/and redshift) is : "value [error] (wavelength) quality bibcode"
  • value : radial velocity or/and redshift (Heliocentric frame) according to your Output Options
    (redshift may be not displayed if the data value is <0 and the database inside value is a radial velocity)
  • [error] : error of the corresponding value displayed before
  • (wavelength) : wavelength range of the measurement : Rad, mm, IR, Opt, UV, Xray, Gam or  '∼'(unknown)
  • quality : flag of quality ( A=best quality -> E=worst quality, ∼=unknown quality)
  • bibcode : bibcode of the value's origin
Radial velocity / Redshift / cz :
V(km/s) 5450 [40] / z(~) 0.018348 [0.000133] / cz 5500.45 [40.00]
   D 2016AJ....151...96M
SIMBAD within arcmin
', {sourceSize:12, color:'#30a090'})); aladin.on('objectClicked', function(object) { var objName=object.data.MAIN_ID; aladin.showPopup(object.ra,object.dec,'',''+ objName+''); });" title="Show Simbad objects"> Overlay Simbad points in this preview
Back
All CDSPortal (CDSPortal)

Send to sendBySAMP sendBySAMP

sedIcon
within arcsec The VizieR photometry tool allows for easy visualization of photometry points extracted around the Simbad position from photometry-enabled catalogues in VizieR.
The search radius has to be specified by the user. It is currently limited to a maximum of 30 arcsec. It depends mostly on the precision or quality of the coordinates (SIMBAD and VizieR catalogs), the resolution of the images from which the sources were extracted, source extent, and source crowding.
Suggestions are: crowded field: 0.5 to 1.5 arcsec, 3 arcsec otherwise; uncertain coordinates (SIMBAD quality E or coordinates without reference): 5 to 30 arsec (risky!).
sed-help-icon

The link on the acronym of the identifiers give access to the information for this acronym in the dictionary of nomenclature.
Identifiers (1) :
An access of full data is available using the icon Vizier near the identifier of the catalogue

NAME DGSAT I

References (32 between 1850 and 2024) (Total 32)
Simbad bibliographic survey began in 1850 for stars (at least bright stars) and in 1983 for all other objects (outside the solar system).
Follow new references on this object
                Reference summaries :

                from: to:

                 or select by : (not exhaustive, explanation here)


External archives :

Search by coordinates in Vizier (radius: 5 arcsec)


Annotations :
Annotations allow a user to add a note or report an error concerning the astronomical object and its data. It requires registration to post a note. See description .
Please, have a look at Best practices. The list of all annotations to SIMBAD objects can be found here .

Currently no annotations available

add an annotation to this object

report an error concerning the data of this object


To bookmark this query, right click on this link: simbad:objects in 2019A&A...632A.110Y and select 'bookmark this link' or equivalent in the popup menu