Data acquisition system for the measurements of corona currents
Bibliographic record
Abstract
The measurements of voltage-current relationships in gas discharge systems often require special equipment not readily available on the market. In the presented study, a data requisition system is described, which was used for the measurements of corona currents in a pin-plane corona generator of the array type, with pins negative. The pins were made of tungsten and were arranged in two rows. The ground plane was planar, made of aluminum, and equipped with circular current-sensing electrodes made of brass and insulated from the planar anode with teflon rings. Each of the sensing electrodes was connected to 50 k/spl Omega/ resistor. The voltage across each of the resistors was measured with an operational amplifier circuit. The output of the operational amplifier was connected to an electronic scanner, the output of which was used as the input for a microcontroller (HC11, Motorola). The microcontroller was connected via the RS 232 link to an interfacing board inserted into the PCI bus of a personal computer. The computer provided a graphical user interface was used to store and process the collected data, and supported the popular data processing programs. The system allowed the measurements of the current magnitudes on up to sixteen corona pin, simultaneously. The computer interfacing board can parse the data into up to eight separate data streams. The data acquisition unit can be configured to operate with four, eight, or sixteen input channels, trading their number for the sampling rate and frequency response in three steps: 4 channels, 16,000 samples.s/sup -1/; 8 kHz; 8 channels, 8,000 samples.s/sup -1/, 4 kHz; 16 channels, 4,000 samples.s/sup -1/, 2 kHz. In the described experiment, the system was set to sample four simultaneous data streams and provided adequate response. The system operated at the same ground level as the high voltage ground. The cost of the parts used in the unit is approximately fifty dollars. With an appropriate set of sensors, the unit can be used in other high voltage applications.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.004 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.002 | 0.000 |
| Bibliometrics | 0.004 | 0.003 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.002 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.066 | 0.033 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".