Succeeds by series index#

This page is generated from the code and must not be edited by hand.

One file is put after another in a series when both are repeats of one condition and the second carries the next number, but repeats whose names differ in more than one part, whose numbers tie or do not count, or whose clocks run against the numbers are not put in order, and the rule is off until a project turns it on.

succeeds_by_series_index version 2

Ships switched off. The engine does not run this rule until a project turns it on.

To turn it on, save a file in the project’s rulebook folder, named for the next free number (for example PROJECT/rulebook/project-0001.yaml), holding these lines, then run ingence infer:

project_revision: 1
changes:
  - enable: succeeds_by_series_index

Set project_revision to the file’s own number. The Rules page does not switch rules on or off; a change file does.

Kind of rule: Pairs suggested for a look (proposes). Proposes that two files are related in one of the eight ways, for a person to look at. A proposal is never a conclusion.
What it concludes: succeeds
Reasoning: defeasible. A conclusion is usually right, and is retracted when a rule it names concludes against it.
What it reads: one file at a time
Where it looks for pairs: within replicates_of_one_condition

Is it available in this version?#

Yes. The engine runs it.

What would defeat it#

It names no rule whose conclusion would defeat it.

Parameters#

Parameter	Shipped value	May be	What it does
`ordering_kind`	`"indexed"`	text	The component kind that carries the order. Indexed counts by a running number written alone (001, 002) and by an indexed label (rep1, rep2), where the numbers count; where they tie, are no numbers or do not count (488, 561), the set abstains.
`tolerance_seconds`	`60`	whole number, from 0 to 86400	How far the files’ own clocks (an instrument’s or a document’s) may run against the order the numbers give before the set is not put in order.