Replies: 1 comment 7 replies
-
@amg369 When your rename them, do you load them into memory? That takes time. There is way to not load them into memory and straight copy to another location with new name. Additionally, use your multiprocessing. I am sure you have several cores. |
Beta Was this translation helpful? Give feedback.
7 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Our MGH waveforms are in Bedmaster HD5 format, with the only PHI that I can identify being the filename itself, which is the PatientEncounterID. Our files are stored in a Windows shared network drive and I was debating the merits of copying the files to another shared location and renaming them there (since this the source is a common network drive and we don't have permissions to directly rename the files). However, this is extremely time consuming as some of these files are several GB. We're at this point considering creating a specific MGH only Azure cloud to move the files to, then rename when they are stored there.
In the meantime, does anyone have an efficient and relatively fast means of copying files in a Windows file structure or should we focus on bringing them up to an MGH Azure Cloud and then rename?
Beta Was this translation helpful? Give feedback.
All reactions