#thermodynamics

Vapor-pressure thermodynamics as an API, computed locally and deterministically. The clausius-clapeyron endpoint predicts the vapor pressure of a substance at a new temperature from a known reference point and the molar enthalpy of vaporization, using ln(P2/P1) = -ΔHvap/R·(1/T2 - 1/T1) with temperatures in kelvin — so from water boiling at 101.325 kPa at 373.15 K and ΔHvap ≈ 40.66 kJ/mol it returns about 42.6 kPa at 350 K. The enthalpy endpoint inverts the same relation: given two pressure/temperature points it solves for the molar enthalpy of vaporization, ΔHvap = -R·ln(P2/P1)/(1/T2 - 1/T1), in J/mol and kJ/mol. The antoine endpoint evaluates the Antoine equation log10(P) = A - B/(C + T) both ways — supply a temperature to get the vapor pressure, or a pressure to get the boiling temperature — defaulting to the water constants (°C and mmHg, so water reads 760 mmHg at 100 °C) but accepting any A, B, C for other substances. The gas constant R = 8.314462618 J/(mol·K). Everything is computed locally and deterministically, so it is instant and private. Ideal for chemical-engineering, process-simulation, distillation, HVAC, meteorology and chemistry-education app developers, boiling-point and phase-equilibrium tools, and lab software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is vapor pressure and boiling point; for humidity and dew point use a psychrometric API and for ideal-gas state use a gas-law API.

api.oanor.com/vaporpressure-api

Heat-engine efficiency and coefficient of performance as an API, computed locally and deterministically. The efficiency endpoint gives the Carnot maximum efficiency of any heat engine working between two temperatures, η = 1 − Tc/Th (in kelvin) — the absolute upper limit no real engine can beat — and, given a heat input, the maximum work it could produce and the heat it must reject. The heat-pump endpoint gives the Carnot coefficient of performance of a heat pump, COP = Th/(Th − Tc), and of a refrigerator or air conditioner, COP = Tc/(Th − Tc), and the heat moved for a given work input. The engine endpoint analyses a real engine from its heat balance: from any two of the heat input, the work output, the efficiency or the heat rejected it returns the rest using η = W/Qh and Qc = Qh − W, and — given the reservoir temperatures — compares it to the Carnot limit and reports the second-law (exergy) efficiency. Temperatures accept kelvin, Celsius or Fahrenheit. Everything is computed locally and deterministically, so it is instant and private. Ideal for thermodynamics-education tools, engine, turbine and HVAC design, refrigeration and heat-pump apps, and energy-systems software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is heat-engine and refrigeration-cycle efficiency; for sensible heat use a specific-heat API and for heat-exchanger LMTD use a heat-exchanger API.

api.oanor.com/carnot-api

Newton's law of cooling and convective heat transfer as an API, computed locally and deterministically. The convection endpoint applies the convective-heat-transfer rate Q = h·A·ΔT — the heat carried away from a surface equals the convection coefficient times the area times the temperature difference between the surface and the fluid — and solves for whichever of the heat rate, the coefficient, the area or the temperature difference you leave out, with typical coefficients for natural and forced air, water, boiling and condensing built in. The cooling endpoint applies Newton's law of cooling, T(t) = T_env + (T0 − T_env)·e^(−k·t): from an initial temperature, the ambient temperature and a cooling constant (or time constant τ = 1/k) it gives the temperature after a time, or the time to reach a target temperature, or it solves the cooling constant from a measured temperature at a known time — the maths behind how a hot drink, a forensic body or a cooling casting approaches room temperature. The coefficient endpoint links the cooling constant to the physical properties, k = h·A/(m·c), and the thermal time constant. Everything is computed locally and deterministically, so it is instant and private. Ideal for thermal-engineering and HVAC tools, food-safety and forensic cooling apps, electronics-cooling and process-control software, and physics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is convection and transient cooling; for steady conduction through walls use a U-value API and for thermal radiation use a Stefan-Boltzmann API.

api.oanor.com/cooling-api

Heat-exchanger LMTD and effectiveness-NTU maths as an API, computed locally and deterministically. The lmtd endpoint computes the log mean temperature difference, LMTD = (ΔT1 − ΔT2)/ln(ΔT1/ΔT2), the true average driving temperature of a heat exchanger, from the hot and cold stream inlet and outlet temperatures for either a counterflow or a parallel-flow arrangement, and flags a temperature cross. The duty endpoint applies Q = U·A·LMTD·F — the heat duty equals the overall heat-transfer coefficient times the area times the LMTD times an optional correction factor — and solves for whichever of the duty, the coefficient, the area or the LMTD you leave out, taking the LMTD directly or from the four temperatures. The effectiveness endpoint uses the effectiveness-NTU method: from the hot and cold heat-capacity rates (given directly or as mass flow times specific heat) and the number of transfer units NTU = U·A/Cmin, it returns the capacity ratio, the effectiveness for the arrangement, and — given the inlet temperatures — the maximum and actual heat duty and the outlet temperatures. Everything is computed locally and deterministically, so it is instant and private. Ideal for process, chemical and mechanical engineering tools, HVAC, refrigeration and thermal-design apps, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is two-stream heat-exchanger analysis; for the sensible heat of a single stream Q = m·c·ΔT use a specific-heat API.

