You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In earlier versions of the looper, the pipeline interface was defined in the PEP (as sample attributes). Relative paths were considered relative to the PEP sample table, I guess.
But 2 things have changed:
In the dev version of looper that introduces looper config, the pipeline interface is defined in the looper config file.
now that looper can get PEPs from PEPhub, what should a relative path be relative to ? In the current implementation, this has been made relative to the current working directory.
This is a problem, because it means I can't just change from a local to a PEPhub PEP, leaving the rest of the file the same. I would also have to change the pipeline interface relative paths.
Shouldn't the pipeline interfaces (and other looper settings) be made relative to the looper config file, now that that's where they're specified (instead of the PEP or sample table)?
The text was updated successfully, but these errors were encountered:
In earlier versions of the looper, the pipeline interface was defined in the PEP (as sample attributes). Relative paths were considered relative to the PEP sample table, I guess.
But 2 things have changed:
This is a problem, because it means I can't just change from a local to a PEPhub PEP, leaving the rest of the file the same. I would also have to change the pipeline interface relative paths.
Shouldn't the pipeline interfaces (and other looper settings) be made relative to the looper config file, now that that's where they're specified (instead of the PEP or sample table)?
The text was updated successfully, but these errors were encountered: