MétaCan
Menu
← Back to cohort
Record W6966523887 · doi:10.4224/19541699

Data acquisition software for port interfacing devices

2011· report· en· W6966523887 on OpenAlexvenueno aff

Bibliographic record

VenueNPARC · 2011
Typereport
Languageen
Field
Topic
Canadian institutionsnot available
Fundersnot available
KeywordsInterfacingSoftwareData acquisitionSerial portInterface (matter)JavaData loggerSoftware design

Abstract

fetched live from OpenAlex

Data acquisition is a problem that is frequently encountered in the world of research and experimentation. There are many existing software applications that are abstract enough to handle data acquisition for a large range of scenarios, but sometimes a more specialized approach is needed. I designed the Data Logger application to be a lightweight standalone application to translate data sent from multiple serial-ports, which interface with IMUs (Inertial Measurement Units), and then record the data in log files. These log files would then be used during post experimental processing to determine conclusions based on IMU performance. This application was written in Java using only one external library, the Java Communications API (also known as javax.comm). The software was designed with extensibility in mind. This is to say that it would be easy for any other serial-port interfacing device (not just IMUs) to have its data recorded by Data Logger. All that’s required is for someone to implement the translation of the data streaming from the serial port. The software architecture is also setup so that it should be simple to add new modules to communicate with and record data from other sources, including different kinds of ports. Throughout design and implementation, a few concerns and problems were noticed and addressed. Solutions have been found for some, such as accurate time stamping, but there are other issues that remain unsolved, such as time-synchronization.

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 imitation

Not 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.

metaresearch head score (Codex)0.003
metaresearch head score (Gemma)0.012
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Software · Consensus signal: none
Teacher disagreement score0.108
Threshold uncertainty score0.361

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0030.012
Meta-epidemiology (narrow)0.0020.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0020.002
Science and technology studies0.0010.000
Scholarly communication0.0020.003
Open science0.0030.002
Research integrity0.0010.003
Insufficient payload (model declined to judge)0.1080.055

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.166
GPT teacher head0.362
Teacher spread0.196 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreSoftware

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".

Quick stats

Citations0
Published2011
Admission routes1
Has abstractyes

Explore more

Same venueNPARC→French-language works237,207→