Skip to main content

CRAMM

PyPI Python License: MIT DOI Platform

General-purpose hyperspectral mineral identification toolkit — built on the USGS MICA (Material Identification and Characterization Algorithm) decision-rule system. The classification core is sensor-agnostic: it works on any VNIR–SWIR reflectance cube given its band configuration (center wavelengths, FWHM, valid-band mask), because the bundled splib06b reference spectra are resampled to the sensor's bands at runtime. EMIT L2A is simply the built-in data reader — one supported input type, not the defining one.

CRAMM extends MICA in three ways:

  1. An enhanced rule schema. CRAMM adds an optional secondary-feature depth-ratio constraint (max_depth_ratio_feat1_over_feat0) that rejects pixels whose secondary absorption is too deep relative to the primary 2.2 µm feature — suppressing white-mica false positives that pass the original five-layer MICA filtering. Nine bundled rules (muscovite, illite, kaolinite–muscovite mixtures) carry the new constraint; any custom rule can opt in. See Enhancements over USGS MICA.
  2. Wavelength-arbitrated muscovite subtyping. MICA labels a pixel "muscovite_lowAl / medAl / medhighAl / Fe-rich" by best fit alone; CRAMM then re-arbitrates that attribution with the pixel's fitted 2.2 µm absorption center against per-rule calibrated wavelength windows (absorption_center_range) — the spectroscopically meaningful axis along which these four subtypes are actually defined. See Enhancements over USGS MICA → Wavelength-based muscovite attribution.
  3. From mineral detection to mineral composition. Beyond labeling muscovite pixels, CRAMM fits the per-pixel 2.2 µm absorption-center wavelength (mus_center) — a quantitative composition proxy whose thermodynamic basis (Tschermak substitution vs. wv2200 on a GEMS/MINES23.1 reaction-path phase diagram) turns each fitted pixel into a calibrated constraint on muscovite chemistry and on its position in the T–log(aK⁺/aH⁺) plane. See Application: reading muscovite composition from mus_center.

Everything is pure Python and GUI-free. Cross-platform: Windows / Linux / macOS · Python 3.9 – 3.13


Highlights

  • Enhanced MICA pipeline — continuum removal → closed-form 2×2 least squares → fit (r²) & absorption depth → five-layer constraint filtering + the CRAMM depth-ratio constraint, driven by a JSON rule library (77 rules covering clay, sulfate, carbonate, mica, chlorite, amphibole, iron oxide, snow/ice and their mixtures).
  • Quantitative muscovite mapping — per-pixel 2.2 µm absorption-center wavelength as a dedicated thematic map and float array; the same center also re-arbitrates the lowAl / medAl / medhighAl / Fe-rich attribution against calibrated wavelength windows, with a phase-diagram interpretation framework.
  • Quantitative chlorite mapping — per-pixel 2250 nm absorption-center wavelength (chl_center) for pixels won by the four pure-chlorite rules, as a fourth thematic map and float array; a continuous Fe-content proxy anchored by the chl13 calibration (LOO 1.0 nm). The same center also re-arbitrates the lowFe / clinochlore / Fe-rich / thuringite attribution against deliberately overlapping tolerance windows — intermediate compositions keep their best-fit class, only clear outliers flip.
  • Quantitative carbonate mapping — per-pixel 2330 nm absorption-center wavelength (cal_center) for pixels won by the five carbonate rules, as a fifth thematic map and float array; band position tracks the seven-anchor C–O sequence (magnesite 2311 nm → rhodochrosite ~2369 nm), making species the rule library cannot tell apart (aragonite, magnesite — silently classified as dolomite) visible in the continuous layer. Its arbitration windows are duplicated across each abundant+plain pair, so the carbonate re-attribution is declarative and never flips — the value is the continuous center itself.
  • Whole-scene and single-spectrum modes — batch-classify an entire scene to GeoTIFF, or identify one spectrum (GUI point-click, field spectrometer) with Top-N ranking and a PDF diagnostic report.
  • Sensor-agnostic core — everything downstream of data loading consumes a generic (spectrum, wavelengths, FWHM, valid bands) contract. The bundled reader covers EMIT L2A NetCDF; any other sensor (airborne or spaceborne) plugs in through the same seven-tuple — no rule or code changes needed.
  • Fast — reference-side constants are precompiled once per band configuration (two-level cache; ~16× speedup on repeated single-spectrum calls), and scene classification parallelizes across rules with worker processes.
  • Bit-exact discipline — serial and parallel paths produce identical bytes; every change is guarded by a dual-path golden regression suite.
  • Self-contained — the rule library (rf.json), the USGS splib06b spectral library, and the mineral color table are bundled inside the wheel.

