A core-collapse supernova occurs when the core of a massive evolved star loses stable pressure support and collapses. Iron-group nuclei no longer provide an exothermic fusion route, while electron capture and photodisintegration reduce electron pressure and consume energy. Collapse accelerates until nuclear-density matter stiffens the inner core and launches a shock. That shock loses energy to dissociation and neutrinos and can stall. Neutrino heating, aided by multidimensional flow, can revive it; sufficiently rapid rotation and magnetic stresses provide other possible channels. Most of the liberated compact-object binding energy escapes as neutrinos rather than optical light or ejecta kinetic energy.
Successful explosions can leave neutron stars, with additional fallback sometimes producing black holes. Failed explosions or very substantial fallback can form black holes more directly. Important theoretical uncertainties include progenitor structure and mass loss, nuclear equation of state, neutrino transport and interaction rates, convection and shock instabilities, rotation, magnetic fields and the relation between these effects and explosion asymmetry. A successful shock launch alone does not guarantee unbinding all overlying layers.
For an initially uniform-density iron core, . Assemble spherical shells from infinity:
At the supplied density , the numerical coefficient is about , consistent with the printed rounded estimate:
The negative sign represents the work recovered in assembling the bound core.
The ejecta binding energy of an initially uniform core is the negative gravitational energy of the outer shells in the original core, including their interaction with the material inside them. It is not the final neutron star's entire binding energy. With and , the shell integral gives
Adding the supplied dissociation cost, , gives
The calculation assumes the initial common density for the shell binding, all the indicated outer iron encounters the dissociating shock, and dissociation is charged as the stated energy cost. It does not subtract the much larger final compact-object binding energy as though all that energy were directly available to the ejecta. Later recombination can return some nuclear binding energy, and overlying noniron layers add their own energy requirements, so the table is a simplified shock-energy budget.
Compared with a characteristic explosion, ejecting a very thin remaining core layer is relatively easy in this estimate; is already demanding, and requires substantially more energy. More massive tightly bound cores therefore tend to make shock revival and complete ejection harder, increasing the possibility of fallback or failed explosions and black-hole remnants. A thin steep-gradient outer layer may allow a rapid, relatively weak explosion and a surviving neutron star.
A natal kick requires asymmetry of ejecta, neutrino emission or subsequent gravitational interaction, not merely a large scalar energy budget. Rapid relatively symmetric low-ejecta explosions can produce small kicks; a shock that develops strong asymmetries can give larger neutron-star kicks, while direct collapse need not do so. A schematic momentum estimate is , but neither the asymmetry nor its direction is fixed by the three core masses. The source data support tendencies, not a unique mapping from iron-core mass to remnant kick.

Pinned article: Introduction to the OurBigBook Project

Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
We have two killer features:
  1. topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculus
    Articles of different users are sorted by upvote within each article page. This feature is a bit like:
    • a Wikipedia where each user can have their own version of each article
    • a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
    This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.
    Figure 1.
    Screenshot of the "Derivative" topic page
    . View it live at: ourbigbook.com/go/topic/derivative
  2. local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:
    This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
    Figure 5. . You can also edit articles on the Web editor without installing anything locally.
    Video 3.
    Edit locally and publish demo
    . Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension.
  3. https://raw.githubusercontent.com/ourbigbook/ourbigbook-media/master/feature/x/hilbert-space-arrow.png
  4. Infinitely deep tables of contents:
    Figure 6.
    Dynamic article tree with infinitely deep table of contents
    .
    Descendant pages can also show up as toplevel e.g.: ourbigbook.com/cirosantilli/chordate-subclade
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact