René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Automatically switch all_signals definition for JET 0D vs 1D","articleBody":"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\":\r\nhttps://github.com/PPPLDeepLearning/plasma-python/blob/c82ba61e339882a5af10b1052edc0348e16119f4/data/signals.py#L399-L415\r\n\r\nbefore re-building the module and preprocessing the raw shot data. This is unique to this selection of the `conf['paths']['data']` in:\r\nhttps://github.com/PPPLDeepLearning/plasma-python/blob/c82ba61e339882a5af10b1052edc0348e16119f4/examples/conf.yaml#L13\r\n\r\nsince 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. \r\n\r\nWe should pop the 2x profile entries from the `all_signals` dictionary automatically when `params['paths']['shot_files'] = [jet_carbon_wall]`.","author":{"url":"https://github.com/felker","@type":"Person","name":"felker"},"datePublished":"2020-01-07T18:44:57.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/57/plasma-python/issues/57"}