How it works

Hyperspectral reflectance cube (any VNIR–SWIR sensor)
      │  built-in: load_emit (EMIT L2A NetCDF, bad-band removal)
      │  or your own loader → (spectrum, wl, w, bp, chanels)
      ▼
Reference resampling ── splib06b records ──► sensor wavelengths/FWHM
      │                                        (Gaussian kernel, cached)
      ▼
Per-rule evaluation (77 rules, parallel across rules)
      │  diagnostic features: continuum removal → 2×2 LSQ → r² / depth
      │  not-absorption / not-related features: exclusion filters
      │  continuum & depth-ratio constraints
      ▼
Best-match selection (argmax weighted fit)  +  muscovite 2.2 µm center fit
      │                                   +  chlorite 2250 nm center fit
      │                                   +  carbonate 2330 nm center fit
      ▼
Wavelength-arbitrated subtyping (muscovite / chlorite / carbonate families)
      │  *_center vs. per-rule absorption_center_range windows
      ▼
Mineral map · color-enhanced map · muscovite map · chlorite map · carbonate map
(+ raw float arrays: mus_center / chl_center / cal_center / fd)

Installation

pip install cramm            # core features (PyPI wheels on all three platforms)
pip install cramm[tiff]      # + GeoTIFF output (GDAL; PyPI wheels are Windows-only)
pip install cramm[pdf]       # + single-spectrum feature PDF diagnostics
pip install cramm[all]       # everything

GDAL on Linux/macOS: PyPI ships GDAL wheels for Windows only. Install a system libgdal first (conda-forge recommended), then install without deps:

conda install -c conda-forge gdal
pip install cramm --no-deps        # or: pip install cramm[pdf]

Without GDAL, only write_tiff (GeoTIFF output) is unavailable — all classification and analysis functions work (lazy import).

From source (sdist / checkout):

pip install .            # add [all] for the optional extras

Quick start

Command line

The CLI uses the built-in EMIT L2A reader; for other sensors, use the Python API (below) with your own loader.

cramm -i EMIT_L2A_RFL_001_xxx.nc -o output [-n scene] [-w 4] [--raw]
Flag Default Meaning
-i, --input (required) Path to the EMIT L2A NetCDF file
-o, --output . Output directory
-n, --name input filename Output filename prefix
-w, --workers min(cpu, 8) Parallel worker processes (1 = serial)
--raw off Also save mus_center + chl_center + fd float arrays as .npz

Output files (written to <output>/<name>*):

File Content
<name>_mapping_orth.tiff Mineral map (orthorectified, rule-library colors)
<name>_color_enhanced_orth.tiff Color-enhanced mineral map
<name>_mus_orth.tiff Muscovite 2.2 µm absorption-center thematic map
<name>_chl_orth.tiff Chlorite 2250 nm absorption-center thematic map
<name>_cal_orth.tiff Carbonate 2330 nm absorption-center thematic map
<name>_raw.npz (only with --raw) mus_center + chl_center + cal_center [μm] + fd (fit×depth), float [r, c]

Python API

from cramm import MicaEngine

engine = MicaEngine()                                    # all resources bundled
spectrum, lon, lat, w, bp, wl, chanels = engine.load_emit("EMIT_xxx.nc")

# --- whole scene → GeoTIFF -------------------------------------------------
orth, color, mus, chl, cal = engine.spectrum_analysis(spectrum, wl, w, bp, chanels,
                                                      n_workers=4)
engine.write_tiff("output/scene", lon, lat, orth, color, mus, chl, cal)

# --- single spectrum (one pixel, field spectrometer, ...) ------------------
pixel = spectrum[100, 200, :]                            # full-band [285] or selected [len(chanels)]
results = engine.classify_spectrum(pixel, wl, w, bp, chanels,
                                   top_n=5, pdf_path="diag.pdf")
for r in results:
    print(f"{r['name']:50s} fit={r['fit']:.4f}  fd={r['fd']:.4f}")

Other sensors (non-EMIT data)

