Add record of project_setup command

[mackenziemitchell]

Hi Will,

We would like to request that the command used to run project_setup be added automatically to the resulting folder (perhaps in the form of a txt file?). This is useful to track the symlink origin of data_DICOMS.

Thanks!
Mackenzie

[wasciutto]

Hi Mackenzie, thanks for the feedback -

Would you mind expanding on your use case for this? It's relatively quick to check the source of a symbolic link with ls -l, so would need a convincing scenario to justify adding an additional file to the root of a clpipe project, which is already getting cluttered.

There is the logs/clpipe.log file, which tracks commands run at the login node (as opposed to launched as jobs), which gives a (small) amount of information about project_setup - I wonder if this would be a better place to include the original source location instead, with an additional line? I definitely agree this should be, at minimum, logged.

So this:

2023-07-11 13:49:38 - willasc - INFO: clpipe.project-setup - Creating SymLink for source data to /nas/longleaf/home/willasc/repos/clpipe/tests/temp/test_project_setup_symlink_sou0/data_DICOMs
2023-07-11 13:49:38 - willasc - INFO: clpipe.project-setup - Completed project setup

Expanded to:

2023-07-11 13:49:38 - willasc - INFO: clpipe.project-setup - Creating SymLink for source data to /data_DICOMs from /path/to/source/data/dicoms
2023-07-11 13:49:38 - willasc - INFO: clpipe.project-setup - Completed project setup

[wasciutto]

Closed for now