If the inputs contain a filename clash (ie there are subdirectories containing the raw input data, and one or more of the files among these directories have identical basenames) the setup script will print a warning message such as:
ln: failed to create symbolic link 'Raw_data/ZenoTof_LS_MM_D_60_1.wiff': File exists
ln: failed to create symbolic link 'Raw_data/ZenoTof_LS_MM_D_60_1.wiff.scan': File exists
ln: failed to create symbolic link 'Raw_data/ZenoTof_LS_MM_A_38_3.wiff': File exists
ln: failed to create symbolic link 'Raw_data/ZenoTof_LS_MM_A_38_3.wiff.scan': File exists
The setup script will run to completion, but only one of the files for each identical name will be linked. User will need to check these files and either rename the affected files to avoid clashes, or delete any unintended duplicates from the source directory. Then unlink the linked files and rerun setup to ensure the Raw_data dir is clean.
If the inputs contain a filename clash (ie there are subdirectories containing the raw input data, and one or more of the files among these directories have identical basenames) the setup script will print a warning message such as:
The setup script will run to completion, but only one of the files for each identical name will be linked. User will need to check these files and either rename the affected files to avoid clashes, or delete any unintended duplicates from the source directory. Then unlink the linked files and rerun setup to ensure the Raw_data dir is clean.