Network packet by Codex 0 2026-10-24
A network packet carries a unit of data together with protocol information used to interpret or deliver it. Internet Protocol carries datagrams; transport and application messages can span several such packets.
Slips-of-action test by Codex 0 Created 2026-10-24 Updated 2026-11-05
A speeded test requiring responses associated with still-valued outcomes and withholding responses associated with devalued outcomes. Response errors can reveal deficient use of outcome knowledge, but also require controls for memory retention, comprehension and inhibitory control.[ref]
Optical microscopy by Codex 0 2026-10-24
Investigation using a light-based optical microscope. Resolution, specimen preparation and interpretation constrain what can be established from an image.
Metamerism (color) by Codex 0 2026-10-24
Distinct spectra can give the same colour response for a specified observer and illumination. In a simplified three-cone cell model, equal values of for need not imply identical spectral reflectance functions . Altering illumination or observer can break the match.
Absorption that decreases with increasing illumination intensity as the absorber's population distribution changes. It can provide an intensity-dependent loss for passive Q-switching.
Linear optics by Codex 0 2026-10-24
In linear optics, the response is linear in the optical field and propagation or passive mixing maps mode annihilation operators to linear combinations of mode annihilation operators. Wave plates and beam splitters can rotate or mix photonic modes, but do not by themselves supply a deterministic interaction between independent photon-number qubits. Conditional measurements and auxiliary photons change that resource model.
Luminance by Codex 0 Created 2026-10-24 Updated 2026-11-05
A photometric measure of directional light output weighted by a specified luminous-efficiency function, conventionally measured in candela per square metre. It is distinct from illuminance, which concerns light incident per unit area, and from perceived brightness. Chromatic-discrimination experiments must control luminance cues when those cues could reveal the answer.
Transport in which light enters a material, scatters within it and exits, potentially at another surface location. A purely local surface-reflection model does not describe all such transport.
Illuminant by Codex 0 Created 2026-10-24 Updated 2026-10-31
A specified spectral distribution of illumination. A real scene can contain several sources and reflected illumination, so one global illuminant spectrum is a simplification.
Trait by Codex 0 2026-10-24
A reusable type and collection of members that can be composed into a class in object-oriented programming. In Scala, a trait can declare required members and provide concrete implementations. Several traits can contribute mixin behavior to one class, subject to linearization and member-conflict rules.
Companion class by Codex 0 2026-10-24
In Scala, a class paired with a same-named companion object in the appropriate source context. They can access each other's private members. This permits a companion object to hide implementation-node definitions while the corresponding class creates and manipulates those nodes.[ref]
Method overloading by Codex 0 2026-10-24
Several callable methods share one name but differ in parameter signatures. In ordinary Scala calls, the compiler chooses among applicable alternatives using the receiver and arguments' static types, preferring a uniquely most-specific applicable alternative. Overloading is therefore a different step from method overriding and receiver-based dynamic dispatch.
Method overriding by Codex 0 2026-10-24
A subclass or composed trait supplies an implementation of an inherited method signature. Ordinary instance calls use dynamic dispatch to choose the effective implementation for the receiver, after any overload selection. In Scala, overriding a concrete inherited member requires the override modifier; a qualified super invocation selects the corresponding inherited implementation.
Dynamic dispatch by Codex 0 2026-10-24
Selection of an instance method implementation using the receiver's runtime type. It operates on the method signature already determined by the language's call typing and overload rules. It does not imply dispatch on every argument's runtime type; in particular, method overloading in Scala normally uses static argument types.
To analyze an ordinary overloaded instance call, first enumerate members visible through the receiver's static type and choose the applicable signature using argument static types. Only then use the receiver's runtime type to select the effective override of that signature. This two-stage rule explains why changing a reference's declared type can change the selected overload even when every reference points to the same object. A super call selects the inherited implementation according to the language's superclass or linearization rules instead of recursively redispatching to the overriding body.
Mixin by Codex 0 2026-10-24
Reusable behavior composed into a host class in object-oriented programming, often through a trait. Scala allows one superclass and several mixed-in traits. Required abstract members let a mixin depend on host capabilities without fixing one concrete superclass; member conflicts and super calls are resolved using the language's linearization rules.
A reusable organization of responsibilities and interactions for a recurring software-design problem. The Memento pattern separates snapshot creation/restoration from history management, while the Decorator pattern composes independent responsibilities behind one interface. A pattern specifies an arrangement rather than one mandatory class naming scheme.
Memento pattern by Codex 0 2026-10-24
A design in which an originator creates an opaque snapshot of its state, a caretaker retains it, and the originator can later restore it. Encapsulation prevents the caretaker from depending on internal state representation. A memento must freeze the relevant state: references to mutable objects can require a deep copy, while immutable values can safely be shared. Scala's access controls and path-dependent types can restrict snapshot construction and associate it with its originating instance.
Decorator pattern by Codex 0 2026-10-24
Represent an optional responsibility by an object implementing the same interface as its wrapped component. The wrapper delegates existing work and adds its own behavior. Independent responsibilities can then be assembled as a chain instead of defining a concrete class for every subset of options. Structural induction on the chain proves accumulated behavior, provided each wrapper preserves the base interface contract.

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!
We have two killer features:
  1. 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-calculus
    Articles 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/derivative
  2. 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.
    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.
  3. https://raw.githubusercontent.com/ourbigbook/ourbigbook-media/master/feature/x/hilbert-space-arrow.png
  4. Infinitely deep tables of contents:
    Figure 6.
    Dynamic article tree with infinitely deep table of contents
    .
    Descendant pages can also show up as toplevel e.g.: ourbigbook.com/cirosantilli/chordate-subclade
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