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
It seems that the app currently uses the parameter study_slide to specify the output file name, but I can't see anywhere that can be specified.
I think currently just generating a study_slide and incrementing it based on the order an image happens to be in a folder should not be the default behavior. In most use cases, the user would either provide a very simple CSV file with. , or the app simply preserves the existing filename, but maybe adds. ".deid." which is what I have been doing internally during testing.
In most use cases, the user would not only hand over the raw images, but some basic manifest that maps the files to some basic metadata. With the current implementation, there doesn't seem to be a simple way to even figure out the map of OldFileName --> NewFileName without doing a lot of work.
At the very least, exporting a deidManifest file with the mapping would allow the user to then update/modify them during whatever QC process they are going to run to make sure all the files they wanted to be processed were actually processed.
The text was updated successfully, but these errors were encountered:
It seems that the app currently uses the parameter study_slide to specify the output file name, but I can't see anywhere that can be specified.
I think currently just generating a study_slide and incrementing it based on the order an image happens to be in a folder should not be the default behavior. In most use cases, the user would either provide a very simple CSV file with. , or the app simply preserves the existing filename, but maybe adds. ".deid." which is what I have been doing internally during testing.
In most use cases, the user would not only hand over the raw images, but some basic manifest that maps the files to some basic metadata. With the current implementation, there doesn't seem to be a simple way to even figure out the map of OldFileName --> NewFileName without doing a lot of work.
At the very least, exporting a deidManifest file with the mapping would allow the user to then update/modify them during whatever QC process they are going to run to make sure all the files they wanted to be processed were actually processed.
The text was updated successfully, but these errors were encountered: