Multi-Machine Disruption Prediction Challenge for Fusion Energy by ITU
$5 000 USD
Challenge completed almost 2 years ago
Prediction
417 joined
55 active
Start
Jul 26, 23
Close
Nov 12, 23
Reveal
Nov 12, 23
'/%3e%3cuse xlink:href='%23a' transform='rotate(23.036 .093 25.536)'/%3e%3cuse xlink:href='%23a' transform='rotate(45.87 1.273 16.18)'/%3e%3cuse xlink:href='%23a' transform='rotate(69.945 .996 12.078)'/%3e%3cuse xlink:href='%23a' transform='rotate(20.66 -19.689 31.932)'/%3e%3c/svg%3e){kind=small}
Question : "&" mean?
Data · 23 Oct 2023, 08:03 · 1
Hello, I have a question. According to the table,
when the Diagnostics column is 【AXUV_01】,
the corresponding C-Mod MDSplus Tag column should be 【\AXA.chord_1 & \AXJ.chord_1】.
However, in the CMod file, there is no such tag,
but I noticed separate AXA.chord_1 and AXJ.chord_1.
So, what operation should be performed based on these two columns to get \AXA.chord_1 & \AXJ.chord_1 to match the AXUV_01 feature?
---- ----
So, the "&" in the
\\xtomo::top.brightnesses.array_1:chord_01 & \\xtomo::top.brightnesses.array_3:chord_01
means the same operation , right?
I also struggle with mapping the CMod data. For your question, I suggest using the first signal when '&' appears.
However, some tags are totally wrong in ITU data - signal.csv, which makes it seem like signals are missing in the CMod files. Please take a look at my latest question in the discussion. How are you going to handle that situation? Thanks.