Still no clue if i am doing things right. I now oversized the channel…

… name array to fit all possible number of channels in use for any shot (i hope). The actual size is dealt with a hidden signal _r. I still have ALL the data read on each of the channels data which is ridiculous. I should be able to SLICE it according to the actual signal i want but the indices are mute in the JSON so the only possible way i can think of is to create hidden signals again to store all the 2D array and then use # for the indexing......argh...

mappings/thomson_scattering/globals.json

@@ -64,6 +64,21 @@
         "CH58",
         "CH59",
         "CH60",
-        "CH61"
+        "CH61",
+        "CH62",
+        "CH63",
+        "CH64",
+        "CH65",
+        "CH66",
+        "CH67",
+        "CH68",
+        "CH69",
+        "CH70",
+        "CH71",
+        "CH72",
+        "CH73",
+        "CH74",
+        "CH75",
+        "CH76"
     ] 
 }

mappings/thomson_scattering/mappings.json

@@ -22,13 +22,22 @@
         "VALUE": 1,
         "COMMENT": "Provenance for the whole IDS"
     },
+    "_r": {
+       "MAP_TYPE": "PLUGIN",
+        "PLUGIN": "MDSPLUS",
+        "ARGS": {
+            "signal": "%TDI%_aux=jet(\"PPF/HRTS/TE\",{{ SHOT }}); _sig = dim_of(_aux,0)"
+        },
+        "COMMENT": "The final syntax of this string may change"
+    },
     "channel": {
-        "MAP_TYPE": "VALUE",
-        "VALUE": "{{ length(CH_NAMES) }}"
+        "MAP_TYPE": "DIMENSION",
+        "DIM_PROBE": "_r"
     },
     "channel[#]/name": {
         "MAP_TYPE": "VALUE",
-        "VALUE": "{{ at(CH_NAMES, indices.0) }}"
+        "VALUE": "{{ at(CH_NAMES, indices.0) }}",
+        "COMMENT": "The array defined in globals is oversized since i have no clue what is the total number of channels for each shot before reading the PPF. If only i had a dynamical string array generator..."
     },
     "channel[#]/position/r": {
        "MAP_TYPE": "PLUGIN",