You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I've been informed that running a pipeline containing SaveCroppedObjects on S3 fails since it generates invalid paths, and so "Prefix saved crop image name with input image name" cannot be used.
Describe the solution you'd like
I suggest modifying the settings to mirror those in SaveImages, particularly the following:
Select method for constructing file names
Select image name for file prefix
Enter single file name
Append a suffix to the image file name?
Text to append to the image name
Describe alternatives you've considered
Since we use an analysis platform which uses LoadData-enabled pipelines, we considered having the backend rename the images according to the Barcode/Row/Column/Field columns in the image list CSV. However, a change to the settings themselves would be easier to handle.
Additional context
The S3 issue may be a bug so I'm happy to open an issue against that specifically. However, to be clear, this feature request concerns a change to settings to mitigate the problem.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I've been informed that running a pipeline containing
SaveCroppedObjects
on S3 fails since it generates invalid paths, and so "Prefix saved crop image name with input image name" cannot be used.Describe the solution you'd like
I suggest modifying the settings to mirror those in
SaveImages
, particularly the following:Select method for constructing file names
Select image name for file prefix
Enter single file name
Append a suffix to the image file name?
Text to append to the image name
Describe alternatives you've considered
Since we use an analysis platform which uses
LoadData
-enabled pipelines, we considered having the backend rename the images according to the Barcode/Row/Column/Field columns in the image list CSV. However, a change to the settings themselves would be easier to handle.Additional context
The S3 issue may be a bug so I'm happy to open an issue against that specifically. However, to be clear, this feature request concerns a change to settings to mitigate the problem.
The text was updated successfully, but these errors were encountered: