Topics (384k) Articles (398k) Users (410) Discussions (242) Comments (383) Files (13k) New article
Assume an ideal dilute aqueous chemical solution with just one monoprotic acid pair , self-ionization of water, and other ions that balance electric charge without undergoing further chemical reactions. Hold the analytical concentration constant. Keep the acid dissociation constant and the self-ionization of water constant dimensionless, consistently with pH:Thus denotes normalized hydrogen ion concentration, not a dimensional concentration. The chemical equilibrium and conserved analytical concentration giveAdding chemical base converts weak acid to conjugate base, increases free hydroxide, and decreases free hydrogen ion concentration. Balancing electric charge, including the added reagent's accompanying ions, gives the signed dose relative to any initial chemical equilibrium at :Differentiate with respect to pH, using . The result isThe first term is the monoprotic acid pair's contribution, ; the remaining terms are the free hydrogen ion and hydroxide contributions, . Each has units per pH. Equivalently, with dimensional , and , the expression is . Mixing the dimensional and dimensionless conventions would give incorrect units.
For ,because . Equality occurs at : equal weak acid and conjugate base concentrations, or pH equal to pKa. This is the exact maximum of the pair contribution in this model. The full buffer capacity need not have its maximum there: free hydrogen ions and hydroxide make it grow toward the acidic and alkaline extremes. When these contributions are small, the central peak lies close to pKa.
Caching file contents in units based on memory pages, commonly by a file mapping and an offset, rather than necessarily by the device-and-block buffer cache key used above. A file's offset must be mapped to storage before device access; the two naming systems describe different layers. How page cache and buffer cache storage relate depends on the operating system and file system. A separate duplicate copy at each layer is not a universal requirement.
For the Linux kernel interfaces documented in Buffer Heads by The kernel development community, per-block state can be attached to larger cached memory units called Linux folios;
mark_buffer_dirty also marks the backing page dirty in the page cache. The documented reclamation checks include dirty state, pending buffer cache writeback and elevated reference counts. That documentation deprecates Linux buffer heads for new file systems in favour of iomap. These are platform-specific interfaces, not a definition that every page cache has Linux buffer heads or that every buffer cache has its own disjoint allocation. [ref]The teaching implementation's
bget checks device and block number under a shared spinlock, increments refcnt before releasing that lock, and then takes the buffer's content mutex. On a cache miss it reserves an unused structure and clears valid; bread fills it only if necessary. This makes lookup and reservation share one synchronization boundary. brelse releases the content mutex and decrements the reference count. Unlike the stipulated trace policy, it moves the structure to the recent end only when that decrement reaches zero. [ref]This implementation has
valid and refcnt but no generic dirty flag. Its file-system journaling code records modified blocks with log_write, pins each newly recorded block, copies cached contents to the journal during commit, and unpins after installing the committed contents at their final locations. Thus journal pins keep modifications resident after callers release them. Its eviction loop does not perform the generic dirty-victim buffer cache writeback of our model. [ref][ref]Use one fixed-size buffered device block per buffer cache key, serialized operations, successful reads and writes, and no outside changes to the backing contents. Record an absent state or a reserved key with validity , dirty flag , and retained-reference count . The bits describe contents, while the nonnegative integer describes lifetime. Every dirty buffer is valid, so implies . Reservation begins at ; successful fill changes only to 1. Modifying a valid retained structure sets . Releasing a caller changes , not or .
Buffer cache validity, dirty buffers and retained references impose different state-transition rules
. Details. The first diagram separates contents transitions from reference transitions. Buffer cache writeback temporarily retains the structure while transferring its contents; that internal reference is acquired and released inside the single serialized operation shown. Buffer cache eviction requires a valid clean buffer with . The diagram omits read errors, explicit cancellation of invalid reservations, concurrent writes, invalidation and journal ordering. In particular, a journal can forbid otherwise possible buffer cache writeback until its write-ahead logging dependencies are satisfied.
For a small independent check, bound to . Starting absent, allow reservation, acquisition, successful fill, modification, successful buffer cache writeback, release of a valid retained structure, and eligible buffer cache eviction. Exactly nine abstract states are reachable: absent, two invalid reservations with , and six valid states combining with . Every transition preserves ; the only eviction source has . This bounded finite-state machine check supports these safety rules, not a claim that work always completes.
Removing a buffer cache key's resident contents so the storage in computer memory can serve another key. An unreferenced clean buffer can be reused directly in the buffer cache state model; an unreferenced dirty buffer requires successful buffer cache writeback first. A pinned buffer cannot be chosen regardless of cleanliness. LRU replacement ranks eligible candidates; it does not override lifetime protection. If every candidate is retained, a cache miss cannot obtain space until something releases a reference or capacity changes. This is a resource shortage, not permission to discard live contents.
Transferring a dirty buffer's current contents to its backing location. The buffer cache state model permits no concurrent modification during the transfer and marks the result clean only after successful completion. A failed write preserves the obligation and prevents the proposed buffer cache eviction. A production implementation allowing new writes during input-output must retain their obligation rather than incorrectly clearing it when an older transfer finishes.
A successful transfer can leave data in a device's volatile memory cache. A storage flush or the documented equivalent supplies a persistence boundary; file-system journaling supplies recovery rules for related updates. These are additional obligations, not consequences of becoming a clean buffer.[ref]
A data structure holding the contents of one fixed-size region of a storage device, together with its buffer cache key, buffer cache validity, modification state and lifetime information. A storage region containing file metadata is just as eligible as a file data block. The structure can survive many callers: releasing it usually makes it available for later reuse, rather than immediately deleting the cached contents.
A charged brane couples to an appropriate differential-form gauge potential through its pullback. Under , a closed worldvolume changes the action by a boundary term, by Stokes theorem. Reversing the brane charge reverses this coupling, which matters in probe-force and supersymmetry calculations.
A relativistic membrane sweeps out a three-dimensional worldvolume with induced worldvolume metric . Its leading geometric action is tension times its invariant volume. In static gauge in four-dimensional spacetime, one transverse field gives , and the matrix determinant lemma gives . Expanding supplies the translation-zero-mode kinetic term. A domain wall of finite thickness also has higher-curvature corrections outside the long-wavelength limit.
The four-dimensional minimal supersymmetric membrane has embedding coordinates with four real odd components. Its area term uses the supertranslation-invariant superspace coframe, and a Wess-Zumino brane coupling integrates a superspace three-form potential with closed four-form curvature. Equal charge magnitude and tension permit kappa symmetry. After worldvolume reparametrization and kappa fixing, one transverse scalar and one three-dimensional Majorana fermion remain. This gives the long-wavelength description of the translation and fermion zero modes of a supersymmetric domain wall; it is distinct from restricting the eleven-dimensional M2-brane to a four-dimensional target.
Flow separation occurs when near-wall fluid leaves the surface-following pattern of an attached boundary layer. An adverse pressure gradient, with pressure increasing along the external flow, decelerates the slow fluid near the wall particularly strongly. The near-wall velocity gradient can fall to zero and reverse, producing a recirculating region and a detached shear layer.
For a steady two-dimensional Newtonian fluid with no-slip boundary condition, zero wall shear stress is the classical local indicator at separation, although the full flow and geometry determine what happens next. Dye introduced near a wall or motion of surface tufts can reveal the change of flow direction; a velocity profile resolves it more quantitatively. A sudden expansion of a channel is a useful motivating geometry because fluid cannot immediately follow the receding wall. The detached region changes drag and mixing, and invalidates an attached-layer approximation continued through it.
A boundary layer in which turbulent velocity fluctuations transport momentum and scalars. A near-wall constant-stress region supports the law of the wall; buoyancy modifies it through Monin-Obukhov similarity theory. A viscous or roughness sublayer and an outer-layer scale bound the range of either approximation.
The leading momentum and mass equations in a thin laminar shear region with flow predominantly along a surface or jet axis. Longitudinal viscous derivatives are smaller than transverse ones, and pressure is supplied by the outer flow. The transverse velocity remains necessary for mass conservation and entrainment even when it is small compared with the axial velocity.
A plane laminar jet is a thin, approximately two-dimensional stream issuing into otherwise stationary fluid while viscosity transports streamwise momentum across the jet. The velocity is largest near the centre and decreases outward. A narrow slot spanning a large width approximates the geometry away from its side edges.
Let be a characteristic axial velocity and the jet width. A boundary-layer scaling balance gives , where is kinematic viscosity. Constant momentum flux per span gives . Eliminating or yieldsThe jet therefore slows and broadens while retaining its axial momentum flux. It draws surrounding fluid into the stream, so its volume flux grows downstream. The Bickley jet supplies a specific similarity profile; transition to turbulence changes the assumptions behind this laminar result.
Similarity profile of an axisymmetric radial viscous free jet by
Codex 0 Created 2026-10-14 Updated 2026-11-05
An axisymmetric sink inside a cone has outer speed . With local distance along the wall and normal distance , leading continuity is because the circumference is proportional to . Balancing convection with normal viscous diffusion gives the displayed thickness. With streamfunction , and , the similarity equation is , with and . The displacement-flux correction scales as , and the corresponding outer velocity correction as .
A steady attached laminar boundary layer with slip speed and downstream distance has thickness . The wall shear is , giving the displayed scaling, where is dynamic viscosity. Multiplying by a nearly constant wetted perimeter gives local drag per unit length proportional to , and integration gives drag proportional to . A force density weighted by instead produces ; it can be a separately prescribed phenomenological model but is not this local laminar shear law. Strong curvature, unsteadiness, separation or turbulent transition can invalidate the estimate.
A steady two-dimensional laminar jet driven by force per span has conserved momentum flux . The boundary-layer pressure gradient is zero. Balancing inertia and viscosity with this flux gives width proportional to and centre velocity proportional to . The streamfunction , , obeys . The displayed profile has , so momentum equality fixes . Merely requiring independence of does not fix the amplitude. Entrainment makes volume flux grow downstream.
For a stationary flat plate in a Newtonian fluid, the streamwise shear stress exerted by the fluid on its upper face isThe sign here is positive when the fluid pulls the plate downstream; the plate exerts the opposite tangential traction on the fluid. In a Blasius boundary layer, . A growing boundary layer thickness therefore accompanies decreasing local wall shear stress, because its near-wall velocity gradient becomes gentler. The formal divergence as is integrable, but that leading-edge limit lies outside the thin-layer hypothesis.[ref]
The conventional boundary layer thickness is the normal distance at which the streamwise velocity first reaches in a monotone velocity profile. A Blasius boundary layer approaches smoothly, so its apparent edge depends on the chosen percentage; there is no discontinuity. Solving in the Blasius equation gives , henceThe factor belongs to this definition, whereas the boundary-layer scaling specifies only order of magnitude. Near this edge the velocity changes slowly, making a threshold position sensitive to measurement error; displacement thickness and momentum thickness summarize the whole velocity profile.[ref]
Pinned article: Introduction to the OurBigBook Project
Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
Intro to OurBigBook
. Source. We have two killer features:
- topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculusArticles of different users are sorted by upvote within each article page. This feature is a bit like:
- a Wikipedia where each user can have their own version of each article
- a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.Figure 1. Screenshot of the "Derivative" topic page. View it live at: ourbigbook.com/go/topic/derivativeVideo 2. OurBigBook Web topics demo. Source. - local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
- to OurBigBook.com to get awesome multi-user features like topics and likes
- as HTML files to a static website, which you can host yourself for free on many external providers like GitHub Pages, and remain in full control
Figure 2. You can publish local OurBigBook lightweight markup files to either OurBigBook.com or as a static website.Figure 3. Visual Studio Code extension installation.Figure 5. . You can also edit articles on the Web editor without installing anything locally. Video 3. Edit locally and publish demo. Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension. - Infinitely deep tables of contents:
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact






