search

orcasound / orcaal

Orca detection Active Learning (Orca AL) tool -- https://ai4orcas.net/portfolio/orca-al/
https://orcasound.github.io/orcaal/
MIT License
7 stars 6 forks source link

Improve logging utilities #32

Open Benjamintdk opened 2 years ago

Benjamintdk commented 2 years ago

Currently, the logging in the repository mostly uses print statements, an example which can be seen here. While this is useful, we want something more robust in the long run that can be more informative about the kind of bugs/errors that we might face. Improve the logging across all the backend services by using a dedicated logging library.

nawed2611 commented 2 years ago

Can I work on this issue?

Benjamintdk commented 2 years ago

Hi @nawed2611, welcome to OrcaAL. Yes, this issue is currently not yet being handled, so you can feel free to work on it and read up on what might be a good logging library to use. I'd suggest also taking sometime to familiarize yourself with the existing code base and how to set up all the various services. Currently, the setup is still very tied to AWS, so you might have some issues accessing the data and resources. Do let us know if you require assistance with this, and keep a look out for the refactor-datahandlers branch as it's currently in works and hopes to allow a local data source instead for easier on-boarding of new developers!

nawed2611 commented 2 years ago

Thanks for the reply! I'll get started with this and let you know if I get stuck

Benjamintdk commented 2 years ago

@nawed2611 the feature for the local setup is done, and can be found in the refactor-datahandlers branch. You can clone the branch onto your local machine, and follow the instructions in the ReadMe to set up the Docker environment locally. If all runs well, you can proceed to improve the logging utilities.

Do let me know if you run into any issues :)

ramvikrams commented 2 years ago

Currently, the logging in the repository mostly uses print statements, an example which can be seen here. While this is useful, we want something more robust in the long run that can be more informative about the kind of bugs/errors that we might face. Improve the logging across all the backend services by using a dedicated logging library.

You mean all the print statements in this repo have to be changed with a logger