phenotypic.abc_.GridCorrector#
- class phenotypic.abc_.GridCorrector[source]#
Bases:
ImageCorrector,GridOperation,ABCApply whole-image transformations (rotation, alignment, perspective) to GridImage objects.
GridCorrector is a type-safe wrapper around ImageCorrector that enforces GridImage input and output types. It is specialized for grid-aware image corrections on arrayed plate images.
Quick Decision Guide
Choose GridCorrector vs ImageCorrector:
GridCorrector: Transformation modifies well structure or assumes grid layout. Examples: align colonies to grid axes, per-well perspective correction, rotation with grid-aware interpolation.
ImageCorrector: Transformation works on any Image. Examples: general rotation, perspective correction on ungridded images, generic image transformations without grid awareness.
Grid-aware operations: Use GridCorrector when grid rows/columns matter for the transformation or when the transformation affects well-level alignment and downstream analysis.
Type safety: GridCorrector enforces GridImage input/output; ImageCorrector accepts plain Image.
Implementation complexity: GridCorrector typically requires understanding grid.rotation_angle, grid.alignment, and per-well coordinate mapping via image.grid.info().
Output consistency: GridCorrector guarantees all components rotate identically. ImageCorrector gives you flexibility but requires manual synchronization of all components.
Grid preservation: GridCorrector may update grid state after transformation. ImageCorrector leaves grid structure unchanged (if present).
Purpose
Use GridCorrector when implementing transformations that modify entire GridImage objects while respecting their grid structure. Like ImageCorrector, it updates all image components (rgb, gray, detect_mat, objmask, objmap) together to maintain synchronization. The difference is that it requires GridImage input and output, making explicit that your transformation works in the context of grid-structured plate images.
What GridCorrector modifies
GridCorrector operations modify ALL image components simultaneously:
Color data: rgb, gray (pixel coordinates change due to rotation/perspective)
Preprocessed data: detect_mat (detection matrix also rotates/transforms)
Detection results: objmask, objmap (colony masks and labels transform identically)
Grid structure: Grid rotation angle and alignment state (optional, depends on operation)
This ensures that a rotated colony mask aligns perfectly with the rotated rgb and gray data.
GridImage vs Image
Image: Generic image with optional, unvalidated grid information.
GridImage: Specialized Image subclass with validated grid structure (row/column layout, well positions, grid alignment angle). Typically used after GridFinder detects the grid structure.
Typical Use Cases
Grid alignment: Rotate the entire image so detected colonies align with grid rows and columns. Improves downstream grid-based analysis via [GridAligner](src/phenotypic/correction/_grid_aligner.py).
Perspective correction: Correct camera tilt or lens distortion that skews the grid layout.
Plate reorientation: Rotate plate image to canonical orientation for consistent well assignment.
Color calibration per well: Apply per-well color correction that respects grid well boundaries.
Implementation Pattern
Inherit from GridCorrector and implement
_operate()as an instance method:from phenotypic.abc_ import GridCorrector from phenotypic import GridImage class GridAligner(GridCorrector): '''Rotate GridImage to align colonies with grid rows/columns.''' axis: int = 0 # Annotated class-level fields max_rotation: float = 45.0 def _operate(self, image: GridImage) -> GridImage: # image is guaranteed to be GridImage with valid grid structure # Access grid structure and compute needed transformation grid_info = image.grid.info() nrows, ncols = grid_info['grid_shape'] # Calculate rotation needed to align colonies with grid axes rotation_angle = self._calculate_grid_rotation(image, self.axis) # Clamp rotation to reasonable range to prevent over-correction if abs(rotation_angle) > self.max_rotation: rotation_angle = self.max_rotation * (1 if rotation_angle > 0 else -1) # Apply rotation to all image components automatically image.rotate(angle_of_rotation=rotation_angle, mode='edge') # Grid structure (rows/cols) unchanged; rotation_angle updated automatically return image
Critical Implementation Details
Ensure ALL image components are transformed identically:
Transformation synchronization: When you rotate/warp rgb, also rotate gray, detect_mat, objmask, objmap. Use image.rotate() or similar methods that handle this automatically. Failure to synchronize causes misalignment between visual and label data.
Coordinate system consistency: Grid coordinates (well centers, row/column positions) must match the transformed pixel coordinates. Update grid.rotation_angle and grid.alignment after transformation so downstream operations use correct well boundaries.
Grid state preservation: Maintain grid.rows, grid.cols, and grid.well_size unchanged unless explicitly needed (e.g., perspective correction may change well size). Update only rotation_angle and alignment for simple rotations.
Interpolation order: Use order=1+ for color data (smooth), order=0 for labels (preserve integers). Mixed interpolation on different components is OK and expected.
Edge handling: Define how image boundaries are handled during transformation (reflect, wrap, constant). Choose mode=’edge’ or mode=’constant’ depending on plate structure and whether border wells matter.
In-place vs return: GridCorrector operations typically modify image in-place AND return it. Follow this pattern for consistency with parent ImageCorrector class.
Interpolation Considerations
When rotating or warping:
Color data (rgb, gray): Use smooth interpolation (order=1+) to preserve colony edges
Detection data (objmask, objmap): Use nearest-neighbor interpolation (order=0) to preserve discrete object labels (must remain integers)
Detection matrix: Use same interpolation as color data for consistency
Common Transformations
Rotation: Most common GridCorrector operation. Rotate entire plate to align colonies with grid axes. Use image.rotate(angle_of_rotation, mode=’edge’) to handle all components automatically.
Perspective correction: Correct camera tilt or lens distortion. More complex; requires affine or homography transformation on all components with careful interpolation.
Scale and crop: Resize plate image while maintaining grid structure. Update grid.well_size accordingly.
Flip/transpose: Flip or transpose plate (e.g., for reorientation). Update grid rows/cols and rotation_angle.
Best Practices
Always verify grid structure is valid before applying GridCorrector (check grid.rows, grid.cols > 0).
Test transformation on synthetic data first; grid misalignment can cascade through entire pipeline.
Update grid metadata (rotation_angle, alignment) immediately after transformation for consistency.
Log the transformation (angle, parameters) for reproducibility and debugging.
Consider edge well effects (evaporation, contamination); some corrections may need well-specific logic.
Notes
GridCorrector has no integrity checks (@validate_operation_integrity), by design. All components are intentionally modified together; there is nothing to validate.
Grid rotation angle and alignment state may be updated after the transformation. Downstream grid-aware operations will work with the updated grid structure.
GridImage must have valid grid structure before correction. Use GridFinder or specify grid manually before applying GridCorrector.
Output is always GridImage (type-safe). Attempting to apply to plain Image raises error.
Coordinate system: Grid rows/cols are logical indices; transformation affects pixel coordinates only. Update rotation_angle to track cumulative transformations.
Relationship to GridFinder and GridOperation
GridFinder: Detects grid structure automatically. Use BEFORE GridCorrector to establish rows/cols.
GridCorrector: Adjusts/aligns detected grid. Use AFTER GridFinder to optimize grid alignment.
GridOperation: Base class for all grid-aware operations. GridCorrector is a specialized subclass that combines ImageCorrector functionality with grid awareness.
Pipeline integration: Typical order: detect_grid (GridFinder) → correct_grid (GridCorrector) → measure/analyze (GridMeasureFeatures).
Image Synchronization Details
When implementing
_operate(), ensure these components stay in sync:rgb & gray: Always rotate together. Gray is derived from rgb, so maintain pixel correspondence.
detect_mat: Detection matrix processed from gray. Must rotate with same angle/transformation.
objmask & objmap: Detection results. Must use SAME interpolation as rgb to maintain object alignment.
Grid metadata: Update grid.rotation_angle if rotation applied. Keep grid.rows/cols unchanged unless grid structure itself changes.
Example Coordinate Transformation
For a 96-well plate rotated by θ degrees:
Original well positions: grid.info()[‘well_centers’] in absolute pixel coordinates
After rotation by θ: well_centers shift to new pixel positions
Update grid.rotation_angle += θ
Grid rows/cols (logical structure) remain unchanged (8 rows × 12 cols)
Known Implementations
Reference implementations in the PhenoTypic framework:
[GridAligner](src/phenotypic/correction/_grid_aligner.py): Rotates entire image to align detected colonies with grid rows and columns. Uses Hough transform to detect dominant angles in colony positions.
ImageRotation (ImageCorrector): Simple rotation without grid awareness. Baseline for understanding how GridCorrector extends basic functionality with grid metadata updates.
Custom implementations: Users can subclass GridCorrector for domain-specific plate corrections (e.g., multi-stage perspective correction, plate-specific calibrations).
Testing GridCorrector Implementations
Best practices for testing new GridCorrector subclasses:
Use
load_synth_yeast_plate()from phenotypic.data (creates GridImage with synthetic colonies).Verify all components (rgb, gray, detect_mat, objmask, objmap) rotate identically by computing pixel differences before/after transformation.
Check that grid.rotation_angle is updated correctly and accumulated rotations are tracked.
Validate on multiple plate formats (96-well, 384-well) to ensure well positions are handled correctly.
Examples
GridAligner: rotate to align colonies with grid axes:
>>> from phenotypic import GridImage, Image >>> from phenotypic.detect import RoundPeaksDetector >>> from phenotypic.correction import GridAligner >>> # Load and detect colonies >>> image = Image('plate.jpg') >>> image = RoundPeaksDetector().operate(image) >>> # Create GridImage with grid structure >>> grid_image = GridImage(image) >>> grid_image.detect_grid() >>> # Align entire image to grid rows/columns >>> aligner = GridAligner(axis=0) # Align rows horizontally >>> aligned = aligner.apply(grid_image) >>> # All components (rgb, gray, masks, map) rotated together >>> # Grid structure updated to reflect rotation >>> print(f"Rotation angle: {aligned.grid.rotation_angle}")
Custom perspective correction (conceptual):
>>> from phenotypic.abc_ import GridCorrector >>> from phenotypic import GridImage >>> class GridPerspectiveCorrector(GridCorrector): ... '''Correct camera tilt or lens distortion on grid plate.''' ... ... tilt_angle: float # Annotated class-level field ... ... def _operate(self, image: GridImage) -> GridImage: ... # Apply perspective transform to all components ... # Update grid coordinates accordingly ... grid_info = image.grid.info() ... image.apply_perspective(self.tilt_angle) ... # Re-validate grid after transformation ... return image >>> # Usage: correct skewed plate image >>> corrector = GridPerspectiveCorrector(tilt_angle=10.0) >>> corrected = corrector.apply(grid_image)
Methods
Create a new model by parsing and validating input data from keyword arguments.
Calculates the optimal rotation angle and applies it to a grid image for alignment along the specified axis.
Returns a copy of the model.
Reconstruct an operation from JSON written by
to_json().Creates a new instance of the Model class with validated data.
!!! abstract "Usage Documentation"
!!! abstract "Usage Documentation"
!!! abstract "Usage Documentation"
Generates a JSON schema for a model class.
Compute the class name for parametrizations of generic classes.
Initialize logging and memory tracking after model construction.
Try to rebuild the pydantic-core schema for the model.
Validate a pydantic model instance.
!!! abstract "Usage Documentation"
Validate the given object with string data against the Pydantic model.
Serialize this operation to JSON.
Return (and optionally display) the root widget.
Attributes
Configuration for the model, should be a dictionary conforming to [ConfigDict][pydantic.config.ConfigDict].
Get extra fields set during validation.
Returns the set of fields that have been explicitly set on this model instance.
- apply(image: GridImage, inplace=False) GridImage[source]#
Calculates the optimal rotation angle and applies it to a grid image for alignment along the specified axis.
The method performs alignment of a GridImage object along either nrows or columns based on the specified axis. It calculates the linear regression slope and intercept for the axis, determines geometric properties of the grid vertices, and computes rotation angles needed to align the image. The optimal angle is found by minimizing the error across all computed angles, and the image is rotated accordingly.
- Raises:
ValueError – If the axis is not 0 (row-wise) or 1 (column-wise).
- Parameters:
image (ImageGridHandler) – The arr grid image object to be aligned.
- Returns:
The rotated grid image object after alignment.
- Return type:
ImageGridHandler
- __del__()#
Automatically stop tracemalloc when the object is deleted.
- classmethod __get_pydantic_json_schema__(core_schema: CoreSchema, handler: GetJsonSchemaHandler, /) JsonSchemaValue#
Hook into generating the model’s JSON schema.
- Parameters:
core_schema (CoreSchema) – A pydantic-core CoreSchema. You can ignore this argument and call the handler with a new CoreSchema, wrap this CoreSchema ({‘type’: ‘nullable’, ‘schema’: current_schema}), or just call the handler with the original schema.
handler (GetJsonSchemaHandler) – Call into Pydantic’s internal JSON schema generation. This will raise a pydantic.errors.PydanticInvalidForJsonSchema if JSON schema generation fails. Since this gets called by BaseModel.model_json_schema you can override the schema_generator argument to that function to change JSON schema generation globally for a type.
- Returns:
A JSON schema, as a Python object.
- Return type:
JsonSchemaValue
- __init__(**data: Any) None#
Create a new model by parsing and validating input data from keyword arguments.
Raises [ValidationError][pydantic_core.ValidationError] if the input data cannot be validated to form a valid model.
self is explicitly positional-only to allow self as a field name.
- Parameters:
data (Any)
- Return type:
None
- __pretty__(fmt: Callable[[Any], Any], **kwargs: Any) Generator[Any]#
Used by devtools (https://python-devtools.helpmanual.io/) to pretty print objects.
- classmethod __pydantic_init_subclass__(**kwargs: Any) None#
Populate field descriptions from the subclass docstring.
Runs once per concrete subclass after pydantic has built its model. Copies parameter descriptions parsed from the Google-style
Args:docstring block onto each field’sdescriptionslot so they surface inmodel_json_schema()— the machine-readable contract used by downstream tooling (e.g. an MCP server).- Parameters:
**kwargs (Any) – Class-keyword arguments forwarded by pydantic.
- Return type:
None
- classmethod __pydantic_on_complete__() None#
This is called once the class and its fields are fully initialized and ready to be used.
This typically happens when the class is created (just before [__pydantic_init_subclass__()][pydantic.main.BaseModel.__pydantic_init_subclass__] is called on the superclass), except when forward annotations are used that could not immediately be resolved. In that case, it will be called later, when the model is rebuilt automatically or explicitly using [model_rebuild()][pydantic.main.BaseModel.model_rebuild].
- Return type:
None
- __rich_repr__() RichReprResult#
Used by Rich (https://rich.readthedocs.io/en/stable/pretty.html) to pretty print objects.
- Return type:
RichReprResult
- copy(*, include: AbstractSetIntStr | MappingIntStrAny | None = None, exclude: AbstractSetIntStr | MappingIntStrAny | None = None, update: Dict[str, Any] | None = None, deep: bool = False) Self#
Returns a copy of the model.
- !!! warning “Deprecated”
This method is now deprecated; use model_copy instead.
If you need include or exclude, use:
`python {test="skip" lint="skip"} data = self.model_dump(include=include, exclude=exclude, round_trip=True) data = {**data, **(update or {})} copied = self.model_validate(data) `- Parameters:
include (AbstractSetIntStr | MappingIntStrAny | None) – Optional set or mapping specifying which fields to include in the copied model.
exclude (AbstractSetIntStr | MappingIntStrAny | None) – Optional set or mapping specifying which fields to exclude in the copied model.
update (Dict[str, Any] | None) – Optional dictionary of field-value pairs to override field values in the copied model.
deep (bool) – If True, the values of fields that are Pydantic models will be deep-copied.
- Returns:
A copy of the model with included, excluded and updated fields as specified.
- Return type:
Self
- dict(*, include: set[int] | set[str] | Mapping[int, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | Mapping[str, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | None = None, exclude: set[int] | set[str] | Mapping[int, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | Mapping[str, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | None = None, by_alias: bool = False, exclude_unset: bool = False, exclude_defaults: bool = False, exclude_none: bool = False) Dict[str, Any]#
- Parameters:
include (set[int] | set[str] | Mapping[int, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | Mapping[str, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | None)
exclude (set[int] | set[str] | Mapping[int, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | Mapping[str, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | None)
by_alias (bool)
exclude_unset (bool)
exclude_defaults (bool)
exclude_none (bool)
- Return type:
- classmethod from_json(json_data: str | Path | dict) BaseOperation#
Reconstruct an operation from JSON written by
to_json().Accepts a JSON string, a path to a JSON file, or a pre-parsed envelope dict (same input handling as
ImagePipeline.from_json()). Polymorphic:ImageOperation.from_json(path)returns whatever concrete operation the file holds. When called on a narrower subclass, the resolved class must be a subclass of it, else aTypeErroris raised.- Parameters:
json_data (str | Path | dict) – A JSON string, path to a JSON file, or envelope dict.
- Returns:
The reconstructed operation instance.
- Raises:
AttributeError – If the recorded class cannot be resolved in the
phenotypicnamespace.TypeError – If called on a concrete subclass and the file holds a class that is not a subclass of it.
- Return type:
Example
>>> import tempfile >>> from pathlib import Path >>> from phenotypic.abc_ import ImageOperation >>> from phenotypic.detect import OtsuDetector >>> with tempfile.TemporaryDirectory() as d: ... p = Path(d) / "op.json" ... OtsuDetector().to_json(p) ... loaded = ImageOperation.from_json(p) # polymorphic >>> type(loaded).__name__ 'OtsuDetector'
- json(*, include: set[int] | set[str] | Mapping[int, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | Mapping[str, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | None = None, exclude: set[int] | set[str] | Mapping[int, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | Mapping[str, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | None = None, by_alias: bool = False, exclude_unset: bool = False, exclude_defaults: bool = False, exclude_none: bool = False, encoder: Callable[[Any], Any] | None = PydanticUndefined, models_as_dict: bool = PydanticUndefined, **dumps_kwargs: Any) str#
- Parameters:
include (set[int] | set[str] | Mapping[int, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | Mapping[str, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | None)
exclude (set[int] | set[str] | Mapping[int, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | Mapping[str, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | None)
by_alias (bool)
exclude_unset (bool)
exclude_defaults (bool)
exclude_none (bool)
models_as_dict (bool)
dumps_kwargs (Any)
- Return type:
- model_computed_fields = {}#
- model_config: ClassVar[ConfigDict] = {'arbitrary_types_allowed': True, 'extra': 'forbid', 'validate_assignment': True}#
Configuration for the model, should be a dictionary conforming to [ConfigDict][pydantic.config.ConfigDict].
- classmethod model_construct(_fields_set: set[str] | None = None, **values: Any) Self#
Creates a new instance of the Model class with validated data.
Creates a new model setting __dict__ and __pydantic_fields_set__ from trusted or pre-validated data. Default values are respected, but no other validation is performed.
- !!! note
model_construct() generally respects the model_config.extra setting on the provided model. That is, if model_config.extra == ‘allow’, then all extra passed values are added to the model instance’s __dict__ and __pydantic_extra__ fields. If model_config.extra == ‘ignore’ (the default), then all extra passed values are ignored. Because no validation is performed with a call to model_construct(), having model_config.extra == ‘forbid’ does not result in an error if extra values are passed, but they will be ignored.
- Parameters:
_fields_set (set[str] | None) – A set of field names that were originally explicitly set during instantiation. If provided, this is directly used for the [model_fields_set][pydantic.BaseModel.model_fields_set] attribute. Otherwise, the field names from the values argument will be used.
values (Any) – Trusted or pre-validated data dictionary.
- Returns:
A new instance of the Model class with validated data.
- Return type:
- model_copy(*, update: Mapping[str, Any] | None = None, deep: bool = False) Self#
- !!! abstract “Usage Documentation”
[model_copy](../concepts/models.md#model-copy)
Returns a copy of the model.
- !!! note
The underlying instance’s [__dict__][object.__dict__] attribute is copied. This might have unexpected side effects if you store anything in it, on top of the model fields (e.g. the value of [cached properties][functools.cached_property]).
- model_dump(*, mode: Literal['json', 'python'] | str = 'python', include: set[int] | set[str] | Mapping[int, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | Mapping[str, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | None = None, exclude: set[int] | set[str] | Mapping[int, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | Mapping[str, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | None = None, context: Any | None = None, by_alias: bool | None = None, exclude_unset: bool = False, exclude_defaults: bool = False, exclude_none: bool = False, exclude_computed_fields: bool = False, round_trip: bool = False, warnings: bool | Literal['none', 'warn', 'error'] = True, fallback: Callable[[Any], Any] | None = None, serialize_as_any: bool = False) dict[str, Any]#
- !!! abstract “Usage Documentation”
[model_dump](../concepts/serialization.md#python-mode)
Generate a dictionary representation of the model, optionally specifying which fields to include or exclude.
- Parameters:
mode (Literal['json', 'python'] | str) – The mode in which to_python should run. If mode is ‘json’, the output will only contain JSON serializable types. If mode is ‘python’, the output may contain non-JSON-serializable Python objects.
include (set[int] | set[str] | Mapping[int, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | Mapping[str, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | None) – A set of fields to include in the output.
exclude (set[int] | set[str] | Mapping[int, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | Mapping[str, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | None) – A set of fields to exclude from the output.
context (Any | None) – Additional context to pass to the serializer.
by_alias (bool | None) – Whether to use the field’s alias in the dictionary key if defined.
exclude_unset (bool) – Whether to exclude fields that have not been explicitly set.
exclude_defaults (bool) – Whether to exclude fields that are set to their default value.
exclude_none (bool) – Whether to exclude fields that have a value of None.
exclude_computed_fields (bool) – Whether to exclude computed fields. While this can be useful for round-tripping, it is usually recommended to use the dedicated round_trip parameter instead.
round_trip (bool) – If True, dumped values should be valid as input for non-idempotent types such as Json[T].
warnings (bool | Literal['none', 'warn', 'error']) – How to handle serialization errors. False/”none” ignores them, True/”warn” logs errors, “error” raises a [PydanticSerializationError][pydantic_core.PydanticSerializationError].
fallback (Callable[[Any], Any] | None) – A function to call when an unknown value is encountered. If not provided, a [PydanticSerializationError][pydantic_core.PydanticSerializationError] error is raised.
serialize_as_any (bool) – Whether to serialize fields with duck-typing serialization behavior.
- Returns:
A dictionary representation of the model.
- Return type:
- model_dump_json(*, indent: int | None = None, ensure_ascii: bool = False, include: set[int] | set[str] | Mapping[int, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | Mapping[str, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | None = None, exclude: set[int] | set[str] | Mapping[int, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | Mapping[str, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | None = None, context: Any | None = None, by_alias: bool | None = None, exclude_unset: bool = False, exclude_defaults: bool = False, exclude_none: bool = False, exclude_computed_fields: bool = False, round_trip: bool = False, warnings: bool | Literal['none', 'warn', 'error'] = True, fallback: Callable[[Any], Any] | None = None, serialize_as_any: bool = False) str#
- !!! abstract “Usage Documentation”
[model_dump_json](../concepts/serialization.md#json-mode)
Generates a JSON representation of the model using Pydantic’s to_json method.
- Parameters:
indent (int | None) – Indentation to use in the JSON output. If None is passed, the output will be compact.
ensure_ascii (bool) – If True, the output is guaranteed to have all incoming non-ASCII characters escaped. If False (the default), these characters will be output as-is.
include (set[int] | set[str] | Mapping[int, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | Mapping[str, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | None) – Field(s) to include in the JSON output.
exclude (set[int] | set[str] | Mapping[int, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | Mapping[str, set[int] | set[str] | Mapping[int, IncEx | bool] | Mapping[str, IncEx | bool] | bool] | None) – Field(s) to exclude from the JSON output.
context (Any | None) – Additional context to pass to the serializer.
by_alias (bool | None) – Whether to serialize using field aliases.
exclude_unset (bool) – Whether to exclude fields that have not been explicitly set.
exclude_defaults (bool) – Whether to exclude fields that are set to their default value.
exclude_none (bool) – Whether to exclude fields that have a value of None.
exclude_computed_fields (bool) – Whether to exclude computed fields. While this can be useful for round-tripping, it is usually recommended to use the dedicated round_trip parameter instead.
round_trip (bool) – If True, dumped values should be valid as input for non-idempotent types such as Json[T].
warnings (bool | Literal['none', 'warn', 'error']) – How to handle serialization errors. False/”none” ignores them, True/”warn” logs errors, “error” raises a [PydanticSerializationError][pydantic_core.PydanticSerializationError].
fallback (Callable[[Any], Any] | None) – A function to call when an unknown value is encountered. If not provided, a [PydanticSerializationError][pydantic_core.PydanticSerializationError] error is raised.
serialize_as_any (bool) – Whether to serialize fields with duck-typing serialization behavior.
- Returns:
A JSON string representation of the model.
- Return type:
- property model_extra: dict[str, Any] | None#
Get extra fields set during validation.
- Returns:
A dictionary of extra fields, or None if config.extra is not set to “allow”.
- model_fields = {}#
- property model_fields_set: set[str]#
Returns the set of fields that have been explicitly set on this model instance.
- Returns:
- A set of strings representing the fields that have been set,
i.e. that were not filled from defaults.
- classmethod model_json_schema(by_alias: bool = True, ref_template: str = '#/$defs/{model}', schema_generator: type[~pydantic.json_schema.GenerateJsonSchema] = <class 'pydantic.json_schema.GenerateJsonSchema'>, mode: ~typing.Literal['validation', 'serialization'] = 'validation', *, union_format: ~typing.Literal['any_of', 'primitive_type_array'] = 'any_of') dict[str, Any]#
Generates a JSON schema for a model class.
- Parameters:
by_alias (bool) – Whether to use attribute aliases or not.
ref_template (str) – The reference template.
union_format (Literal['any_of', 'primitive_type_array']) –
The format to use when combining schemas from unions together. Can be one of:
’any_of’: Use the [anyOf](https://json-schema.org/understanding-json-schema/reference/combining#anyOf)
keyword to combine schemas (the default). - ‘primitive_type_array’: Use the [type](https://json-schema.org/understanding-json-schema/reference/type) keyword as an array of strings, containing each type of the combination. If any of the schemas is not a primitive type (string, boolean, null, integer or number) or contains constraints/metadata, falls back to any_of.
schema_generator (type[GenerateJsonSchema]) – To override the logic used to generate the JSON schema, as a subclass of GenerateJsonSchema with your desired modifications
mode (Literal['validation', 'serialization']) – The mode in which to generate the schema.
- Returns:
The JSON schema for the given model class.
- Return type:
- classmethod model_parametrized_name(params: tuple[type[Any], ...]) str#
Compute the class name for parametrizations of generic classes.
This method can be overridden to achieve a custom naming scheme for generic BaseModels.
- Parameters:
params (tuple[type[Any], ...]) – Tuple of types of the class. Given a generic class Model with 2 type variables and a concrete model Model[str, int], the value (str, int) would be passed to params.
- Returns:
String representing the new class where params are passed to cls as type variables.
- Raises:
TypeError – Raised when trying to generate concrete names for non-generic models.
- Return type:
- model_post_init(_BaseOperation__context: Any) None#
Initialize logging and memory tracking after model construction.
Replaces the legacy
__init__body: creates the per-class logger and, when that logger is enabled for INFO level or higher, startstracemallocso per-operation memory usage can be logged.- Parameters:
__context – Pydantic post-init context (unused).
_BaseOperation__context (Any)
- Return type:
None
- classmethod model_rebuild(*, force: bool = False, raise_errors: bool = True, _parent_namespace_depth: int = 2, _types_namespace: MappingNamespace | None = None) bool | None#
Try to rebuild the pydantic-core schema for the model.
This may be necessary when one of the annotations is a ForwardRef which could not be resolved during the initial attempt to build the schema, and automatic rebuilding fails.
- Parameters:
force (bool) – Whether to force the rebuilding of the model schema, defaults to False.
raise_errors (bool) – Whether to raise errors, defaults to True.
_parent_namespace_depth (int) – The depth level of the parent namespace, defaults to 2.
_types_namespace (MappingNamespace | None) – The types namespace, defaults to None.
- Returns:
Returns None if the schema is already “complete” and rebuilding was not required. If rebuilding _was_ required, returns True if rebuilding was successful, otherwise False.
- Return type:
bool | None
- classmethod model_validate(obj: Any, *, strict: bool | None = None, extra: Literal['allow', 'ignore', 'forbid'] | None = None, from_attributes: bool | None = None, context: Any | None = None, by_alias: bool | None = None, by_name: bool | None = None) Self#
Validate a pydantic model instance.
- Parameters:
obj (Any) – The object to validate.
strict (bool | None) – Whether to enforce types strictly.
extra (Literal['allow', 'ignore', 'forbid'] | None) – Whether to ignore, allow, or forbid extra data during model validation. See the [extra configuration value][pydantic.ConfigDict.extra] for details.
from_attributes (bool | None) – Whether to extract data from object attributes.
context (Any | None) – Additional context to pass to the validator.
by_alias (bool | None) – Whether to use the field’s alias when validating against the provided input data.
by_name (bool | None) – Whether to use the field’s name when validating against the provided input data.
- Raises:
ValidationError – If the object could not be validated.
- Returns:
The validated model instance.
- Return type:
- classmethod model_validate_json(json_data: str | bytes | bytearray, *, strict: bool | None = None, extra: Literal['allow', 'ignore', 'forbid'] | None = None, context: Any | None = None, by_alias: bool | None = None, by_name: bool | None = None) Self#
- !!! abstract “Usage Documentation”
[JSON Parsing](../concepts/json.md#json-parsing)
Validate the given JSON data against the Pydantic model.
- Parameters:
json_data (str | bytes | bytearray) – The JSON data to validate.
strict (bool | None) – Whether to enforce types strictly.
extra (Literal['allow', 'ignore', 'forbid'] | None) – Whether to ignore, allow, or forbid extra data during model validation. See the [extra configuration value][pydantic.ConfigDict.extra] for details.
context (Any | None) – Extra variables to pass to the validator.
by_alias (bool | None) – Whether to use the field’s alias when validating against the provided input data.
by_name (bool | None) – Whether to use the field’s name when validating against the provided input data.
- Returns:
The validated Pydantic model.
- Raises:
ValidationError – If json_data is not a JSON string or the object could not be validated.
- Return type:
- classmethod model_validate_strings(obj: Any, *, strict: bool | None = None, extra: Literal['allow', 'ignore', 'forbid'] | None = None, context: Any | None = None, by_alias: bool | None = None, by_name: bool | None = None) Self#
Validate the given object with string data against the Pydantic model.
- Parameters:
obj (Any) – The object containing string data to validate.
strict (bool | None) – Whether to enforce types strictly.
extra (Literal['allow', 'ignore', 'forbid'] | None) – Whether to ignore, allow, or forbid extra data during model validation. See the [extra configuration value][pydantic.ConfigDict.extra] for details.
context (Any | None) – Extra variables to pass to the validator.
by_alias (bool | None) – Whether to use the field’s alias when validating against the provided input data.
by_name (bool | None) – Whether to use the field’s name when validating against the provided input data.
- Returns:
The validated Pydantic model.
- Return type:
- classmethod parse_file(path: str | Path, *, content_type: str | None = None, encoding: str = 'utf8', proto: DeprecatedParseProtocol | None = None, allow_pickle: bool = False) Self#
- classmethod parse_raw(b: str | bytes, *, content_type: str | None = None, encoding: str = 'utf8', proto: DeprecatedParseProtocol | None = None, allow_pickle: bool = False) Self#
- classmethod schema_json(*, by_alias: bool = True, ref_template: str = '#/$defs/{model}', **dumps_kwargs: Any) str#
- to_json(filepath: str | Path | None = None) str | None#
Serialize this operation to JSON.
Captures the operation as a
{"class", "params"}envelope:paramsismodel_dump(mode="json")(every declared field, including nested operations and raw arrays;PrivateAttrstate such as loggers and timing is excluded automatically), andclassrecords the concrete class name sofrom_json()can rebuild the right subclass. This mirrorsImagePipeline.to_json().- Parameters:
filepath (str | Path | None) – Optional path to write the JSON to. When None, the JSON string is returned instead. Accepts a
strorPath.- Returns:
The JSON string when
filepathis None, otherwise None.- Return type:
str | None
Example
>>> import tempfile >>> from pathlib import Path >>> from phenotypic.detect import OtsuDetector >>> from phenotypic.sdk_ import CONFIG_SUFFIX_OPERATION, ensure_typed_json_suffix >>> with tempfile.TemporaryDirectory() as d: ... p = Path(d) / "op.json" ... saved = ensure_typed_json_suffix(p, CONFIG_SUFFIX_OPERATION) ... OtsuDetector(ignore_zeros=True).to_json(p) ... loaded = OtsuDetector.from_json(saved) >>> loaded.ignore_zeros True
- widget(image: Image | None = None, show: bool = False) Widget#
Return (and optionally display) the root widget.
- Parameters:
image (Image | None) – Optional image to visualize. If provided, visualization controls will be added to the widget.
show (bool) – Whether to display the widget immediately. Defaults to False.
- Returns:
The root widget.
- Return type:
ipywidgets.Widget
- Raises:
ImportError – If ipywidgets or IPython are not installed.