MétaCan
Menu
Back to cohort
Record W4322742899 · doi:10.3390/jrfm16030157

The Split-Screen Approach for Project Appraisal (Part II: Spreadsheet Modeling)

2023· article· en· W4322742899 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.

venuePublished in a venue whose home country is Canada.
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

VenueJournal of risk and financial management · 2023
Typearticle
Languageen
FieldComputer Science
TopicSpreadsheets and End-User Computing
Canadian institutionsnot available
Fundersnot available
KeywordsTransparency (behavior)Consistency (knowledge bases)Computer scienceAsset (computer security)SoftwareCapital (architecture)Software engineeringAccountingIndustrial engineeringFinanceProgramming languageEconomicsEngineeringArtificial intelligence

Abstract

fetched live from OpenAlex

This paper employs the newly conceived accounting-and-finance engineering system (AFES) described in a previous paper (Magni 2023, “The Split-Screen Approach for Project Appraisal (Part I: The Theory)”), addressed to the analysis of capital asset investments. In this second part, we show how to implement this theoretical framework onto a spreadsheet software. We guide the analyst step by step, cell by cell, to the creation of the Split-Screen Matrices describing the project film. Because the AFES is based on two arithmetic relations (law of motion and law of conservation), we can use a minimal approach to modeling, with a frugal use of the most common spreadsheet functions (essentially INDEX and MATCH) and no use of the traditional financial functions, yet fulfilling the requisite of clearness, transparency, consistency, and ease of use. Starting from the informal description of the project, we build the model by breaking it down to 7 modules. The spreadsheet model is available online (see link provided in the paper).

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.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.831
Threshold uncertainty score0.541

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0010.000
Scholarly communication0.0000.000
Open science0.0010.001
Research integrity0.0000.000
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.029
GPT teacher head0.267
Teacher spread0.238 · 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