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
The flowJo parser generates temporary h5 folders and h5 files for each run. Right now we set the default h5_dir as /tmp or Rtmp and let os or R session to do the clean up job.
If we ever want to proactively do the garbage collection to avoid flooding the fs by the large number of temporary h5s (given os may not clean /tmp folder as frequent).
We will have to maintain a global counter (at cytolib level) for each GatingSet in order to decide whether to delete the associated h5 folder. It may not always be easy, because GatingSet can be loaded from user-archived folder, which we don't necessarily want to delete them after it is done.
What makes it more complicated is, CytoFrame can potentially live outside of the scope of GatingSet and we then also need to have a counter per frame.
For now, I will leave it as it is. We can revisit this issue as needed later.
The text was updated successfully, but these errors were encountered:
The flowJo parser generates temporary
h5
folders andh5
files for each run. Right now we set the defaulth5_dir
as/tmp
orRtmp
and letos
orR
session to do the clean up job.If we ever want to proactively do the garbage collection to avoid flooding the
fs
by the large number of temporary h5s (givenos
may not clean/tmp
folder as frequent).We will have to maintain a global counter (at
cytolib
level) for eachGatingSet
in order to decide whether to delete the associated h5 folder. It may not always be easy, becauseGatingSet
can be loaded from user-archived folder, which we don't necessarily want to delete them after it is done.What makes it more complicated is,
CytoFrame
can potentially live outside of the scope ofGatingSet
and we then also need to have a counter per frame.For now, I will leave it as it is. We can revisit this issue as needed later.
The text was updated successfully, but these errors were encountered: