Critical valve-closure time
API · /waterhammer-api
Water Hammer API
Water-hammer (hydraulic-transient) maths as an API, computed locally and deterministically — the surge-pressure, wave-speed and valve-timing numbers a piping or plumbing engineer guards a system with. The surge endpoint applies the Joukowsky equation Δp = ρ · a · Δv: a sudden stop of the flow spikes the pressure by the fluid density × the pressure-wave speed × the velocity change — stopping 2 m/s of water at a ≈ 1200 m/s adds about 24 bar (348 psi), far above the line pressure, which is what bangs the pipes and can split fittings. The wave-speed endpoint gives that pressure-wave speed: a = √(K/ρ) in a rigid pipe (≈ 1,480 m/s for water), slowed in a real elastic pipe to √(K/ρ) ÷ √(1 + (K·D)/(E·t)) — a thin or plastic pipe gives a lower wave speed and a gentler surge, which is why PVC tolerates hammer better than steel. The critical-time endpoint gives 2L/a, the round-trip time of the wave: close a valve faster than this and you get the full Joukowsky surge, slower and the returning relief wave eats into it, so sizing closure times (or fitting a surge tank or air chamber) above the critical time is the standard cure. Everything is computed locally and deterministically, so it is instant and private. Ideal for piping- and plumbing-design tools, pump-station and pipeline-surge analysis, and hydraulic-engineering utilities. Pure local computation — no key, no third-party service, instant. Idealised single-pipe transient. 3 compute endpoints. For steady pipe pressure drop use a Darcy API; for pump head and affinity a pump API.
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 82 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 3,906
- attiva
- Chiamate totali
- 0
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 4,900 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 4.900 Aufrufe/Monat
- 2 req/sec
- Surge + Wave Speed + Critical Time
- Keine Kreditkarte
Starter
€12.60 /mese
- 50,500 chiamate/mese
- 6 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 50.500 Aufrufe/Monat
- 6 req/sec
- Elastic-pipe wave speed
- E-Mail-Support
Pro
€39.00 /mese
- 216,000 chiamate/mese
- 15 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 216.000 Aufrufe/Monat
- 15 req/sec
- Pipeline & Pumpstation-Druckstoßleitungen
- Priority-Support
Mega
€120.50 /mese
- 1,125,000 chiamate/mese
- 40 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 1.125.000 Aufrufe/Monat
- 40 req/sec
- Firm & utility scale
- Dedicated SLA
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
Hydraulic Cylinder API
Hydraulic-cylinder engineering maths as an API, computed locally and deterministically — the force, speed and oil-volume numbers a fluid-power designer, machine builder or hydraulics technician sizes a cylinder with. The force endpoint gives the push and pull from the bore, rod diameter and working pressure: extending, the oil acts on the full bore area, so the cylinder is strongest pushing out; retracting, it acts only on the annulus left by the rod, giving less force — a 100 mm bore with a 56 mm rod at 160 bar pushes about 125.7 kN out but pulls only 86.3 kN back, which is why a press or an excavator does its hard work on the extend stroke. The speed endpoint gives the piston speed from the pump flow (speed = flow ÷ area), so extending is the slower stroke and retracting the faster, the trade-off every circuit designer balances against force. The volume endpoint gives the swept oil volume per stroke for extend and retract, the rod displacement and the bore-to-annulus area ratio — the differential (regeneration) ratio used to speed the extend stroke in a regen circuit — so the pump, tank and lines can be sized for the larger volume. Everything is computed locally and deterministically, so it is instant and private. Ideal for fluid-power and machine-design tools, hydraulics-sizing calculators, mobile- and industrial-equipment utilities, and engineering apps. Pure local computation — no key, no third-party service, instant. Ideal-area estimates — allow for friction, back-pressure and efficiency. 3 compute endpoints. For Pascal force-multiplication use a hydraulics API; for valve sizing a valve-flow (Cv/Kv) API.
api.oanor.com/hydrauliccylinder-api
O-Ring Seal API
O-Ring-Dichtungs-Design-Mathematik als API, lokal und deterministisch berechnet – die Squeeze-, Gland- und Stretch-Werte, die ein Ingenieur oder Hersteller für eine Dichtung entwirft. Der Squeeze-Endpunkt liefert die Kompression, die die Dichtung bewirkt: Squeeze = (Querschnitt − Nuttiefe) ÷ Querschnitt, also wird eine 0,139-Zoll-Schnur in einer 0,113-Zoll-tiefen Nut um 18,7 % gequetscht, und bewertet das Ergebnis – etwa 10–16 % eignet sich für dynamische (hin- und hergehende) Dichtungen und 15–30 % für statische – und, bei gegebener Nutbreite, den Nutfüllgrad, der unter etwa 85 % bleiben sollte, damit der Gummi Platz zum Ausdehnen durch Hitze oder Flüssigkeitsquellung hat. Der Gland-Endpunkt arbeitet umgekehrt: Aus dem Querschnitt und ob die Dichtung statisch oder dynamisch ist (oder einem Ziel-Squeeze) gibt er die Nuttiefe und eine Breite zurück, die für etwa 70 % Füllung ausgelegt ist – typischerweise das 1,3- bis 1,5-fache des Querschnitts – plus einen Eckradius. Der Stretch-Endpunkt prüft die Installation: Stretch = (Paarungsdurchmesser − O-Ring-ID) ÷ ID, der unter etwa 5 % auf einer Stange bleiben sollte, da Dehnung den Querschnitt verringert und Squeeze stiehlt. Alles wird lokal und deterministisch berechnet, daher ist es sofort und privat. Ideal für App-Entwickler im Maschinenbau, Hydraulik, Pneumatik, Vakuum- und Produktdesign, Dichtungsauswahl- und Nutdesign-Tools sowie CAD-Plugins. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofort. Zoll oder Millimeter. Live, nichts gespeichert. 3 Compute-Endpunkte.
api.oanor.com/oring-api
API de Eflujo de Torricelli
Matemáticas de eflujo de Torricelli y descarga por orificio como una API, calculadas local y determinísticamente. El endpoint de velocidad aplica la ley de Torricelli, v = √(2·g·h) — la velocidad a la que un fluido sale de un orificio bajo una carga h es igual a la de un cuerpo que ha caído la misma altura — y devuelve la velocidad ideal y real del chorro (corregida por un coeficiente de velocidad), y, si se proporciona el diámetro o área del orificio, el caudal volumétrico ideal y real Q = Cd·A·√(2gh) en litros por segundo y minuto, metros cúbicos por hora y galones estadounidenses por minuto. El endpoint de tiempo de vaciado calcula cuánto tarda un tanque cilíndrico vertical en vaciarse a través de un orificio, t = (2·A_tanque)/(Cd·A_orificio·√(2g))·(√h0 − √h1), a partir de los tamaños del tanque y del orificio, la carga inicial y una carga final opcional, con el caudal inicial. El endpoint de alcance da la distancia horizontal que recorre un chorro desde un orificio lateral antes de caer, x = 2·Cv·√(h·y), a partir de la carga sobre el orificio y la altura del orificio sobre el suelo, con la velocidad del chorro y el tiempo de vuelo. Los coeficientes de descarga y velocidad tienen valores predeterminados de 0.62 y 0.97 y pueden ser anulados, al igual que la gravedad. Todo se calcula local y determinísticamente, por lo que es instantáneo y privado. Ideal para herramientas de mecánica de fluidos e hidráulica, drenaje de tanques, riego y aplicaciones de ingeniería de procesos, y educación en física. Cálculo puramente local — sin clave, sin servicio de terceros, instantáneo. En vivo, no se almacena nada. 3 endpoints. Esto es eflujo por orificio y drenaje de tanques; para continuidad en tuberías Q = A·v use una API de caudal y para volumen y nivel de tanque use una API de tanque.
api.oanor.com/torricelli-api
Open Channel Flow API
Open-channel flow maths as an API, computed locally and deterministically with the Manning equation. The flow endpoint computes the discharge and velocity of water in an open channel — rectangular, trapezoidal, triangular or circular (a part-full pipe) — from the flow depth, the channel dimensions, the channel slope and the Manning roughness coefficient n: it works out the flow area, the wetted perimeter and the hydraulic radius, then applies Q = (1/n)·A·R^(2/3)·S^(1/2) and V = Q/A, reporting the discharge in cubic metres per second and hour, litres per second, cubic feet per second and US gallons per minute. The normal-depth endpoint reverses it: given a target discharge it solves for the normal depth by bisection and returns the resulting area, velocity and a discharge check. The roughness endpoint is a reference of typical Manning n values, from smooth PVC (0.009) and concrete (0.013) through earth and gravel to rocky natural streams (0.05); pass a material name or an explicit n. Dimensions are metric (metres by default, or cm, mm, ft, in). Everything is computed locally and deterministically, so it is instant and private. Ideal for civil and drainage engineering tools, stormwater and culvert design, irrigation and hydrology apps, and environmental modelling. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is open-channel (Manning) hydraulics; for full-pipe flow rate from diameter and velocity use a pipe-flow API.
api.oanor.com/manning-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Water Hammer API?
Qual è il limite di velocità di Water Hammer API?
Quanto costa Water Hammer API?
Posso cancellare l'abbonamento in qualsiasi momento?
Water Hammer API è conforme al GDPR?
Scegli un endpoint dall'elenco a sinistra per visualizzarne i dettagli e provarlo.
Frammenti di codice
Iscriviti per ottenere una chiave API, quindi chiama qualsiasi percorso sotto il tuo slug.
curl https://api.oanor.com/waterhammer-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/waterhammer-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/waterhammer-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/waterhammer-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Valutazioni
Accedi per votare.
Nessuna recensione ancora.
Discussione
Fai domande, condividi consigli, ricevi risposte dal provider e dagli altri sviluppatori. Pubblico — chiunque può leggere.
Accedi per scrivere o rispondere.
AccediNuova discussione
·
-
Risposta del provider
🔒 Discussione bloccata — non si può più rispondere.
-
·
- Nessuna discussione — inizia tu.
Supporto
Supporto privato 1:1 con il provider — fatturazione, integrazione, account. Solo tu e il team del provider vedete questi thread.
Accedi per aprire un ticket di supporto.
AccediApri nuovo ticket
Descrivi cosa ti serve. Il team del provider riceve un'email e risponde sulla pagina del ticket.
-
·
Urgente - Nessun ticket per questa API.