Pedestal scalings using published data

[jonmaddock]

In GitLab by @mkovari on Mar 16, 2023, 16:26

We need to remove the DEMO pedestal scaling from the open source version of PROCESS as it is based on EUROfusion data (#413 and #1405). The best we can get to a published version is here:

Remember also that using this scaling can give perverse results.

If in the future we want a scaling based on real published data we could try these papers:
Role of the separatrix density in the pedestal performance in deuterium low triangularity JET-ILW plasmas and comparison with JET-C (26 pages)
and
Pedestal structure, stability and scalings in JET-ILW: the EUROfusion JET-ILW pedestal database (50 pages),
both by Lorenzo Frassinetti.

[jonmaddock]

In GitLab by @ajpearcey on Mar 30, 2023, 15:47

Check if this is being used in any regression test. If not remove it. @ajpearcey

[jonmaddock]

In GitLab by @ajpearcey on Mar 30, 2023, 16:15

The scaling ieped = 1 is used in both baselines and 8 regression tests. It is also used in the ref_IN.DAT used in the integration tests.

While it is the 2019 baseline i assume it overwritten by PLASMOD and be easily be removed.

The regression tests it is used in are:
steady_state
secondary_CD
QH_mode
L_mode
i_mode
Hybrid_mode
Bucked_and_wedged
2D_scan

For this regression tests, i'd just remove the switch, this will lead to a different t_eped, which hopefully shouldn't change the solution to much.

[jonmaddock]

In GitLab by @ajpearcey on Jul 6, 2023, 13:53

There is a also a p_eped_scaling which isn't called and can be removed

[jonmaddock]

In GitLab by @ajpearcey on Jul 6, 2023, 14:53

I have had a go at running the 2018 baseline with ieped=0 and setting teped what would have be the solution value in the IN.DAT. With teped = 3.8162988701814933 we find (3.816 also gets the same result)

		ref_OUT		ieped=0 	ieped=1

rmajor		9.137 		9.175		9.175

te		12.260		12.270		12.270
teped		3.808		3.816		3.816
tesep		0.1		0.1		0.1

dene		7.162		7.115		7.115	
neped		5.618		5.581		5.581
nesep		3.305		3.283		3.283

So we can reproduce the answers by set teped IN.DAT

[jonmaddock]

In GitLab by @ajpearcey on Jul 7, 2023, 16:24

closed via merge request !939

[jonmaddock]

In GitLab by @ajpearcey on Jul 7, 2023, 16:24

mentioned in commit ce6a3a0c6db8cef218b3c373673cbad3cbb19a4b

[jonmaddock]

Already closed via merge request !939 in gitlab.