Ansel 0.0
A darktable fork - bloat + design vision
Loading...
Searching...
No Matches
pixel Directory Reference
Directory dependency graph for pixel:

Files

 
bilateral.c
 
bilateral.h
 
bilateralcl.c
 
bilateralcl.h
 
box_filters.c
 
box_filters.h
 
bspline.h
 
chromatic_adaptation.h
 
colorequal_shared.c
 
colorequal_shared.h
 
distance_transform.h
 
dwt.c
 
dwt.h
 
eaw.c
 
eaw.h
 
eigf.h
 
fast_guided_filter.h
 
format.c
 
format.h
 
gaussian.c
 
gaussian.h
 
guided_filter.c
 
guided_filter.h
 
heal.c
 
heal.h
 
illuminants.h
 
interpolation.c
 
interpolation.h
 
locallaplacian.c
 
locallaplacian.h
 
locallaplaciancl.c
 
locallaplaciancl.h
 
luminance_mask.h
 
lut3d.c
 
lut3d.h
 
nlmeans_core.c
 
nlmeans_core.h
 
rgb_norms.h
 
tea.h

Detailed Description

`src/pixel/` — pixel algorithms

Operations on buffers of pixels that are not tied to a specific IOP module: shared filters, decompositions and colour primitives that several modules build on.

Layer 2 — above common/ and math/, below control/ and everything visual.

Rules

No module state, no pipeline knowledge. Code here takes buffers and parameters and returns buffers. It does not know what a dt_iop_module_t is, does not read history, and does not decide when it runs — that is develop/'s job.

No GUI, no database, no files. A pixel algorithm that needs to report progress or ask a question is in the wrong place, or needs its caller to do the asking.

SIMD and alignment come from system/. Use system/simd.h for the aligned pixel type and load/store helpers rather than hand-rolling intrinsics, and system/openmp.h for the pragma shorthands.

Related

  • src/math/ — arithmetic and solvers with no notion of a pixel.
  • src/iop/ — the modules themselves, with parameters, GUI and pipeline integration.