DM-39214: Move ingredient pipelines into _ingredients dir

[leeskelvin]

No description provided.

[kfindeisen]

I'm a bit concerned about applying the boilerplate to some of ap_verify's weirdness, but otherwise looks good.

[kfindeisen]

The original description sounds a bit odd, as if you were documenting a natural phenomenon:

Suggested change

	Pipelines within the ingredients directory tend to be imported by other pipelines, and are not intended to be used directly by end-users for science purposes.
	Pipelines within the ingredients directory are meant to be imported by other pipelines, and are not intended to be used directly by end-users for science purposes.

[kfindeisen]

Nothing in ap_verify should be used for science purposes, something I occasionally butt heads with users about. Perhaps:

Suggested change

	Pipelines within the ingredients directory tend to be imported by other pipelines, and are not intended to be used directly by end-users for science purposes.
	Pipelines within the ingredients directory tend to be imported by other pipelines, and are not intended to be used directly by end-users for verification purposes.

[leeskelvin]

This may be a matter of definition - isn't verification a part of the scientific process? If this is a point of contention then we could just remove the latter part of this sentence, ending with "by end-users."

[kfindeisen]

When I hear a phrase like "science runs" or "scientific processing", it usually means running a pipeline on a generic set of data. The ap_verify pipelines, unlike the ap_pipe pipelines, are not designed to be run on anything other than a packaged ap_verify dataset -- it might work, but it's very Not Supported.

I'm fine with just removing the final phrase.

[kfindeisen]

Suggested change

	The pipelines defined here are intended to be used as building blocks for more complex pipelines.
	As such, they are not intended to be used directly by end-users for science purposes.
	Science ready pipeline definitions are located in the [pipelines](..) directory.
	The pipelines defined here are intended to be used as building blocks for more complex pipelines.
	As such, they are not intended to be used directly by end-users for verification purposes.
	Standalone pipeline definitions are located in the [pipelines](..) directory.

[leeskelvin]

See above for discussion.

[leeskelvin]

Modifying this sentence to end with "by end-users.", as discussed above.

[leeskelvin]

Replacing "Standalone" with "User-facing". The term standalone to me implies that these may be used in isolation, but more often than not they import a series of other pipeline YAMLs in order to function correctly.