Laboratory Electrical Model of the Louis-Hippolyte \nLafontaine Tunnel
Bibliographic record
Abstract
The Louis-Hippolyte Lafontaine tunnel is defined as a critical infrastructure as it represents a major transportation link connecting the island of Montreal and the South Shore. Consequently, the daily operation of the tunnel is highly dependent on the stability of the electrical grid to maintain a proper power supply. Moreover, the changing electrical profile of the tunnel throughout the year is reflected differently on the grid. Hence, the scope of this work is to emulate and model a scaled-down version of the electrical system of the tunnel Louis-Hippolyte Lafontaine based on different operational scenarios. The system that is considered is simplified to the main electrical loads, which are the heating (purely resistive), lighting (mostly resistive) and ventilation fans. The modeling of the electrical profile is achieved using measurement-based data. To achieve the emulation of the ventilation fan, a drive system for a 2-hp induction motor is modeled in the MATLAB/Simulink environment and validated experimentally using open-loop voltage-over-frequency control under no-load condition. The results show proper speed control with the flux maintained constant under rated frequency in addition to accurate response to speed command change. To illustrate the changing operational profile of the tunnel throughout the year, the scaled-down electrical system is simulated and adapted to the corresponding profile of a summer day, a winter day and during an emergency event (diesel generator supply). For each distinctive day, the power characteristics at the point of common coupling are evaluated in regards to the respective electrical loads connected to the system. The analysis of the scaled-down simulated system has shown that the nature of the loads solicited in their respective scenarios has different impacts on the supply system. Through this research work, the scaled-down model of the Louis-Hippolyte Lafontaine tunnel electrical system showed similar power characteristics to what is observed on the actual system.
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.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 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".