Systems analysis development for aries next step
Download
1 / 18

Systems Analysis Development for ARIES Next Step - PowerPoint PPT Presentation


  • 79 Views
  • Uploaded on

Systems Analysis Development for ARIES Next Step. C. E. Kessel 1 , Z. Dragojlovic 2 , and R. Raffrey 2 1 Princeton Plasma Physics Laboratory 2 University of California, San Diego ARIES Next Step Meeting, April 3-4, 2007, UCSD. Motivation for a “New” Systems Code.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Systems Analysis Development for ARIES Next Step' - kay


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Systems analysis development for aries next step

Systems Analysis Development for ARIES Next Step

C. E. Kessel1, Z. Dragojlovic2, and R. Raffrey2

1Princeton Plasma Physics Laboratory

2University of California, San Diego

ARIES Next Step Meeting, April 3-4, 2007, UCSD


Motivation for a new systems code
Motivation for a “New” Systems Code

  • Systems codes are critical tools in fusion design, because they integrate physics, engineering, design and costing

    • Scanning can be done with simple models

    • Results from detailed analysis can be incorporated for more specific searches

  • Our ARIES Systems Code (ASC) has become very cumbersome and has lost its technical maintenance (primarily physics and engineering)

  • The approach taken by most (if not all) systems codes has been to produce an optimal operating point, which is often difficult to justify, why is it optimal?

  • This does not utilize the power of a systems code, which is to generate many operating points (operating space approach)


Operating space approach to systems analysis
Operating Space Approach to Systems Analysis

  • On the FIRE project I developed a systems code that combined physics and engineering analysis for a burning plasma experiment, which found the minimum major radius solution within several constraints

  • For Snowmass 2002 I took the physics part out, and began to use it to generate many physics operating points, that satisfied multiple physics boundaries/constraints ---> physics operating space

  • Finally I started to use a second code that took the all the viable physics operating points and imposed engineering constraints (divertor heat load, FW surface heat load, nuclear heating, TF coil heating, PF coil heating, etc) and physics filters to find feasible operating space


Operating space approach feasible operating space physics and engr
Operating Space Approach: Feasible Operating Space (Physics and Engr.)

AT-mode

H98 ≤ 2.0

FIRE

ELMy H-mode

H98 ≤ 1.1


The operating space approach has several advantages
The Operating Space Approach Has Several Advantages and Engr.)

  • Operating space approach to systems analysis makes the effect of constraints more transparent

  • Many constraints carry a lot of uncertainty, which can be quantified

  • Sequencing the analysis through 1) physics operating space, 2) engineering operating space, and 3) device build and cost, will provide a better explanation of available operating points and why they are desirable


Systems code being developed
Systems Code Being Developed and Engr.)

Systems analysis flow

physics

engineering

build out/cost

Inboard radial build and engineering limits

Top and outboard build, and costing

Plasmas that satisfy power and particle balance

Systems applications

Large systems scans

Targeted systems scans

Operating point search and sensitivity scans, supported by detailed analysis


Systems code being developed1
Systems Code Being Developed and Engr.)

  • Physics module:

    • Plasma geometry (R, a, , , o, I)

    • Power and particle balance

    • Bremsstrahlung, cyclotron, line radiation

    • Up to 4 heating/CD sources

    • Up to 3 impurities beyond e, DT, and He

    • Bootstrap current, flux consumption, fast beta

    • …..

  • Engineering module:

    • Physics filters: PCD≤ Paux

    • Feasible inboard radial build (SOL, FW, gap1,blkt, gap2,shld,gap3, VV, gap4, TF, gap5, BC, gap6, PF)

    • Pelec = th(PnxMn+Pplas)x(1-fpump-fsubs) - Paux/ aux

    • FW peak surface heat flux limit (≤ 0.5-1.0 MW/m2)

    • Divertor peak heat flux (conduction+radiation, ≤ 20 MW/m2)

    • BT,max ≤ BT,maxlimit, jsc ≤ jsc,max(BT,max)

    • Bucking cylinder pressure

    • BPF,max ≤ BPF,maxlimit, jsc ≤ jsc,max(BPF,max)

    • …..


Systems code being developed2
Systems Code Being Developed and Engr.)

  • Device Buildout (develop outboard description) and Costing

    • TF coil shape, full sector maintenance

    • PF coil layout

    • Divertor layout

    • Extension of inboard build to outboard, VV, shield, BC, etc.

    • Outboard radial build (different from inboard)

    • Volume/mass calculation

    • Costing

    • ……


Physics module input assumptions
Physics Module Input/Assumptions and Engr.)

Can run a single point to determine its power balance

Input file #1

Output file (screen)

  • BT

  • A

  • N

  • q95 or cyl

    n

    T

    n/nGr

    tflattop

    

    He*/E

    li

    Cejim

    breakdown

    CD

    PCD

    rCD

CD1

PCD1

fCD1

rCD1

CD2

PCD2

fCD2

rCD2

CD3

PCD3

fCD3

rCD3

CD4

PCD4

fCD4

rCD4

Hmin

Hmax

R

<ne>

n/nGr

<Te>

tflattop/J

frad

Zeff

tflattop

E

P

J

fBS

Nwall

fHe

fDT

fast

H98(y,2)

Wth

consumed

2

Zimp1

fimp1

Zimp2

fimp2

Zimp3

fimp3

T(0)/Tedge

n(0)/nedge

R

A

BT

IP

q95

t

P

N

P

Pbrem

Pcycl

Pline

PLH

Ploss/PLH

Pfusion

Paux

Pohm

Vloop

fCD

fNI

n(0)/<n>

