Design and Simulation of a Double Potential Well Flat Ion Trap
Bibliographic record
Abstract
A double potential well flat ion trap was designed as an ion accumulating and focusing device for multi-reflection time-of-flight mass analyzer. Two potential wells of the trap were severally used for accumulation of injected ions, controlled cooling and ejection of trapped ions, which had features to accumulate ions continuously and cool ion for almost one period. While a flat ion trap with only one potential well is a traditional and excellent ion accumulating and focusing device, which has an intermittent ion accumulation and an ion cooling around half period. Compared with the single potential well flat ion trap, the double potential well flat ion trap had better performance on ion accumulation and focusing in principle. Four steps to run the trap were simulated and researched by an ion optics simulator of SIMION 8.1. The first step was ion accumulation, ions were successively injected into the trap, and then stored and accumulated in the first potential well. The second step was ion transfer, the trapped ions were transferred from the first potential well to the second potential well. The third step was ion cooling, the trapped ions were confined in the second potential well, and were simultaneously cooled by collisions with 0.5 Pa He. The fourth step was ion ejection, the trapped ions were ejected from the trap and focused into the next device. Ion optics simulations indicated that the trap had a period from 1 ms to above 10 ms, a total ion transmission efficiency of 83%, and an ion flux of at most 1.6×106 ions. In addition, ion packets ejected from the trap had thermalized with radial diameters of 1.0 and 1.0 mm, angular standard deviations of 24 mrad and 16 mrad, and an energy standard deviation of 15 eV. This trap can be coupled with and provide high-flux and full-focusing ion packets for multi-reflection time-of-flight mass analyzers, due to an excellent suitability between the operation of the analyzer and the period, the ion transmission efficiency, the ion flux, and ejected ion packets of the trap.
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.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.002 | 0.000 |
| Insufficient payload (model declined to judge) | 0.006 | 0.001 |
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".