This is possibly just not good user practice rather than a software issue, but may want thinking about at some point in the future, so just recording it for reference.
If there is data telemetry, files which are acquired will be deleted from pycam/Images as they are downloaded. If a user is in the field also connected to the instrument and also trying to grab data so that they view it locally, there can be errors thrown by ftplib as files will be deleted by the telemetry before the local instrument can grab them (or vice versa).
Perhaps the software should always download from the SSD rather than the pycam/Images folder? And then just attempt to delete the file in the pycam/Images folder if it still exists. This way we still make sure the pycam/Images backup is removed when it is redundant but FTP transfers will never fail to find a file.
This is possibly just not good user practice rather than a software issue, but may want thinking about at some point in the future, so just recording it for reference.
If there is data telemetry, files which are acquired will be deleted from
pycam/Images
as they are downloaded. If a user is in the field also connected to the instrument and also trying to grab data so that they view it locally, there can be errors thrown byftplib
as files will be deleted by the telemetry before the local instrument can grab them (or vice versa).Perhaps the software should always download from the SSD rather than the
pycam/Images
folder? And then just attempt to delete the file in thepycam/Images
folder if it still exists. This way we still make sure thepycam/Images
backup is removed when it is redundant but FTP transfers will never fail to find a file.