Could the pipestat schema be adapted to integrate with the looper output schema? See #16
The looper output schema formally specifies the output produced by this pipeline. It is used by downstream tools to that need to be aware of the products of the pipeline for further visualization or analysis. Like the input schema, it is based on the extended PEP JSON-schema validation framework, but adds looper-specific capabilities.
Currently, the looper schema is used to define the output files of the pipeline. Each of these includes a path and the types are specified as being one of link, image, or file.
But pipelines also produce statistics -- primitive types, like string or int. In fact, that is what the pipestat schema specifies.
It would be more convenient if these two schemas became one. If looper is pipestat-aware, then the looper output schema should just be the pipestat schema. To do this:
- the looper schema would need to be adapted to allow it to specify pipestat types.
- the pipestat schema would have to be adapted to allow it to accommodate the looper types
Then, the two schemas could be combined; the pipeline interface would point to the pipestat schema as the output schema. Looper would use pipestat to manage outputs.
Could the pipestat schema be adapted to integrate with the looper output schema? See #16
Currently, the looper schema is used to define the output files of the pipeline. Each of these includes a
pathand the types are specified as being one oflink,image, orfile.But pipelines also produce statistics -- primitive types, like
stringorint. In fact, that is what the pipestat schema specifies.It would be more convenient if these two schemas became one. If looper is pipestat-aware, then the looper output schema should just be the pipestat schema. To do this:
Then, the two schemas could be combined; the pipeline interface would point to the pipestat schema as the output schema. Looper would use pipestat to manage outputs.