Proposal to implement a new command or other functionality which would automate updating metadata stored about the run and each of its project, and synchronise this across a run.
Some examples:
Updates made to user, PI, organism etc in projects.info should be propagated to the project's README file (with the option of forcing an update to the QC reports if appropriate)
Update the list of sample names stored in projects.info and the project README file based on the Fastqs present in the project
Update the endedness metadata in the project README file (i.e. whether project is paired-end or single-end) based on the Fastqs in the project
Update the paths stored in auto_process.info (in the top-level run directory) and the qc.info files (in each QC directory) to reflect the current location.
This could reuse functionality already present in the update_project_metadata.py utility (which should be dropped); it would also address the underlying complaint in issue #49.
Proposal to implement a new command or other functionality which would automate updating metadata stored about the run and each of its project, and synchronise this across a run.
Some examples:
projects.infoshould be propagated to the project'sREADMEfile (with the option of forcing an update to the QC reports if appropriate)projects.infoand the projectREADMEfile based on the Fastqs present in the projectREADMEfile (i.e. whether project is paired-end or single-end) based on the Fastqs in the projectauto_process.info(in the top-level run directory) and theqc.infofiles (in each QC directory) to reflect the current location.This could reuse functionality already present in the
update_project_metadata.pyutility (which should be dropped); it would also address the underlying complaint in issue #49.