MétaCan
Menu
Back to cohort
Record W4416884617 · doi:10.37665/srdnikr63209

Addressing the Problems with Ionic Cleanliness Testing on Modern Circuits

2017· article· W4416884617 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueSoldering and Reliability Conferences · 2017
Typearticle
Language
FieldComputer Science
TopicExperience-Based Knowledge Management
Canadian institutionsnot available
Fundersnot available
KeywordsPrinted circuit boardReliability (semiconductor)Electronic circuitPoint (geometry)Test dataTest methodVoltageResistorVolume (thermodynamics)

Abstract

fetched live from OpenAlex

ABSTRACT ROSE Testing – A Historical Perspective Shortly after the electronic circuit card replaced point to point wiring in the 1950's, the reliability of manufactured circuit assemblies was directly linked to the amount of “freely” ionizable material remaining on the board following assembly. These residues in the presence of moisture and a voltage differential will undergo both chemical and dendritic electrochemical reactions resulting in rapid and catastrophic circuit failure. In response to several high profile space and military systems failures in the 1960's, the US Military developed and incorporated the “Resistance of Solvent Extract” test or as it became commonly known as the ROSE test. The ROSE test initially was performed manually using a procedure in which a known volume of clean solution of 75% IPA and 25% purified water was sprayed onto the assembly being tested and collected in a clean beaker. The resistance of the soiled solution was measured and compared to standard NaCl solutions. Based upon final resistance, the amount of NaCl equivalent on the test assembly could be determined with some accuracy. The amount determined to be present was divided by the area of the circuit being tested and an average ionic contamination was determined. A limit of no more than 10 micrograms per square inch, or 1.56 micrograms per square centimeter, was set based upon test data and reliability data from failed units. This remains the default standard today. Automated testing machines became available and replaced the manual method. The ROSE method quickly gained acceptance and was incorporated in the US military specification, Mil-P-28809 in 1971 1 . From that point forward, virtually all US contracts to build electronic hardware required that a sample board be pulled from normal production and a daily ROSE test performed. Everything got more complicated in the 1980's with the introduction of SMT assembly design because the flux in solder paste got a lot more complicated. Viscosity modifiers and thixotropic agents were added to improve printability. Tack extending agents and anti-slump compounds are present to keep things in place until the reflow soldering process heats and melts the solder. All these additions make cleaning and cleanliness testing more difficult. In 1990 the Montréal protocol was enacted and stopped the production and use of the primary class of cleaning agents being used. In response the Industry developed a new class of fluxes referred to as “No-clean fluxes”. This gave license to the flux and solder paste formulators to put things in that cannot be cleaned or at the very least were difficult to clean. Cleaning and testing got even more difficult with the introduction of higher temperature “lead free” solders which expose flux residue to a longer and hotter assembly profile. Through all of this, the ROSE test protocol remained virtually unchanged for 50 years. Confidence in the cleanliness test has eroded significantly because of concerns about dissolving and measuring the “right stuff”. ROSE testing is still required on most high reliability electronic build contracts because there is no better method which is practical in production. Figure 1 shows the evolution of cleaning and testing.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Science and technology studies, Scholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.940
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.000
Science and technology studies0.0050.002
Scholarly communication0.0050.001
Open science0.0030.001
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0000.000

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.

Opus teacher head0.177
GPT teacher head0.314
Teacher spread0.137 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it