J/A+A/624/A88ivo://CDS.VizieR/J/A+A/624/A88doi:10.26093/cds/vizier.36240088CDSAndersen J.Torres G.Clausen J.V.2019-05-06T15:41:51Z2019-04-23T08:44:51ZCDS support team

CDS, Observatoire de Strasbourg, 11 rue de l'Universite, F-67000 Strasbourg, France

cds-question@unistra.freclipsing-binary-starsccd-photometryvisible-astronomymedium-band-photometryOne of the greatest uncertainties in modelling the mass-exchange phases during the evolution of a binary system is the amount of mass and angular momentum that has been lost from the system. In order to constrain this problem, a favourable, evolved and detached real binary system is valuable as an example of the end result of this process. We study the 52-day post-mass-exchange eclipsing binary V643 Ori from complete uvby light curves and high-resolution spectra. V643 Ori is double-lined and shows total primary eclipses. The orbit is accurately circular and the rotation of both stars synchronised with the orbit, but the photometry from a single year (1993) shows signs of weak spot activity (0.02mag) around the primary eclipse. We determine accurate masses of 3.3 and 1.9M_{sun}_ from the spectroscopic orbit and solve the four light curves to determine radii of 16 and 21R_{sun}_, using the Wilson-Devinney photometric code. The rotational velocities from the cross-correlation profiles agree well with those computed from the known radii and orbital parameters. All observable parameters are thus very precisely determined, but the masses and radii of V643 Ori are incompatible with undisturbed post-main-sequence evolution. We have attempted to simulate the past evolutionary history of V643 Ori under both conservative and non-conservative Case B mass transfer scenarios. In the non-conservative case we varied the amounts of mass and angular momentum loss needed to arrive at the present masses in a circular 52-day orbit, keeping the two stars detached and synchronized as now observed, but without following the evolution of other stellar properties in any detail. Multiple possible solutions were found. Further attempts were made using both the BSE formalism and the binary MESA code in order to track stellar evolution more closely, and make use of the measured radii and temperatures as important additional constraints. Those efforts did not yield satisfactory solutions, possibly due to limitations in handling mass transfer in evolved stars such as these. We remain hopeful that future theoreticians can more fully model the system under realistic conditions.2019A&A...624A..88Ahttps://cdsarc.cds.unistra.fr/viz-bin/cat/J/A+A/624/A88CatalogResearchIsServedByTAP VizieR generic servicehttps://cds.unistra.fr/vizier-org/licences_vizier.htmlhttps://vizier.cds.unistra.fr/viz-bin/VizieR-2?-source=J/A+A/624/A88https://vizier.iucaa.in/viz-bin/VizieR-2?-source=J/A+A/624/A88http://vizieridia.saao.ac.za/viz-bin/VizieR-2?-source=J/A+A/624/A88https://vizier.cds.unistra.fr/viz-bin/votable?-source=J/A+A/624/A88https://vizier.iucaa.in/viz-bin/votable?-source=J/A+A/624/A88http://vizieridia.saao.ac.za/viz-bin/votable?-source=J/A+A/624/A88GETtext/xml+votablehttps://tapvizier.cds.unistra.fr/TAPVizieR/tapOpticaldefaultJ/A+A/624/A88/table3uvby photometry of V643 OrirecnoRecord number assigned by the VizieR team. Should Not be used for identification.meta.recordintHJDHeliocentric Julian day (HJD-2400000)dtime.epoch;pos.heliocentricdoubleDumagDifferential u magnitudemagphot.mag;em.opt.U;arith.difffloatDvmagDifferential v magnitudemagphot.mag;em.opt.B;arith.difffloatDbmagDifferential b magnitudemagphot.mag;em.opt.B;arith.difffloatDymagDifferential y magnitudemagphot.mag;em.opt.V;arith.difffloatJ/A+A/624/A88/listspList of fits spectrarecnoRecord number assigned by the VizieR team. Should Not be used for identification.meta.recordintNxNumber of pixels along X-axismeta.numberintObs.DateObservation datestime.epoch;obsnullableblambdaLower value of wavelength interval0.1nmem.wl;stat.minfloatBlambdaLower value of wavelength interval0.1nmem.wl;stat.maxfloatdlambdaSpectral resolution0.1nmspect.resolutiondoublesizeSize of FITS fileKibytephys.size;meta.fitsintspShow the spectrummeta.ref.urlcharFileNameName of FITS file, in subdirectory fitsmeta.id;meta.fitschar