Pipeline stage from name

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

A file is placed at the step of the work its name states, such as raw, processed or analysis, unless it is a program or sits inside an installed program.

pipeline_stage_from_name version 2

• Kind of rule: What files are (classifies). Says what a file or a folder is, by placing it in a class.

• What it concludes: a class

• 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

What this rule concludes about something is withdrawn when any of these rules concludes about the same thing:

• program_from_extension: Files whose extensions come from programming or macro languages, such as .py, .R or an ImageJ macro, are recognized as programs, unless their contents say otherwise.

• 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.

Parameters

Parameter	Shipped value	May be	What it does
theme_kind	"stage"	text	The axis to read.
senses	["raw", "acquisition", "preprocessed", "intermediate", "processed", "analysis", "pooled", "quantification", "summary", "report", "export"]	list of text	The pipeline stages. The transformations applied at a stage, such as cropped or stitched, are left out, and so is unaffiliated.
minimum_senses	1	whole number, from 1 to 10	How many distinct stages a name needs.