api.oanor.com/lmtd-api

Latent-heat and phase-change enthalpy as an API, computed locally and deterministically. The latent endpoint applies Q = m·L — the heat to melt, freeze, boil or condense a substance equals its mass times the latent heat — and solves for whichever of the heat, the mass or the latent heat you leave out, taking the latent heat of fusion or vaporization directly or from a built-in substance table (water, ethanol, mercury, lead, aluminium, iron, nitrogen, oxygen). The phase-change endpoint computes the full enthalpy of heating or cooling a substance from one temperature to another, automatically combining the sensible heat m·c·ΔT within each phase with the latent heat at every melting and boiling transition it crosses, and returns a step-by-step breakdown — so it can tell you, for example, the total energy to turn ice at −10 °C all the way into steam at 110 °C, using the right specific heat for the solid, the liquid and the gas. The substances endpoint lists the latent heats and per-phase specific heats. Heat is reported in joules, kilojoules, watt-hours and kilocalories. Everything is computed locally and deterministically, so it is instant and private. Ideal for thermodynamics and HVAC tools, refrigeration, heating and process-engineering apps, food and material science, and physics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is latent heat and phase change; for sensible heat alone (Q = m·c·ΔT with no phase change) use a specific-heat API.

api.oanor.com/enthalpy-api

Thermal-expansion maths as an API, computed locally and deterministically. The linear endpoint computes how much a solid grows or shrinks when its temperature changes, ΔL = α·L0·ΔT, returning the change in length and the new length from an original length, a temperature change (given directly or as an initial and final temperature) and the linear expansion coefficient α — taken from a built-in material table (steel, aluminium, copper, concrete, glass, invar and more) or supplied directly; lengths accept metres, centimetres, millimetres, feet or inches. The volume endpoint computes volumetric expansion, ΔV = β·V0·ΔT, where for a solid the volumetric coefficient is β ≈ 3α and for a liquid (water, ethanol, mercury, petrol and others) β is taken directly; volumes accept cubic metres, litres, millilitres or cubic feet. The materials endpoint lists the coefficients. A negative temperature change gives contraction. Everything is computed locally and deterministically, so it is instant and private. Ideal for civil and mechanical engineering tools, rail, pipe and bridge expansion-gap design, manufacturing-tolerance and HVAC apps, and physics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is thermal expansion; for heat energy and temperature change use a specific-heat API.

api.oanor.com/thermalexpansion-api

Calorimetry (specific-heat) maths as an API, computed locally and deterministically. The heat endpoint applies the sensible-heat equation Q = m·c·ΔT — the heat energy equals the mass times the specific heat times the temperature change — and solves for whichever of the four quantities you leave out, taking the temperature change directly or as the difference of an initial and final temperature, and the specific heat directly or from a built-in material (water, ice, aluminium, copper, steel, glass, ethanol and more); it reports the heat in joules, kilojoules, calories, kilocalories and watt-hours. The mix endpoint finds the equilibrium temperature when two bodies at different temperatures are brought into thermal contact, Tf = (m1·c1·T1 + m2·c2·T2) / (m1·c1 + m2·c2), with the heat transferred, for the same or different materials. The materials endpoint lists typical specific heats. Use SI units — mass in kilograms, specific heat in joules per kilogram-kelvin, temperatures in °C or K (the difference is the same). Everything is computed locally and deterministically, so it is instant and private. Ideal for physics and chemistry education, thermal-engineering and HVAC tools, cooking and brewing apps, and material-science calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is calorimetry; for the ideal gas law use a gas-law API.

api.oanor.com/specificheat-api

Ideal-gas-law maths as an API, computed locally and deterministically. The ideal endpoint solves PV = nRT for whichever quantity you leave out: provide any three of pressure, volume, amount of substance (moles) and temperature, and it returns the fourth in several units. The combined endpoint applies the combined gas law, P₁V₁/T₁ = P₂V₂/T₂: give a first state and two quantities of the second state and it finds the missing one — handy for "what happens to the volume if I double the pressure" questions. The density endpoint computes the density of an ideal gas from the pressure, temperature and molar mass (ρ = P·M / R·T). Pressure accepts pascals, kPa, bar, atm, psi, mmHg and Torr; volume accepts m³, litres, mL and cubic feet; temperature accepts kelvin, Celsius and Fahrenheit; and the gas constant R is 8.314462618 J/(mol·K). Everything is computed in SI internally and is instant and private. Ideal for chemistry and physics education, lab and process tools, HVAC and scuba calculations, and engineering software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is ideal-gas thermodynamics; for the chemical elements and periodic-table data use an elements API.

api.oanor.com/gaslaw-api