MétaCan
Menu
Back to cohort
Record W2903117470 · doi:10.1002/cjce.23422

Improving the network pinch approach for heat exchanger network retrofit with bridge analysis

2018· article· en· W2903117470 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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
venuePublished in a venue whose home country is Canada.

Bibliographic record

VenueThe Canadian Journal of Chemical Engineering · 2018
Typearticle
Languageen
FieldEngineering
TopicProcess Optimization and Integration
Canadian institutionsUniversité de SherbrookePolytechnique Montréal
Fundersnot available
KeywordsPinch analysisPinchHeat exchangerBridge (graph theory)Computer scienceNetwork analysisEnergy (signal processing)EngineeringMechanical engineeringElectrical engineeringMathematics

Abstract

fetched live from OpenAlex

ABSTRACT Economic and environmental benefits result from increasing the energy efficiency of industrial systems. This article presents the application of bridge analysis concepts to improve the methodology of network pinch for heat exchanger network retrofit. In two simple examples, we compare bridge analysis with the network pinch approach, in terms of saving energy by heat exchanger network improvement. The first example is solved with both methods, while the second can only be solved by bridge analysis. In the first example, three different solutions are proposed, and the third solution leads to 3800 kW energy savings, i.e., the full savings capacity. In the second example, no heat can be saved using the network pinch approach, but two solutions are proposed using bridge analysis, which lead to 395 kW energy savings, i.e., the full savings capacity. Then, we discuss the advantages and limits of pinch analysis and the network pinch approach. Bridge analysis provides a broader perspective on pinch analysis, explains the natural presence of a pinch in a network, shows that removing cross pinch transfers is not necessary to save energy, and helps improve heuristics for creating new cooler‐heater paths in the network pinch procedure.

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.000
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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.961
Threshold uncertainty score0.332

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
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.009
GPT teacher head0.180
Teacher spread0.171 · 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