Closed donaldcampbelljr closed 1 week ago
Related to this Pipestat enhancement: https://github.com/pepkit/pipestat/issues/125
Can Looper easily distinguish between using an input pep and sending an output pep for results reporting via pipestat?
Pipestat now has the pephub_path parameter: psm = PipestatManager(pephub_path=pephuburl, schema_path=schema_file_path)
pephub_path
psm = PipestatManager(pephub_path=pephuburl, schema_path=schema_file_path)
But it does not search for this via a config file (yet), so Looper may not be able to send this information to Pipestat at this time.
Previous discussion: we decided it best to keep the input PEP separate from the output PEP.
There isn't an actionable item from this issue at the moment, so I will close it for now.
Related to this Pipestat enhancement: https://github.com/pepkit/pipestat/issues/125
Can Looper easily distinguish between using an input pep and sending an output pep for results reporting via pipestat?
Pipestat now has the
pephub_path
parameter:psm = PipestatManager(pephub_path=pephuburl, schema_path=schema_file_path)
But it does not search for this via a config file (yet), so Looper may not be able to send this information to Pipestat at this time.
Previous discussion: we decided it best to keep the input PEP separate from the output PEP.