NOTE: some FORTRAN files were modified at CDS to ensure an edition
of the result to the standard output (required for the usage behind
a HTTP server). The original files were renamed xxx_ori.f

drwxr-xr-x 3 cds cds 4096 Dec 15 2013 [Up] drwxr-xr-x 2 cds cds 4096 Apr 25 2009 [TAR file] -r--r--r-- 1 cds cds 639 Apr 25 2009 Makefile -r--r--r-- 1 cds cds 302323 Mar 30 1998 OVS0001 -r--r--r-- 1 cds cds 321125 Mar 30 1998 OVS0003 -r--r--r-- 1 cds cds 328235 Mar 30 1998 OVS001 -r--r--r-- 1 cds cds 342613 Mar 30 1998 OVS004 -r--r--r-- 1 cds cds 352093 Mar 30 1998 OVS01 -r--r--r-- 1 cds cds 358729 Mar 30 1998 OVS02 -r--r--r-- 1 cds cds 361573 Mar 30 1998 OVS03 -r--r--r-- 1 cds cds 7688 Apr 25 2009 README -r--r--r-- 1 cds cds 7413 Aug 19 1998 README.ori -r--r--r-- 1 cds cds 149001 Mar 25 1998 STD0001 -r--r--r-- 1 cds cds 155795 Mar 25 1998 STD0003 -r--r--r-- 1 cds cds 158165 Mar 24 1998 STD001 -r--r--r-- 1 cds cds 160377 Mar 25 1998 STD004 -r--r--r-- 1 cds cds 349380 Mar 23 1998 STD01 -r--r--r-- 1 cds cds 354752 Mar 23 1998 STD02 -r--r--r-- 1 cds cds 354752 Mar 23 1998 STD03 -r--r--r-- 1 cds cds 320136 Dec 12 1997 UBVRI.Kur -r--r--r-- 1 cds cds 320136 Dec 12 1997 UBVRI.LBC -r--r--r-- 1 cds cds 28206 Mar 18 1998 ZAMS0001 -r--r--r-- 1 cds cds 28206 Mar 18 1998 ZAMS0003 -r--r--r-- 1 cds cds 28206 Mar 17 1998 ZAMS001 -r--r--r-- 1 cds cds 28206 Mar 17 1998 ZAMS004 -r--r--r-- 1 cds cds 28206 Mar 17 1998 ZAMS01 -r--r--r-- 1 cds cds 28206 Mar 17 1998 ZAMS02 -r--r--r-- 1 cds cds 28206 Mar 17 1998 ZAMS03 -r--r--r-- 1 cds cds 438 Mar 19 1998 indx.f -r--r--r-- 1 cds cds 1433 Mar 19 1998 intplz.f -r--r--r-- 1 cds cds 1836 Apr 25 2009 iso.f -r--r--r-- 1 cds cds 1495 Aug 19 1998 iso_ori.f -r--r--r-- 1 cds cds 6744 Mar 19 1998 isochr.f -r--r--r-- 1 cds cds 453 Aug 19 1998 makefile.ori -r--r--r-- 1 cds cds 4604 Mar 24 1998 mkgrid.f -r--r--r-- 1 cds cds 2993 Aug 19 1998 rdgrid.f -r--r--r-- 1 cds cds 2400 Mar 19 1998 track.f -r--r--r-- 1 cds cds 1627 Apr 25 2009 trk.f -r--r--r-- 1 cds cds 1264 Aug 19 1998 trk_ori.f -r--r--r-- 1 cds cds 2302 Aug 19 1998 ubvcol.f
Beginning of README : NOTE: some FORTRAN files were modified at CDS to ensure an edition of the result to the standard output (required for the usage behind a HTTP server). The original files were renamed xxx_ori.f ================================================================================ Contents: -------- This package contains 3 sets of files that allow the construction of isochrones for arbitrary age and metallicity: (1) evolution tracks and ZAMS models, as described in the paper by Pols, Schroder, Tout, Hurley & Eggleton (1998, MNRAS, 298, 525). (2) synthetic bolometric corrections and UBVRI colours, for the conversion of (L,Teff) to broadband magnitudes and colours. (3) subroutines for reading the above data and interpolating tracks and constructing isochrones. file: description: OVS0001 ... OVS03 evolution tracks with `overshooting', delta(OV)=0.12, for Z=0.0001 to 0.03 (7 files), M=0.5...50 Msol STD0001 ... STD03 'standard' evolution tracks, delta(OV)=0, for Z=0.0001 to 0.03 (7 files), M=0.5...2.0 Msol (Z<=0.004) or M=0.5...40 Msol (Z>=0.01) ZAMS0001 ... ZAMS03 ZAMS models for Z=0.0001 to 0.03 (7 files), M=0.1...100 Msol UBVRI.Kur table of synthetic BC and UBVRI colours, from Kurucz model atmospheres (1992, IAU Symp 149, p.225) UBVRI.LBC empirically corrected version of the above, from Lejeune, Cuisinier & Buser (1997, A&AS 125, 229) indx.f ... ubvcol.f 9 FORTRAN77 subroutines for grid assembly, track interpolation and isochrone construction makefile makefile for compilation Introduction: ------------ Two sets of evolution tracks are provided, one (OVS) computed with extended mixing or `overshooting', the other (STD) without. As discussed in our paper (cited above), empirical tests show that the OVS tracks should be preferred for M >= 1.6 Msol, but that the assumed amount of overshooting is too large for lower masses. For M <= 1.0 Msol, however, both sets of models are essentially the same. For consistency, it would be best to use the OVS models over the entire range, but this may lead to an erroneus location of the main-sequence hook in the mass range 1.0 - 1.6 Msol. Perhaps the best compromise would be to interpolate in this mass range by using a `hybrid' grid as described below. Each stellar model in the grids is represented by one line of information, i.e.: [column 1] equivalent model number (referring to the evolutionary state, as described in the paper), [2] actual model number in output of the evolution run, [3] age (yrs) , [4] log of effective temperature (K), [5] log luminosity (Lsun), [6] log radius (Rsun), [7] helium core mass (Msun; defined as the mass shell where X=0.1), [8] carbon/oxygen core mass (Msun; mass shell where Y=0.1), [9] dimesionless moment of inertia k^2 = I/(MR^2), [10] log of central temerature (K), [11] log of central density (g cm^-3), [12-16] central mass fractions of H1, He4, C12, N14 and O16, [17-21] surface mass fractions of the same. Finally, it should be kept in mind that, if the isochrones will be used for comparison with broadband magnitudes and colours, the colour conversion is an important intermediate step and a source of uncertainty, especially for cool stars. Two tables are provided for this conversion, without warranty. In the present version, the empirically corrected Kurucz tables are read from file UBVRI.LBC. If preferred, this can be changed to read the original Kurucz tables, but in principle any other method can be used to make the colour conversion. Instructions for use: -------------------- To use the provided subroutines for interpolating evolution tracks and constructing isochrones, first the appropriate evolution grid must be assembled from the data files. This is done with the program MKGRID, which is compiled with the command `make mkgrid'. You can specify upon running the program: * whether the STD models, the OVS models or a hybrid (HYB) grid is to be used. The HYB grid is assembled from OVS models for M >= 1.6 Msun, and STD models for M <= 1.4 Msun up to the He flash. For post He-flash models, OVS models are used for all masses (because all such low-mass models contain a 0.5 Msun He core and their physical structure is very similar); * the required range of metallicities and masses; * the amount of detail required: only global properties (up to column 6 above), interior structure data (up to column 11), composition data (all columns). MKGRID creates the files EVOLGRID and ZAMSGRID. The last specifications are to avoid creating, and having to read, very large tables, when the application requires only a limited M or Z range or a limited amount of detail. For example, the subroutines for the construction of isochrones only use the global properties. At installation of the other routines, the values of character string DIREC in subroutines RDGRID and RDUBVI should be changed to the appropriate directory paths where the data files are placed. In the application program, these two subroutines should be called first to read the data. RDGRID returns the type of grid it has read from EVOLGRID as a 3-letter code. Subroutine TRACK has two input arguments: MLOG = log(M/Msun) and ZLOG = log(Z/0.02). It first calls subroutine INTPLZ to interpolate in Z; if many tracks are interpolated for a single Z value it is much more efficient to call INTPLZ outside TRACK. The output is stored in COMMON block TRKDAT, i.e. for each equivalent model number: age, log Teff, log L, log R, mass, M_V (abs.vis.magnitude), U-B, B-V, V-R, V-I, and the total number of points. Subroutine ISOCHR has four input arguments: AJ = age (in yrs), ZLOG = log(Z/0.02), MLMIN = minimum log(mass/Msol), MLMAX = maximum log(mass/Msol). The last two parameters allow computation over a limited mass range; making MLMIN very small and MLMAX very large produces an isochrone over the whole mass range of the evolution grid. The output is stored in COMMON block ISODAT, i.e. for each point along the isochrone: zero-age mass, actual mass, log Teff, log L, log R, M_V, U-B, B-V, V-R, V-I, equivalent model number, and the total number of points. (The equivalent model number referes to the evolutionary status.) Examples: -------- The programs TRK and ISO serve as examples of the kind of output generated by TRACK and ISOCHR respectively, as well as of how the subroutines can be implemented in other programs. To use them, compile the codes with the commands 'make trk' and `make iso'. Both programs require 2 input arguments on the command line. For TRK, specify M/Msun and Z, e.g.: > trk 1.63 0.0072 produces an evolution track for 1.63 Msun and Z=0.0072. For ISO, specify log(age) and [Fe/H], e.g.: > iso 9.0 -0.22 produces an isochrone for 10^9 yrs with [Fe/H] = -0.22. Notes: ----- Please note the following incompletenesses: * At present no mass loss is taken into account, but it can be included in a simplified way for giants. I hope to modify the code to include this in the near future. * The tracks usually extend up to the start of double-shell burning, i.e. the start of the TP-AGB. Some tracks extend further, but not always to the same equivalent point, so that the interpolation beyond the early-AGB (model 129) can be a bit erratic. However, these late-AGB models are very simplified in any case because they do not include thermal pulses. * The UBVRI tables only extend down to Teff = 3500 K. The code extrapolates to lower temperatures, leading to (probably) erroneous results for the M_V and colours of the coolest models. Lejeune et al also give BC and colours for M giants and M dwarfs but these have not (yet) been incorporated in the present tables.