HBT-EP magnetic sensor array: analysis scripts, derived tables, and figures for two companion papers on reference-channel and analysis-window artefacts and magnetic-sensor fault localisation

Analysis scripts, derived tables, and publication figures supporting two companion papers on the ten-station Mirnov array of the HBT-EP tokamak. Paper A, "A reference channel and an analysis window can create an apparent ranking of nominally identical magnetic sensor channels" (submitted to Measurement Science and Technology), reports that the apparent ranking of ten nominally identical magnetic sensors came largely from the comparison quantity: the Rogowski cosine channel used as the reference records the horizontal moment of the plasma current with pickup from the ohmic and vertical-field coils, not a mode amplitude. Against the n=1 mode amplitude fitted to the separate thirty-sensor toroidal array, all ten channels agree positively under both analysis configurations; the configuration timed from the recorded actuator turn-on resolves nine of them individually, against four under the experiment's own configuration. Paper B, "Gibbs Sensor Fusion: a one-pass combination rule from a hyperbolic ratio cost, and the limits of reweighting a tokamak magnetic array", is in preparation; its numbers in this deposit are on the earlier references and will be restated on the n=1 reference in a later version. Every HBT-EP number printed in Paper A is in the deposited tables: the rows with reference n1 of the cos1 tables, and the round-50 and round-51 files listed in README.txt. The derived n=1 amplitude traces of all 44 discharges are included. Raw HBT-EP pulse files and raw-signal caches are not included and remain subject to HBT-EP collaboration and facility data policies; regenerating the tables from the scripts in the scripts folder therefore needs access to the MDSplus trees. The synthetic benchmark of Paper B is not reproducible from this deposit: its CGYRO-derived ground-truth waveform, generating script, and per-trial outputs were never archived. Two runnable stand-ins are included instead, listed in README.txt. README.txt describes every file, and the manifest at the root of the archive gives the SHA-256 of each file.