Develop the ability to use plasmod/jetto profile directly in PROCESS

ukaea / PROCESS

PROCESS is a systems code at UKAEA that calculates in a self-consistent manner the parameters of a fusion power plant with a specified performance, ensuring that its operating limits are not violated, and with the option to optimise to a given function of these parameters.

https://ukaea.github.io/PROCESS/

MIT License

35 stars 11 forks source link

Develop the ability to use plasmod/jetto profile directly in PROCESS #3347

Open ym1906 opened 1 week ago

ym1906 commented 1 week ago

When the plasma profile was refactored, it was done so with a view to using completely custom profiles. However, a custom case was never developed or tested in practice. Now we should test this ability.

Figure out the best way to import profile data into PROCESS.
Modify the code to handle this profile (add new argument, and create the profile object correctly)
Point generic profile object to data
Run, test.
Develop a tool for profile comparison between PROCESS and external profile.

mkovari commented 4 days ago

See #766 (also #3254).

Most codes output profiles as a function of the normalised flux (usually poloidal flux), a quantity that PROCESS does not use. We would need:

To be able to convert from the normalised minor radius to normalised flux, and
To be able to calculate the volume element dV. In all JETTO runs, dV/drho is output in the signal profiles / DVEQ.

mkovari commented 4 days ago

Once the profiles are fixed, perhaps normalised by the central temperature and density, what variables remain for PROCESS to optimise? Is it still self-consistent to vary the major radius, aspect ratio, toroidal field, impurity concentration, plasma density and temperature?

Did you test an optimisation run using a custom profile? @ym1906

Opinions @stuartmuldrew @ajpearcey ?