Skip to content

One of the Docker Images has a fine-tuned Yamnet-tensorflow model that serves predictions. Other containers are for uploading audio files and sending a request to the previous container for prediction. If prediction comes out as true, the said audio file is redownloaded again for futher analysis of the audio by a doctor.

License

Notifications You must be signed in to change notification settings

vsnupoudel/snoring_endpoint01

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

19 Commits
 
 
 
 
 
 
 
 

Repository files navigation

snoring_endpoint01

Following is the project in brief:

  1. I fine-tuned a Yamnet audio tf-model to classify audio (.wav files supported for now) into snoring or not-snoring. Trained on fresh audio data.
  2. Containerised the model into tfserving, which is the default tensorflow serving docker container.
  3. 2 other REST endpoints made for uploading .wav files, and downloading files ( but only if they are predicted as positive)
  4. mongodb and mysql docker containers used in minikube. In case of GKE, mongodb atlas and mysql were both used from gcp service.
  5. Works both on local minikube and Google Cloud - GKE.

In works.

  • Asynchronous calls to endpoints could improve speed.
  • Scaling test for real-world use

About

One of the Docker Images has a fine-tuned Yamnet-tensorflow model that serves predictions. Other containers are for uploading audio files and sending a request to the previous container for prediction. If prediction comes out as true, the said audio file is redownloaded again for futher analysis of the audio by a doctor.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published