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
To better ensure that the results from scpca-nf are stable and allow easier comparisons between the production results and any changes in progress, we should create separate staging and production profiles, with separate output locations for checkpoints and results.
The current ccdl profile uses an output location that is effectively a testing ground; there are no particular controls on the data that are found there. When we are performing a production run, we currently set the output location to the scpca-prod directory manually with the --outdir parameter, but this is a bit brittle and, well, manual.
Instead, we should define ccdl_staging and ccdl_prod profiles that set appropriate output paths.
For extra protection, we may want to see if we can restrict the production profile so that will only run with a versioned tag (so we do not accidentally overwrite results from a development version of the workflow).
This issue should also include:
Creation of an appropriate staging output location (scpca-staging), which will begin as a duplicate of the scpca-prod directory
To better ensure that the results from
scpca-nf
are stable and allow easier comparisons between the production results and any changes in progress, we should create separate staging and production profiles, with separate output locations for checkpoints and results.The current
ccdl
profile uses an output location that is effectively a testing ground; there are no particular controls on the data that are found there. When we are performing a production run, we currently set the output location to thescpca-prod
directory manually with the--outdir
parameter, but this is a bit brittle and, well, manual.Instead, we should define
ccdl_staging
andccdl_prod
profiles that set appropriate output paths.For extra protection, we may want to see if we can restrict the production profile so that will only run with a versioned tag (so we do not accidentally overwrite results from a development version of the workflow).
This issue should also include:
scpca-staging
), which will begin as a duplicate of thescpca-prod
directoryThe text was updated successfully, but these errors were encountered: