Group incomplete against workflow#

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

Not available in this version. A group is flagged as incomplete when it has nothing at one of the steps raw, processed or analysis, naming the step that is missing.

group_incomplete_against_workflow version 1+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: a group of files

Is it available in this version?#

Not available in this version. Its test is declared and not written yet, so the engine skips it and it concludes nothing.

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:

Parameters#

Parameter

Shipped value

May be

What it does

required_stages

["raw", "processed", "analysis"]

list of text

The stages every group is expected to hold. Entirely the user’s definition: a field where acquisition and analysis are separate efforts will remove one, and the engine has no opinion.