Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add average effect of ELMS on divertors heat flux #590

Open
orso82 opened this issue Jun 24, 2024 · 2 comments
Open

Add average effect of ELMS on divertors heat flux #590

orso82 opened this issue Jun 24, 2024 · 2 comments
Labels

Comments

@orso82
Copy link
Member

orso82 commented Jun 24, 2024

image image image image image
@orso82 orso82 added enhancement New feature or request negative_triangularity labels Jun 24, 2024
@bclyons12
Copy link
Member

You've got better experts than I in that thread, and some of these points got mentioned already, but there are two separate issues.

  • The peak heat load from ELMs. This is generally considered to be intolerable in PT anyway, so a reactor will need an ELM mitigation strategy. A PT reactor should then take into account the cost of such a system (e.g., RMP coils, pellet pacing) and the cost for divertor materials that can tolerate expected peak heat fluxes (e.g., pellet pacing, grassy ELMs) from an erosion standpoint. The latter should be higher than what would be required by the time-averaged heat flux. You would also want to account for the risk that ELMs breakthrough your mitigation strategy (e.g., loss of QH-mode or ELM suppression).
  • The average divertor heat loads in PT vs NT. Again, I think a PT attached divertor is generally considered intolerable (except with liquid metals, perhaps?).
    • PT you need a detachment strategy. Radiation is still localized to the divertor region, so there's some increased heat flux there. That has cost implications on the materials. Then there are risk considerations from loss of detachment and loss of confinement if there's a pedestal collapse.
    • NT benefits from the potential use of radiated mantle. At the very least, there's TRL risk associated with that for core-edge integration. I'm not sure what the demonstration status is for this.

I would think you'd want an actor making discrete choices between these options, then assess the monetary cost and the quantized risk associated with each. After that, the optimizer can figure out which is best. Here's an example, though there might be other options of course (strike point sweeping?).
Screenshot 2024-06-24 at 12 17 15 PM

@orso82
Copy link
Member Author

orso82 commented Jun 24, 2024

I love this way of breaking down the problem @bclyons12 !

The ActorDivertors should capture the expected change in divertor heatflux, while cost and risk should go in the ActorCosting and ActorRisk respectively

Here's a mermaid diagram of your figure ;)

flowchart TD
  FPP("FPP")
  DetachedPT("Detached PT")
  NT("NT")
  RMP("RMP")
  ELMFreeScenario("ELM-free Scenario")
  PelletPacing("Pellet Pacing")
  DetachedDivertor("Detached Divertor")
  RadiativeMantle("Radiative Mantle")
  StrikePointSweeping("Strike Point Sweeping")
  CostRisk("COST AND RISK FOR EACH LEAF")

  FPP --> DetachedPT
  FPP --> NT
  DetachedPT --> RMP
  DetachedPT --> ELMFreeScenario
  DetachedPT --> PelletPacing
  DetachedPT --> StrikePointSweeping
  NT --> DetachedDivertor
  NT --> RadiativeMantle
  RMP --> CostRisk
  StrikePointSweeping --> CostRisk
  ELMFreeScenario --> CostRisk
  PelletPacing --> CostRisk
  DetachedDivertor --> CostRisk
  RadiativeMantle --> CostRisk
Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants