Hello again! Thank you so much for the help on my last issue.
I would like to request that the temp files made in the temp directory have some kind of naming scheme that makes them easy to parse through in the case of a job kill. Perhaps this could help with jobs picking up where they leave off - if the chromosome name is in the filename, and then that name is changed to indicate that the chromosome is done in some way, when the threads get a job they can look through the temp dir (if saved) and if the chromosome they've been assigned is already done, then they can mark that job as done and get their next one.
I've never done coding for multithreaded processes so this is just an idea, but even if this idea isn't feasible or well optimized I think having the files named something human-readable would make parsing through large data sets easier.
Thanks!
Hello again! Thank you so much for the help on my last issue.
I would like to request that the temp files made in the temp directory have some kind of naming scheme that makes them easy to parse through in the case of a job kill. Perhaps this could help with jobs picking up where they leave off - if the chromosome name is in the filename, and then that name is changed to indicate that the chromosome is done in some way, when the threads get a job they can look through the temp dir (if saved) and if the chromosome they've been assigned is already done, then they can mark that job as done and get their next one.
I've never done coding for multithreaded processes so this is just an idea, but even if this idea isn't feasible or well optimized I think having the files named something human-readable would make parsing through large data sets easier.
Thanks!