Missing outer target ion power in wall IDS

[hrdoktorx]

The wall IDS contains a field for global_quantities/power_inner_target_ion_total, but not for global_quantities/power_outer_target_ion_total. Is this an oversight?
Also, what to do for double-null topologies, which would also affect the global_quantities/power_density_inner_target_max and global_quantities/power_density_outer_target_max fields?
Also, these fields are duplicates to some found in the divertors IDS, and are also not adapted for DN (or snowflake) topologies.

[imbeauf]

Indeed, those three quantities which correspond to divertor targets would fit much better in the divertors IDS, where an arbitrary number of targets can be defined.
global_quantities/power_density_inner_target_max and global_quantities/power_density_outer_target_max already their equivalent in the divertors IDS: divertor/target/power_flux_peak, so I propose to declare them as obsoloscent in the WALL IDS.
global_quantities/power_inner_target_ion_total has no equivalent quantity, although divertor/target/power_incident is close. Is there a real interest for this quantity describing specifically the ion total incident power ? If no one indicates his interest in this ticket, my proposal would be simply to declare it as obsolescent in the WALL IDS. Otherwise if there is an interest, I can add it to the divertors IDS.

[imbeauf]

Closed by PR #135