Stated count may mark replicates

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

A name stating a small count, such as N=3, is flagged: on a program or on a file past the point of recording it is read as how many things the file rests on, and on a recording, or wherever the step is unclear, as which one of several it is, for you to confirm.

stated_count_may_mark_replicates version 2+d1

• Kind of rule: What is raised for attention (flags). Raises something for a person’s attention without concluding anything.

• What it concludes: a finding

• 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

Is it available in this version?

Yes. The engine runs it.

What would defeat it

A finding is never withdrawn. When any of these rules also concludes about the same thing, the finding records it:

• installed_software_in_folder: A folder is recognized as an installed program, such as a copy of Fiji or a Python environment, from the parts it holds, a name ending .app, its program-style subfolders or a majority of program files; its files are still indexed and read, and rules about experiments leave them alone.

It stands aside beneath every folder one of these rules raises:

• installed_software_in_folder

Parameters

Parameter	Shipped value	May be	What it does
maximum_count	9	whole number, from 1 to 99	How large a stated count may be and still describe a replicate set. A bound, and past it the number is a true count of something that is not a replicate design.
theme_kind	"count"	text	The axis whose matched labels are read. Not replicate: a stated count is a cardinality and an indexed label an ordinal, and on one axis the rule that reads a position would conclude one as the other.
stage_rules	["pipeline_stage_from_name", "acquisition_stage_from_format", "analysis_stage_from_derived_sense"]	list of text	The rules whose conclusion is read as this file’s stage. Named rather than matched on the concluded value, so a revision renaming one passes its own name and no rule becomes a stage rule by happening to conclude a word a workflow uses as a rung.
observation_rules	["acquisition_stage_from_format"]	list of text	Rules whose conclusion makes the file an observation whatever the workflow says: an instrument’s own extension is what the instrument wrote, and no declaration outranks it.
derivation_rules	["program_from_extension"]	list of text	Rules whose conclusion makes the file a derivation whatever the workflow says: a program exists to do something to something else, so a script stating N=3 states what it rests on.