ukaea / ukaea/PROCESS

Current ramp-up time

Open
#489 5 comments 0 reactions 1 assignee View on GitHub

@mkovari is already working on this.

Since Jul 30, 2024.

  • #3269 by @mkovari — open
Physics
Dominant language
Python
Stars
71
Forks
27
Avg merge
2d 18h
Merged PRs (30d)
33

Description

In GitLab by @mkovari on Mar 2, 2017, 11:08

The consumption of flux during start-up and current ramp is given by sum of the resistive flux consumption during start-up and current ramp and the flux consumption due to the self-inductance of the plasma during current ramp-up. The calculation of resistive flux consumption is based on the fact that the ramp-up takes of the order of the resistive current penetration time. The flux consumption is therefore dependent on the empirical Ejima constant, defined by the user (default value 0.4).

However, we don't actually calculate the ramp-up time in this way! There are a couple of limitations on the ramp-up time:

  • Constraint 41: Plasma current ramp-up time lower limit (The minimum inductive current ramp-up time depends on the voltage available from the CS power supply and the inductive coupling between the CS and the plasma).
  • Constraint 66: Limit on rate of change of energy in poloidal field.
  • In addition the maximum rate of change of plasma current is a function of the plasma current:
    ipdot = 0.0455D0*plascur

When the plasma reaches its burn temperature the resistive diffusion time is very long, and it is this time that is implied in the flux calculation using the Ejima coefficient:

Resistive diffusion time (s)         (res_time)                3.170E+03  OP 

The current ramp actually takes place at much lower temperatures, and does not take this long.

In practice this means that the calculation of the required flux swing is probably OK as long as the current ramp is set to a value less than the resistive diffusion time res_time.

Comments @rkemp @jmorris-uk @fmavig

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.