T(0)/<T>


Physics Module Input/Assumptions and Engr.)

Can run many points by scanning a variable, and writing a out data

Input file #2 (scan parameters)

Output file (ascii datafile)

nBT

BT,start

BT,final

nN

N,start

N,final

nq95

q95,start

q95,final

n

start

final

.

.

.

n

T

n/nGr

Paux

PCD3

PCD4

fimp1

fimp2

fimp3

T(0)

fCD

fNI

fHe

fDT

Wth

consumed

Vloop

n(0)/<n>

T(0)/<T>

t

P

P

Ploss/PLH

Q

He*/E

R

CD

fimp1

fimp2

fimp3

R

A

BT

IP

N

q95

qcyl

n

T

n/nGr

Q

H98(y,2)

J

E

p*/E

<ne>

<Te>

tflattop

PLH

Nwall

Pbrem

fBS

CD

PCD

Paux

Pcycl

Pohm

Pline

fast

Zeff

T(0)/Tedge

n(0)/nedge

PCD1

PCD2


Systems code test physics database intended to include aries at type solutions
Systems Code Test: Physics Database Intended to Include ARIES-AT Type Solutions

  • Physics input: (not scanned)

    • A = 4.0

    • = 0.7

      n = 0.45

      T = 0.964

    • = 2.1

      li = 0.5

      Cejim = 0.45

      CD = 0.38

      rCD = 0.2

      Hmin = 0.5

      Hmax = 4.0

      Zimp1 = 4.0

      fimp1 = 0.02

      Zimp2 = 0.0015

      fimp2 = 18.0

      Tedge /T(0) = 0.0

      nedge /n(0) = 0.27

  • Physics input: (scanned)

    BT = 5.0-10.0 T

    N = 0.03-0.06

    q95 = 3.2-4.0

    n/nGr = 0.4-1.0

    Q = 25-50

    He*/E = 5-10

    R = 4.8-7.8 m

Generated 408780 physics operating points


Systems code test engineering constraint reduction of physics database
Systems Code Test: Engineering Constraint Reduction of Physics Database

  • Engineering input/assumptions:

    • FW radiation peaking = 2.0

    • QFW < 1.0 MW/m2

    • fdivrad = 0.65

    • fSOLoutboard/inboard = 0.8/0.2

    • fflux/angle = 10

    • Qdiv,outboardpeak < 20 MW/m2

    • Qdiv,inboardpeak < 20 MW/m2

    • Mblkt = 1.1

    • th/aux = 0.59/0.43

    • fpump = 0.03

    • fsubs = 0.04

    • SOLi = 0.07 m

    • FWi = 0.075 m

    • gap1i = 0.01 m

    • blkti = 0.35 m

    • gap2i = 0.01 m

    • shldi = 0.25 m

    • gap3i = 0.01 m

    • VV = 0.40 m

  • gap4i = 0.01 m

  • TFi = solved for

  • gap5i = 0.01 m

  • BCi = solved for

  • gap6i = 0.01 m

  • PFi = solved for

  • NTF = 16.0

  • Btmax, limit = 21 T

  • Jsc, max, limit = 2.5x108 A/m2

  • jTFoverall (ARIES-I)

  • hBC = 1.2 x 2 x  x a

  • hPF = hBC

  • BPF,max,limit = 16 T

  • Jsc, max, limit = 2.5x108 A/m2

  • Imax = 1/2 x I (provide )

  • PCD ≤ Paux

53354 operating points survive


Filtering the operating points further
Filtering the Operating Points Further Physics Database

975 ≤ Pelec (MW) ≤ 1025

Paux ≤ 40 MW

R ≤ 5.5 m

975 ≤ Pelec (MW) ≤ 1025

ARIES-AT


Looking at a few points
Looking at a Few Points Physics Database


How should we visualize the operating space
How Should We Visualize the Operating Space? Physics Database

975 ≤ Pelec (MW) ≤ 1025

975 ≤ Pelec (MW) ≤ 1025, Paux ≤ 40 MW, R ≤ 5.5 m


How should we visualize the operating space1
How Should We Visualize the Operating Space? Physics Database

975 ≤ Pelec (MW) ≤ 1025

Paux ≤ 40 MW

R ≤ 5.5 m

975 ≤ Pelec (MW) ≤ 1025


Future work continue to exercise systems code
Future Work - Continue to Exercise Systems Code Physics Database

  • Physics module:

    • Include squareness, add numerical volume/area calculation

    • Additional parameters to scan input file

    • Separate electron and ion power balance

    • Multiple fusion reactions?

    • Reproduce other operating points (ITER, FIRE, ARIES-I, ARIES-ST, etc.)

  • Engineering module:

    • Refine FW and divertor heating models

    • Is there an approximate neutronics model for inboard radial build?

    • Examine more complex power conversion cycles

    • Establish a general TF coil model

    • Examine PF equilibrium solutions

    • Anticipate detailed analysis constraints/inputs to systems code

    • Plotting and outputing results of scans/filters etc.


Neutronics for inboard radial build
Neutronics for Physics DatabaseInboard Radial Build

  • FW/Blanket lifetime limited by damage/gas production > 2 years

  • Shield limited by damage/gas production > 7 years

  • VV is lifetime component, reweldability

  • FW/Blanket/Shield/VV provides neutron attenuation at TF magnet (nuclear heating, Cu damage, insulator dose, …)

  • Blanket provides limited tritium breeding

  • Deposited surface heat flux removed by FW

  • Deposited volumetric heating removed by FW/Blanket/Shield

  • Generic material fractions in each component

  • Estimates for neutron power fraction to inboard

  • …..


ad