Muse Invocation Opening Locator

Locate independently annotated Muse invocation lines within an explicit half-open opening window, zero-based indices, not lexical inference from a translated muse token.

Description

A Muse invocation must be identified within a text and edition before its position is counted.

A Muse invocation must be identified within a text and edition before its position is counted.1

This locator partitions supplied line indices rather than recognizing invocations from language. Use Muse Invocation Opening Locator to evaluate the supplied inputs under the model explained below.

When to use Muse Invocation Opening Locator

Use Muse Invocation Opening Locator to evaluate the supplied inputs under the model explained below. Choose the applicable era, source or grammatical convention and independently establish the annotations or numerical assumptions.

How to use Muse Invocation Opening Locator and understand its results

  1. Choose the applicable era, source or grammatical convention and independently establish the annotations or numerical assumptions.
  2. Enter Independently annotated invocation line indices, Caller opening end exclusive using the field table and validation rules below, then run the tool.
  3. Read Invocations Within Opening, Later Invocation Indices in the Result object; interpret the units, signs, ordering and unknown-value placeholders described below.
  4. Correct reported input errors and rerun. Apply successful results according to their specific meanings and check the assumptions before using them in a decision.
Input fieldMeaningValue typeRequirement
independentlyAnnotatedInvocationLineIndicesIndependently annotated invocation line indicesarray of numberRequired; constraints below
callerOpeningEndExclusiveCaller opening end exclusivenumberRequired; constraints below

Enter distinct independently annotated zero-based invocation line indices from 0 to 100000 and an opening-end-exclusive integer from 1 to 100000. Return indices below the opening bound and indices at or above it in original input order. The index array may be empty; it need not be sorted. No corpus, line count or invocation detection is supplied.

opening = indices<endExclusive; later = indices≥endExclusive

Use the field order, units and branch conditions described above.

Output fieldMeaningValue type
resultObject containing the named result fields below.object
result.invocationsWithinOpeningInvocations Within Openingarray of number
result.laterInvocationIndicesLater Invocation Indicesarray of number
json
{
  "input": {
    "independentlyAnnotatedInvocationLineIndices": [
      0,
      9
    ],
    "callerOpeningEndExclusive": 5
  },
  "output": {
    "result": {
      "invocationsWithinOpening": [
        0
      ],
      "laterInvocationIndices": [
        9
      ]
    }
  }
}

Limitations and assumptions

This locator partitions supplied line indices rather than recognizing invocations from language. Apply the exact scope and assumptions explained above.

All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are explained above; extremely large inputs or outputs can also be rejected. Input errors differ from successful false results, empty match lists and unknown-evidence placeholders.

Alternative or Complementary methods

Use in Medias Res Opening Classifier for a related task: In medias res describes an opening's relationship to an already developing action.

Use Menippean Satura Mixed Genre Classifier for a related task: Menippean classification depends on independently identified literary features.

References

  1. Muse Invocation Opening Locator — tool.io

Similar or alternative tools

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