Scoria vs Pumice Vesicularity Split Checker

Screen independent density/composition/vesicle context using caller scoria/pumice evidence rules, vesicularity alone not sufficient identity. Positive caller evidence rules only; missing evidence retains compatible possibilities, overlaps not forced to one identity. Caller independently establishes units, regime, calibration and applicability; this does not establish design-code compliance, authenticity, operational safety, treatment efficacy or a validated forecast.

Description

Scoria and pumice descriptions require more than a porosity number.

Scoria and pumice descriptions require more than a porosity number.1

This tool screens your density, composition, and vesicle evidence against explicit class requirements, keeping overlapping or incomplete possibilities visible.

When to use Scoria vs Pumice Vesicularity Split Checker

Use this tool when you need to review whether explicit class requirements are contradicted or fully witnessed. Prepare matched observations and independently established site, specimen, units, datum, and calibration context.

How to use Scoria vs Pumice Vesicularity Split Checker and understand its results

  1. Prepare matched observations and independently established site, specimen, units, datum, and calibration context.
  2. Enter callerVesicularRockClassIds, callerVesicularRockRequiredEvidence, observedVesicularRockEvidence, knownVesicularRockEvidenceFlags, following the field table and rules below, then run the tool.
  3. Read contradictionFreeCallerClasses, fullyWitnessedCallerClasses. Use the output meanings below to interpret units, signs, flags, and any nested result fields.
  4. Correct reported input issues and run again. For a successful result, check the stated evidence coverage and assumptions before using it in your review.
Input fieldMeaningValue typeRequirement
callerVesicularRockClassIdsCaller vesicular rock class idslist of stringRequired
callerVesicularRockRequiredEvidenceCaller vesicular rock required evidencenumeric matrixRequired
observedVesicularRockEvidenceObserved vesicular rock evidencelist of numberRequired
knownVesicularRockEvidenceFlagsKnown vesicular rock evidence flagslist of numberRequired

Provide unique nonblank class IDs, a nonempty rectangular binary requirements matrix with one row per class and one column per evidence item, aligned binary observed and known flags, and at least one required positive witness per class. A required known-zero observation contradicts a class. Unknown requirements leave it compatible but not fully witnessed. Return all compatible and all fully witnessed class IDs in supplied order; a zero requirement means that column is ignored, not a required negative fact.

compatible_c=∀j(required_cj=0 or known_j=0 or observed_j=1); witnessed_c=∀j(required_cj=0 or (known_j=1 and observed_j=1))

Symbols follow the input and output meanings and the calculation rules above.

Output fieldMeaningValue type
contradictionFreeCallerClassesContradiction free caller classeslist of string
fullyWitnessedCallerClassesFully witnessed caller classeslist of string
json
{
  "input": {
    "callerVesicularRockClassIds": [
      "class-a",
      "class-b"
    ],
    "callerVesicularRockRequiredEvidence": [
      [
        1,
        0
      ],
      [
        0,
        1
      ]
    ],
    "observedVesicularRockEvidence": [
      1,
      0
    ],
    "knownVesicularRockEvidenceFlags": [
      1,
      0
    ]
  },
  "output": {
    "contradictionFreeCallerClasses": [
      "class-a",
      "class-b"
    ],
    "fullyWitnessedCallerClasses": [
      "class-a"
    ]
  }
}

Limitations and assumptions

These are user-defined positive-evidence screens. Multiple classes may remain, no class may qualify, and missing evidence must be resolved independently. Fully witnessed requirements do not establish that the supplied classification rules are legally or scientifically complete.

Missing required fields, unknown fields, wrong types, and violated calculation rules are input issues. Numeric values must be finite; nonfinite results are rejected. Evidence arrays must be dense, with no missing cells. Numeric observation lists allow at most 10,000 entries, subject to any smaller bounds stated above. String lists allow at most 128 strings of at most 128 characters. Numeric matrices are limited to 128 rows and 128 entries per row, with rectangularity required where stated.

Alternative or Complementary methods

For a related review, use Vesicularity Porosity Calculation Tool: Vesicles are cavities within volcanic rock; only some may connect to an open pore network. Whole specimen, total vesicle, and connected vesicle volumes allow total vesicularity and connected porosity to be reported separately. For a complementary step, use Caldera vs Summit Crater Classifier: A caldera or summit-crater interpretation depends on the origin of a depression, such as collapse or excavation. This checker reviews your mapped origin evidence instead of assigning an identity from diameter alone.

References

  1. Scoria vs Pumice Vesicularity Split Checker — tool.io

Similar or alternative tools

  • Vesicularity Porosity Calculation Tool

    Vesicles are cavities within volcanic rock; only some may connect to an open pore network. Whole specimen, total vesicle, and connected vesicle volumes allow total vesicularity and connected porosity to be reported separately.

  • Caldera vs Summit Crater Classifier

    A caldera or summit-crater interpretation depends on the origin of a depression, such as collapse or excavation. This checker reviews your mapped origin evidence instead of assigning an identity from diameter alone.

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies