Derivation by a scripts calls

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

A file is suggested as made from another when one script’s own lines read the second by name and write the first by name, which says which came first; never inside an installed program.

derivation_by_a_scripts_calls version 1

• 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: derives, named processed_from

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

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:

• 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
describing_formats	["python_source", "matlab_source", "imagej_macro"]	list of text	The script types whose calls are read: the languages the dive reads calls in.
minimum_resolution	"unique_basename"	one of exact, unique_suffix, unique_basename	How firmly each name must have resolved: beside the script is exact, and found by name among its experiment’s files is unique_basename.