load_emit is only a convenience reader. For any other sensor, load the cube yourself and pass the same band-configuration contract — references are resampled to your wavelengths/FWHM automatically:

from cramm import MicaEngine
import numpy as np

engine = MicaEngine()
spectrum = my_loader("scene.dat")          # [rows, cols, bands] reflectance
w  = np.array([...])                       # band center wavelengths [µm]
bp = np.array([...])                       # band FWHM [µm]
chanels = np.arange(len(w))                # valid bands (drop bad-band indices)
wl = w[chanels]

orth, color, mus, chl = engine.spectrum_analysis(spectrum, wl, w, bp, chanels,
                                                 n_workers=4)

Only the map rendering (write_tiff) needs geolocation (lon/lat grids); classification itself is purely spectral and location-free.

classify_spectrum returns a list of {"name", "fit", "fd"} dicts sorted by descending fit (empty list when nothing passes the filters). With pdf_path= it also writes a multi-page PDF: one page per Top-N mineral with continuum-removed feature overlays and constraint annotations (requires the [pdf] extra).

Each PDF page dissects one candidate rule — every diagnostic / not-absorption / not-relative feature with its continuum endpoints, the reference continuum-removed profile (squares) against the input (circles), and the full constraint audit (k0/k1, r², raw depth, weights, thresholds):

Single-spectrum diagnostic PDF: per-rule feature dissection

More scenarios — float (raw=True) output, custom rule libraries, the invalidate_caches() contract, component-level calls — in example_usage.py: python example_usage.py pixel.

API overview

MicaEngine method Purpose
load_emit(path) (EMIT-specific convenience reader) Read EMIT L2A NetCDF → (spectrum, lon, lat, w, bp, wl, chanels); float32 cube, bad bands removed, fill values zeroed. Not needed for other sensors — supply the same tuple yourself
spectrum_analysis(spectrum, wl, w, bp, chanels, ...) Classify a whole scene → 4 uint8 RGB images; raw=True adds mus_center + chl_center + fd float arrays. Supports progress_callback, log_callback, cancel_flag, n_workers
classify_spectrum(spectrum, wl, w, bp, chanels, top_n=10, pdf_path=None) Identify one spectrum → Top-N [{"name", "fit", "fd"}]
write_tiff(prefix, lon, lat, orth, color, mus, chl=None) Orthorectify (pyresample) and write the GeoTIFFs; chl is optional (omit for legacy 3-file output); requires GDAL
get_resample(w, bp) All reference spectra resampled to the sensor bands {record_id: spectrum} (cached)
invalidate_caches() Required after mutating engine.rf in place — see below

Custom rule libraries

engine = MicaEngine(rf_path="my_rules.json")          # at construction
# — or mutate in place —
engine.rf["my_mineral"] = {...}
engine.invalidate_caches()                            # mandatory!

The compiled-rule cache is keyed on band configuration only, not on rule content. If you modify engine.rf after any classification call, you must call invalidate_caches() (or build a new engine) — otherwise results silently use the old reference-side constants.

Enhancements over USGS MICA

CRAMM extends the original USGS MICA decision rules with an optional per-rule secondary-feature depth-ratio constraint, max_depth_ratio_feat1_over_feat0:

After the standard MICA filtering, a rule carrying this key rejects any pixel where raw_depth(feat1) / raw_depth(feat0) ≥ threshold, using the unweighted feature depths (1 − min(continuum-removed)) × k0. Pixels with an invalid primary feature (NaN depth) are conservatively kept.

For white micas the primary 2.2 µm Al-OH absorption (feat0) must dominate the secondary ~2.35 µm feature (feat1); a secondary absorption that is too deep relative to the primary indicates look-alike minerals rather than muscovite / illite. Nine bundled rules use this constraint:

Threshold Rules
0.6 muscovite_lowAl, muscovite_medAl, muscovite_medhighAl, muscovite_Fe-rich, illite_imt1, illite_gds4
0.4 kaolinite.5+muscoviteMedAl.5, kaolinite.5+muscoviteMedhighAl.5, kaolinite+muscovite_mix_intimate

The constraint is part of the rule schema — custom rule libraries can set "max_depth_ratio_feat1_over_feat0": <float> on any rule with ≥2 diagnostic features; omitting the key disables it (original MICA behavior).

Wavelength-based absorption-center attribution

