alopez3702 / gun-detect Goto Github PK

This project currently does not delete files from the Minio Client once they have been used by Session 2. Theoretically, since those images have been used by Session 2, they do not need to be used again and can safely be deleted, thus freeing up space in the Minio Client. However, it was feared that deleting files may cause other issues. We also didn't want others to concern themselves with "garbage collection".
Because of this, if the code is left running for a long time, one could potentially fill up their Minio Client.
To fix this issue, code has been commented into Session 2. This code deletes files from the Minio Client once they have been used by Session 2.
To use it, just un-comment it. See lines 177 and 189 - 198 on camera-person-session-two.py

In person-camera-session-two.py, when using the bash command BOTH, it loads the model files called 'frozen_inference_graph.pb' and 'frozen_inferecne_graph.txt'. On line 213, an error appears:
KeyError: "the name 'final_result:0' refers to a tensor which does not exist. The operation, 'final_result', does not exist in the graph."
It is believed this is involved in how the model was trained. During training the model and/or freezing the inference graph, a tensor is made. The code is looking for the tensor called 'final_result:0', but can't find it. The model may need to be retrained, and during training, a tensor called 'final_result:0' would need to be made. Some adjustments may need to be made to the config file used to train it or to the code export_inference_graph.py, although it is unknown which changes need to be made.
Even though the model is trained, it effectively can't be used until this error is resolved.

Sometimes, when trying to store newly created files into the Minio Client bucket that is being used, Session 1 just will fail in trying to store them. This doesn't invoke any errors and the cause is unknown. What is known is that it only happened when trying to store files in a Minio Client bucket that was stored with many, many, many files.
To fix the problem, I changed which bucket I was storing images to and began to store images in an empty bucket. After that, the issue went away completely and files were being stored.
The code as it is creates a bucket called "test" in the Minio Client and stores files to that bucket. If one wants to change which bucket is being used, they'll have to change every instance of "test" in Session 1 and Session 2.