From a power requirement to a compatible system
Include what keeps
the power running.
Support consumes resources it must itself support. An extra battery pack brings a cooling allowance. Cooling draws power. Conversion loses energy. That can call for another pack. The least compatible design has to close the whole loop.
01 · BATTERIESSupply energy.
Bring a heat allowance.
Usable battery energy must cover the monitoring equipment, cooler draw and converter loss throughout the monitoring period.
02 · CONVERTERSSupply output.
Add conversion loss.
Converters must support monitoring demand plus cooling draw. Their fixed operating loss becomes heat and an energy requirement.
03 · COOLINGRemove heat.
Use some power.
Coolers cover the allowance from operating packs and converter losses. Their own electrical draw returns to the power requirement.
Three interfaces, checked in their own units
Battery energy ≥ hours × (monitoring power + cooling draw + converter loss)
Converter output ≥ monitoring power + cooling draw
Heat removal ≥ pack heat allowance + converter loss
Counts are whole numbers. Within each of eight fixed-family architectures, the actual Python codesign-mcdp package composes these modules using System and starts its feedback calculation at zero. Each pass increases obligations until the count vector stabilises. The app preserves the package’s trace and the implementing equipment counts.
A converged count vector is checked directly against all three interfaces. It is then compared with explicit equipment availability: 32 battery packs, 12 converters and 20 coolers. Calculation completion and catalogue availability are separate findings.
Why the least counts are enough here
The declared count map is monotone: raising connected obligations cannot reduce the required number of a component. The zero-start fixed point is componentwise no larger than any compatible count vector in the same architecture. Every extra component has positive cost and cabinet volume. Thus the least compatible vector dominates larger vectors of that family. If it exceeds an equipment cap, a larger one cannot repair availability.
After this sizing, the app compares capital and cabinet volume across all eight families. Equal resource points retain all family IDs. Upper ceilings on these resources can filter the complete results without hiding a newly preferable oversized design. This conclusion relies on this particular monotone model and its resource coefficients.
A finite atlas of real package calculations
The 98 selectable briefs cover seven power values, seven durations and two declared conditions. Each has eight cold-start package calculations. The browser reads those precomputed records and filters or displays them; it does not run Python or substitute a JavaScript sizing algorithm. Arbitrary power values, durations, component coefficients and climate conditions are outside the atlas. Capital and cabinet volume ceilings may be entered freely. They are retained as decimal strings in the record; comparison with the whole-pound and whole-litre resource totals uses the exact integer part, so a ceiling just below a boundary cannot round up to include it.
Model, equations and verification · Python calculation recipe · Complete calculation atlas
Read the component catalogue and hot-condition factors
Hot multiplies usable battery energy by 4/5, pack heat allowance by 3/2, and cooler removal capacity by 4/5. Converter parameters and cooler draw are unchanged. “Hot” is one declared scenario, not a probability distribution or a universal worst case.
Usable Wh is net DC energy after internal cell losses. Cooling draw and converter loss are accounted for separately. The fixed heat per operating pack is a design allowance; it is not a physical assertion that adding parallel batteries always increases actual heat at a fixed monitoring load.
What the first pass leaves out
The comparison initially sizes batteries for monitoring energy and converters for monitoring power, then adds cooling for those initial components. It stops before enlarging batteries and converters for cooling draw and conversion losses. The resulting interface checks expose what remains unsupported. It is a deliberately incomplete comparison, not an alternative acceptable design.
A cabinet beside the crossing
The 750 W default represents a cluster of cameras, illumination, sensors, a logger and a data link, operating for eight hours without charging. It can stand for an overnight or temporary deployment; it is not the draw of a typical individual camera trap. The model sizes its power equipment, not the crossing itself.
Cabinet volume is an additive allocation in litres for equipment housing and internal spacing: 28/16 L per standard/compact battery pack, 12/8 L per standard/efficient converter and 12/6 L per air/liquid support unit. It does not predict ground footprint, exterior dimensions or physical packing. Liquid cooling is one equipment-family choice.
A sizing result, with a clear boundary
Equipment capacities, heat allowances, losses, costs and cabinet volumes are model inputs rather than supplier data. Steady demand replaces a real duty cycle. The model omits transient thermal behaviour, charging, protection, reliability, distribution losses, construction sequence and site constraints beyond its explicit inventory and resource ceilings. A converged calculation is not an engineering or safety approval.
For the separate question of keeping a crossing usable while work proceeds, visit Staged crossing paths. This app sizes monitoring power; it does not place it into that construction model or predict animal behaviour.