Automatically switch all_signals definition for JET 0D vs 1D

[felker]

A tricky, undocumented step when switching to training on jet_data_0D is that the user must comment-out the line containing 'etemp_profile': etemp_profile, 'edens_profile': edens_profile, in the definition of the dictionary that stores "all signals defined on this machine":

plasma-python/data/signals.py

Lines 399 to 415 in c82ba61

	all_signals = {
	'q95': q95, 'li': li, 'ip': ip, 'betan': betan, 'energy': energy, 'lm': lm,
	'dens': dens, 'pradcore': pradcore,
	'pradedge': pradedge, 'pradtot': pradtot, 'pin': pin,
	'torquein': torquein,
	'energydt': energydt, 'ipdirect': ipdirect, 'iptarget': iptarget,
	'iperr': iperr,
	# 'tmamp1':tmamp1, 'tmamp2':tmamp2, 'tmfreq1':tmfreq1, 'tmfreq2':tmfreq2,
	# 'pechin':pechin,
	# 'rho_profile_spatial':rho_profile_spatial, 'etemp':etemp,
	'etemp_profile': etemp_profile, 'edens_profile': edens_profile,
	# 'itemp_profile':itemp_profile, 'zdens_profile':zdens_profile,
	# 'trot_profile':trot_profile, 'pthm_profile':pthm_profile,
	# 'neut_profile':neut_profile, 'q_profile':q_profile,
	# 'bootstrap_current_profile':bootstrap_current_profile,
	# 'q_psi_profile':q_psi_profile}
	}

before re-building the module and preprocessing the raw shot data. This is unique to this selection of the conf['paths']['data'] in:

plasma-python/examples/conf.yaml

Line 13 in c82ba61

data: d3d_data_0D # 'd3d_to_jet_data' # 'd3d_to_jet_data' # 'jet_to_d3d_data' # jet_data

since the carbon-wall training set defined for jet_data_0D, jet_data_1D, jet_data (latter two are basically unused) has missing or incomplete 1D density and temperature profile data for many shots, unlike other data choices. This causes a significant fraction of shots to be excluded during the python guaranteed_preprocessed.py step, even when the 1D profiles are not used.

We should pop the 2x profile entries from the all_signals dictionary automatically when params['paths']['shot_files'] = [jet_carbon_wall].