, but this code // executes before the first paint, when

ÃÛÌÒapp

is not yet present. The // classes are added to so styling immediately reflects the current // toolbar state. The classes are removed after the toolbar completes // initialization. const classesToAdd = ['toolbar-loading', 'toolbar-anti-flicker']; if (toolbarState) { const { orientation, hasActiveTab, isFixed, activeTray, activeTabId, isOriented, userButtonMinWidth } = toolbarState; classesToAdd.push( orientation ? `toolbar-` + orientation + `` : 'toolbar-horizontal', ); if (hasActiveTab !== false) { classesToAdd.push('toolbar-tray-open'); } if (isFixed) { classesToAdd.push('toolbar-fixed'); } if (isOriented) { classesToAdd.push('toolbar-oriented'); } if (activeTray) { // These styles are added so the active tab/tray styles are present // immediately instead of "flickering" on as the toolbar initializes. In // instances where a tray is lazy loaded, these styles facilitate the // lazy loaded tray appearing gracefully and without reflow. const styleContent = ` .toolbar-loading #` + activeTabId + ` { background-image: linear-gradient(rgba(255, 255, 255, 0.25) 20%, transparent 200%); } .toolbar-loading #` + activeTabId + `-tray { display: block; box-shadow: -1px 0 5px 2px rgb(0 0 0 / 33%); border-right: 1px solid #aaa; background-color: #f5f5f5; z-index: 0; } .toolbar-loading.toolbar-vertical.toolbar-tray-open #` + activeTabId + `-tray { width: 15rem; height: 100vh; } .toolbar-loading.toolbar-horizontal :not(#` + activeTray + `) > .toolbar-lining {opacity: 0}`; const style = document.createElement('style'); style.textContent = styleContent; style.setAttribute('data-toolbar-anti-flicker-loading', true); document.querySelector('head').appendChild(style); if (userButtonMinWidth) { const userButtonStyle = document.createElement('style'); userButtonStyle.textContent = `#toolbar-item-user {min-width: ` + userButtonMinWidth +`px;}` document.querySelector('head').appendChild(userButtonStyle); } } } document.querySelector('html').classList.add(...classesToAdd); })(); Prediction of a red nova outburst in KIC 9832227 - News & Stories | ÃÛÌÒapp

ÃÛÌÒapp

Skip to main content

Publications

Prediction of a red nova outburst in KIC 9832227

Wed, Apr 26, 2017
{}

We present the first identification of a candidate precursor for an imminent red nova. Our prediction is based on the example of the precursor to the red nova V1309 Sco, which was retrospectively found to be a contact binary with an exponentially decreasing period. We explore the use of this distinctive timing signature to identify precursors, developing the observational and analysis steps needed. We estimate that our Galaxy has roughly 1–10 observable precursors. Specifically, we lay out the observational case for KIC 9832227, which we identified as a tentative candidate two years ago (Molnar et al. 2015, AAS Meeting #225 Abstracts 415.05). Orbital timing over the past two years has followed the tentative exponential fit. As of late 2015, the period time derivative went beyond the range found in other systems ($\dot{P}\lt | 1\times {10}^{-8}| $), a necessary criterion for a serious candidate. We estimate time of merger is the year 2022.2Ìý±Ìý0.7. Double absorption line spectra confirm directlyÌýthe 0.458-dayÌýlight-curve is the orbital period of a contact binary system and yield a mass ratioÌý${m}_{B}/{m}_{A}=0.228\pm 0.003$. Closer analysis of theÌýKeplerÌýtiming data shows evidence of a component C with orbital periodÌý${P}_{C}=590\pm 8$Ìýdays andÌý${m}_{C}\sin {i}_{C}=0.11\,{M}_{\odot }$. An alternative interpretation of the long-term timing trend, that is, aÌýlight travel-time delay due to theÌýorbit around a distant component D, is ruled out by the spectroscopic data for any nondegenerate star. Additional measurements are needed to test further the merging hypothesis and to use fully this fortuitous opportunity.