当前位置: X-MOL 学术Plasma Phys. Control. Fusion › 论文详情
Our official English website, www.x-mol.net, welcomes your feedback! (Note: you will need to create a separate account there.)
Predictive analysis for triton burnup ratio in HL-2A and HL-2M plasmas
Plasma Physics and Controlled Fusion ( IF 2.2 ) Pub Date : 2021-02-25 , DOI: 10.1088/1361-6587/abe054
Kunihiro Ogawa 1, 2 , Yipo Zhang 3 , Jie Zhang 3 , Siriyaporn Sangaroon 1, 4 , Mitsutaka Isobe 1, 2 , Yi Liu 3
Affiliation  

The expected triton burnup ratio was analyzed based on numerical simulation to study the feasibility of demonstrating energetic particle confinement through 1 MeV triton burnup experiments in HL-2A and HL-2M. Calculations were conducted using LORBIT, a collisionless Lorentz orbit code, and FBURN, a neutron emission calculation code based on the classical confinement of energetic particles. First, the orbit loss and radial distribution of the tritons were evaluated using the LORBIT code. The LORBIT code revealed that all tritons were lost within ∼10−6 s in HL-2A, whereas in HL-2M, most of the tritons were still confined at 10−3 s. The FBURN code calculated the deuterium–tritium neutron emission rate using the radial distribution of 1 MeV tritons. The predictive analysis found that nearly no deuterium–tritium neutrons remained in HL-2A at a plasma current of 160 kA. Also, in HL-2M, a significant triton burnup ratio could be obtained at the relatively high plasma currents of 1MA, 2MA, and 3MA. This analysis predicts that the triton burnup ratio exceeds 1% under relatively high plasma current conditions.



中文翻译:

HL-2A和HL-2M血浆中Triton燃耗比的预测分析

在数值模拟的基础上分析了预期的Triton燃耗比,以研究通过HL-2A和HL-2M的1 MeV Triton燃耗实验证明高能粒子约束的可行性。计算是使用LORBIT(无碰撞洛伦兹轨道代码)和FBURN(中子发射计算代码)进行的,该代码基于高能粒子的经典约束。首先,使用LORBIT代码评估tri的轨道损耗和径向分布。LORBIT代码表明,在HL-2A中,所有tri子都在约10 -6 s内丢失,而在HL-2M中,大多数tri子仍被限制在10 -3内s。FBURN代码使用1 MeV Triton的径向分布计算了氘–中子的发射速率。预测分析发现,在160 kA等离子体电流下,HL-2A中几乎没有残留氘–中子。同样,在HL-2M中,在1MA,2MA和3MA的相对较高的等离子体电流下,可以获得显着的tri核燃耗比。该分析预测,在相对较高的等离子体电流条件下,ton核燃耗比超过1%。

更新日期:2021-02-25
down
wechat
bug