Open gmhhope opened 6 months ago
This is largely OS dependent. Most do not allow symbolic links across device partitions. I have no intention of fixing this directly because that is probably a restriction for a good reason, rather, you can use '--file_mode=copy' in the assemble step to copy the files instead of symbolically linking them. This will however, make a copy of the file to the partition where the pcpfm is being ran from which may or may not be a good thing depending on your use case. Alternatively if you have your files on an external drive, cd to the drive partition and process the data there.
Just FYI. This requirement was only due to Asari. Now Asari no longer needs all the files to be in the same place (will be merged into V2). In a future version of the pipeline, this will be fixed as files will no longer need to be moved/linked/copied at all during processing.
I'm going to reopen the issue as now I intend to fix this as it is fixed in Asari too.
Cross-device link" error when running assemble
Describe the bug When running the
pcpfm
tool, an OSError with code 18 occurs, indicating a "Cross-device link" error. This error arises when attempting to create a hard link between files located on different devices.To Reproduce Steps to reproduce the behavior:
pcpfm
command with specific parameters.Expected behavior The
pcpfm
tool should successfully add the acquisition without encountering a cross-device link error.Screenshots N/A
Desktop
Additional context This error likely arises due to attempting to copy or move files across different filesystems or partitions. The
pcpfm
tool could be modified to handle copying files across devices more gracefully, perhaps by using a method that automatically handles such scenarios(generated from chatGPT)