CRAMM also adds an optional per-feature absorption-center window, absorption_center_range on a rule's first diagnostic feature. After the best-match selection, pixels attributed to a rule carrying this field are re-arbitrated by their fitted absorption center (mus_center at 2.2 µm for the white-mica family, chl_center at 2250 nm for the chlorite family, cal_center at 2330 nm for the carbonate family):

If the center falls inside exactly one rule's [lo, hi) window, differs from the current match, and that rule itself accepted the pixel, the pixel is reassigned to the matching rule (fit/depth/index follow, and the center is refitted once with the new rule's endpoints). An invalid center, a center outside every window, or a center inside several overlapping windows keeps the original match (conservative).

The four bundled pure-muscovite rules carry calibrated windows (anchored on each reference spectrum's measured wv2200): medhighAl [2.195, 2.200), medAl [2.200, 2.206), lowAl [2.206, 2.210), Fe-rich [2.210, 2.220) — the four windows tile the 2.195–2.220 µm range without overlap, so every valid center arbitrates to exactly one subtype. The four bundled pure-chlorite rules instead carry overlapping windows — lowFe [2.245, 2.248), clinochlore [2.247, 2.252), Fe-rich [2.251, 2.25549), thuringite [2.255, 2.266) — whose overlaps (1 nm between the first three, 0.49 nm at the Fe-rich/thuringite seam) act as tolerance zones: an intermediate-composition pixel lands in two windows at once, is ambiguous by the rule above, and keeps its best-fit class (see Application: reading chlorite Fe content from chl_center). The four calcite/dolomite rules carry duplicate windows — calcite_abundant and calcite share [2.334, 2.350); dolomite_abundant and dolomite share [2.308, 2.328) — pushing the tolerance scheme to its extreme: every in-window center hits two identical ranges, is ambiguous, and keeps its match. The carbonate arbitration is therefore declarative and never flips (pinned by a dedicated unit test); the product line's value is the continuous cal_center layer itself (see Application: reading carbonate species from cal_center). This is a scene-classification feature; single-spectrum Top-N ranking is unaffected. Each arbitration call locks its group to one mineral family (MUSCOVITE_MINERALS / CHLORITE_MINERALS / CARBONATE_MINERALS ∩ windowed rules), so cross-family flips are structurally impossible (pinned by a dedicated unit test). Custom rule libraries opt in per family: append the new rule to the corresponding family list AND give it the field; rules without it are never reassigned.

Seven white-mica-group and chlorite rules carry parsed structural formulas of their reference spectra as bundled metadata: reference.structural_formula with structural_formula_tier (A = wet-chemistry Fe³⁺/Fe²⁺ split, B = total-Fe convention). White micas (O=11 anhydrous basis, from the 14-sample white-mica composition–band-position calibration set): muscovite_medhighAl (GDS113), muscovite_Fe-rich (GDS116), illite_gds4 (GDS4) and illite_imt1 (IMt-1) — of the four arbitration windows above, medhighAl and Fe-rich are thereby anchored to measured chemistry; medAl (CU91-250A) and lowAl (CU93-1) have no published full analysis. Chlorites (O₁₀(OH)₈ basis, from the chl13 calibration set): chlorite_lowFe (SMR-13), clinochlore (GDS158) and clinochlore_Fe (SC-CCa-1; chemistry from the Bartel XRF of the same CMS CCa-1 specimen) — the full lowFe→Fe-rich gradient is chemistry-anchored. The metadata is informational only and never enters the classification math.

Application: reading muscovite composition from mus_center

The muscovite thematic map's per-pixel mus_center (2.2 µm Al-OH absorption position) is a quantitative proxy for muscovite chemistry. The phase diagram below — a GEMS/MINES23.1 titration reaction-path model of the K₂O–Al₂O₃–SiO₂–H₂O–HCl–FeO–MgO system — overlays the Tschermak substitution degree X_Ts = X(Fe-Celadonite)+X(Celadonite) in the muscovite stability field with the corresponding wv2200 position (USGS conversion chain: X_Ts → Al₂O₃ wt% → λ = −3.1·Al₂O₃ + 2308):

Tschermak substitution degree vs. wv2200 in the muscovite field

X_Ts rises from ~0 on the high-T / low-K⁺ side to 0.35+ on the low-T / high-K⁺ side. The wv2200 contours (magenta, 2190→2215 nm) are derived by chaining the empirical wavelength–composition calibration through the modelled X_Ts field, so they track the X_Ts contours (dark blue) by construction. Each mus_center value fitted from an image pixel therefore selects one isopleth on this diagram: muscovite composition (X_Ts) is read directly, while in the T–log(aK⁺/aH⁺) plane the value defines a one-dimensional constraint locus, not a unique point. Pinning down both formation temperature and fluid K⁺/H⁺ requires a second independent constraint — e.g. the chl_center of a coexisting chlorite read on the companion diagram, under a same-pressure, same-fluid equilibrium assumption. The diagram is an interpretive framework for the product, not a ground-validated inversion.

Application: reading chlorite Fe content from chl_center

The chlorite thematic map's per-pixel chl_center (2250 nm Fe–OH absorption position) is a continuous composition proxy: across the chl13 calibration set (13 samples spanning xFe 0.014–0.553) the closed-form model pos2250 = 2218.8·xAl + 2279.6·xFe + 2249.7·xMg reproduces band positions with LOO-RMSE 1.0 nm — at the repeat-measurement noise floor — and the calibration is immune to the Fe²⁺/Fe³⁺ reporting convention (closure normalization cancels it exactly). Unlike the muscovite subtypes — whose windows tile their range without overlap — the four chlorite rules carry deliberately overlapping tolerance windows: lowFe [2.245, 2.248), clinochlore [2.247, 2.252), Fe-rich [2.251, 2.25549), thuringite [2.255, 2.266) µm. A chl_center landing in an overlap hits two windows, is declared ambiguous, and keeps its argmax attribution (the four references are points on a composition continuum, so intermediate compositions must not be forced into a class); only a center falling exclusively inside another rule's window flips the attribution, with the center refitted once against the target rule's endpoints. Practical limits from the calibration: quantitative inversion needs chlorite ≳50 % of the pixel and a comparable sample preparation; the 2350 nm Mg–OH band (cross-instrument anchor, bias ≈0.2 nm) is reserved for pure-mineral checks.

Application: reading carbonate species from cal_center

The carbonate thematic map's per-pixel cal_center (2330 nm C–O absorption position) discriminates carbonate species along the seven-anchor band sequence: magnesite 2311 nm < aragonite 2315 nm < Fe-dolomite 2319 nm < dolomite 2321 nm < siderite ~2327 nm < calcite 2339 nm < rhodochrosite ~2369 nm (Fe²⁺ substitution blue-shifts the band by ~2 nm; Mn²⁺ red-shifts it). The bundled rule library covers only three of these anchors — calcite (WS272), dolomite (HS102.3B) and a manganoan siderite (HS271, inherited from USGS MICA as carbonate_Fe_bearing) — so aragonite and magnesite pixels are silently classified as dolomite by best fit. cal_center makes them visible: a "dolomite" pixel whose center sits at 2311–2316 nm is a magnesite/aragonite suspect, and the continuous layer likewise exposes Fe-bearing dolomite (≤2319 nm) inside the dolomite class. The calcite and dolomite abundant+plain pairs carry duplicate arbitration windows ([2.334, 2.350) and [2.308, 2.328) respectively), so the wavelength arbitration never reassigns a carbonate pixel — every in-window center is ambiguous between the twins — and the map can be read as a pure measurement layer: bin edges at 5 nm steps over [2.308, 2.358) µm, shorter wavelength = earlier anchor in the sequence above.

Performance notes

  • Precompiled rules: continuum endpoints, band indices, the reference-side normal-equation constant B and depth factors are computed once per (wavelengths, FWHM, valid-band) configuration and reused across all pixels and calls.
  • Parallelism: scene classification fans out across the 77 rules with multiprocessing (spawn context). The per-pixel normal-equation solve (k0/k1) is a BLAS-free np.einsum, so results are independent of the pixel-row count and the BLAS thread pool — the parallel path is bit-identical to the serial one structurally, not by BLAS-configuration luck (worker BLAS pinning to a single thread is retained as defense in depth).
  • Typical runtime: a full scene (e.g. an EMIT granule, ≈1280×1242 pixels) classifies in about a minute with a few workers on a desktop; a warm single-spectrum call is ≈10 ms.

Testing

python tests/test_core.py              # 21 API contract / behavior tests
                                       # (integration section auto-skips without the test scene)
python tests/test_custom_rules.py      # custom rule-library verification (7 scenarios:
                                       #   rf_path / constraint & window edits / new rules / cache contract)
python tests/test_parallel_isolation.py # shared-state isolation (6 checks: worker/thread
                                       #   isolation, env restore, temp-file cleanup)

# The suites below need the EMIT test scene in the working directory
# (file name defined in each script's NC constant):
python tests/check_rows_logic.py       # rows alive-pixel semantics (16 checks)
python tests/check_alive_restriction.py # end-to-end A/B: rows-on vs forced-full computation,
                                       #   77 rules + classify + compiled path, bit-level diff
python tests/test_single_spectrum.py   # single-spectrum identification (7 tests:
                                       #   self-ID / noise robustness / determinism / ...)
python tests/check_compiled_path.py    # compiled vs direct path, 302 pixels × 77 rules, bit-level diff
python tests/test_parallel.py 4        # full-scene golden regression (parallel)
python tests/test_parallel.py 1        # full-scene golden regression (serial)

The golden baseline is platform-bound. tests/golden_arrays.npz encodes this machine's BLAS results; ulp-level differences across BLAS builds are expected. On a new platform — or after an intentional classification-semantics change — regenerate the baseline locally with python tests/rebaseline_golden.py (runs the full scene, audits every differing pixel against the intended change, then atomically rewrites the golden) before relying on test_parallel.py.

Troubleshooting

  • netCDF4 fails to open a path containing non-ASCII characters on Windows — a limitation of the netCDF C library, not of CRAMM. cd into the data directory and use a relative path instead.
  • ImportError: gdal — you called write_tiff without GDAL installed; see Installation. Classification itself never imports GDAL.

Package layout

cramm/
  __init__.py       # exports MicaEngine / ProcessResult
  mica_engine.py    # facade: resource loading + component wiring + CLI main()
  emit_reader.py    # EMIT L2A NetCDF reader + bad-band removal (float32 contract)
  classifier.py     # MICA core: resampling / compiled rules / serial & parallel classification
  renderer.py       # rendering: three maps / GeoTIFF / single-spectrum PDF diagnostics
  data/             # rf.json + splib06b + color_table.json
tests/              # bit-exact verification suite + API contract tests
example_usage.py    # five usage-scenario examples

Requirements

  • Python 3.9 – 3.13
  • Runtime: numpy, pandas, netCDF4, pyproj, pyresample, threadpoolctl
  • Optional: gdal (GeoTIFF), matplotlib (PDF diagnostics)

Acknowledgments

The decision rules implement the USGS MICA system (Kokaly et al., russet-era rule set); reference spectra come from the USGS splib06b spectral library (Clark et al., 2007). The bundled test scene uses EMIT L2A products, courtesy of NASA/JPL.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

cramm-1.1.0.tar.gz (21.2 MB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

cramm-1.1.0-py3-none-any.whl (14.9 MB view details)

Uploaded Python 3

File details

Details for the file cramm-1.1.0.tar.gz.

File metadata

  • Download URL: cramm-1.1.0.tar.gz
  • Upload date:
  • Size: 21.2 MB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.13.9

File hashes

Hashes for cramm-1.1.0.tar.gz
Algorithm Hash digest
SHA256 106f6a9b7148cd685bc66ca229527d150fd368c53bc5d0e911f0c886c9451b93
MD5 962dfeb613d66fb1d99940270ec781c9
BLAKE2b-256 767a8d03f700382e35f0fb112e6690ec1fc8a810f4a70509db6be5c63088e6e7

See more details on using hashes here.

File details

Details for the file cramm-1.1.0-py3-none-any.whl.

File metadata

  • Download URL: cramm-1.1.0-py3-none-any.whl
  • Upload date:
  • Size: 14.9 MB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.13.9

File hashes

Hashes for cramm-1.1.0-py3-none-any.whl
Algorithm Hash digest
SHA256 5fb58ef01174473134f53cc2e402e6654b3bd2ecad7b8edf8af51add224d2add
MD5 112bf0e37369b43a5f7fc78440824bbd
BLAKE2b-256 dcc910d72b54e775be95a0418be21432ca76a8f8506acc11aa35574a11449f69

See more details on using hashes here.

Release history Release notifications | RSS feed

This release

1.1.0 This release

2 files

1.0.3

2 files

1.0.2

2 files

1.0.1

2 files

1.0.0

2 files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page