Conversation
7817b0a to
905ad24
Compare
|
@jcitrin could you comment on some of the boundary value extrapolations done here? |
1e0c0a6 to
971f37e
Compare
|
I’ve reviewed the changes in the
|
jcitrin
left a comment
There was a problem hiding this comment.
Sorry this took so long to review!
|
|
||
| # TODO: Map impurity quantities in PostProcessedOutputs on cell_plus_boundaries | ||
| # grid to get rid of this function. | ||
| def _calculate_impurity_density_scaling_and_charge_states( |
There was a problem hiding this comment.
apologies if you already have this. But it would be great to unit test such functions with "round trip" calculations from IMAS --> TORAX --> IMAS
There was a problem hiding this comment.
There is one TORAX -> IMAS -> TORAX but indeed it could be useful to have it also the other way around to test other quantities. Will try to add it !
c7c099b to
23a82ac
Compare
|
Apologies this seems to have fallen through the net. Can you rebase and then someone will take a look |
23a82ac to
4148d5d
Compare
4148d5d to
867c583
Compare
Mapping of some quantities which are not directly available on cell_plus_boundaries grid: j_parallel_total, j_parallel_ohmic, j_non_inductive, Z_avg for impurities and impurity_density_scaling factor.
IDS requires all profiles_1d to be on the same grid, therefore these quantities needed to be computed on the cell_plus_boundaries grid.
Question
To extend them, neighbouring values were copied as boundary values. Other possibility could be to use linear / polynomial extrapolation. What choice should be made for these quantities ?
Fixing wrongly mapped quantities:
j_totalandj_bootstrapcorresponds to their parallel current density. It was previously mapped from the toroidal values.Newly mapped quantities:
j_ohmic,j_non_inductive,j_phiz_ion_1d,n_impurity,n_i_volume_average