Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • K kedgi
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • public_projects
  • kedgi
  • Issues
  • #6

Closed
Open
Created May 26, 2020 by Oliver Kirsebom@kirsebomOwner10 of 10 tasks completed10/10 tasks

Issues to be addressed before release

Hi @xuhui_liu , I have reviewed the Kedgi app. Good work. Please take some time to fix the issues listed below. Thanks.

  1. In the environment files, change the environment name from adi_env to kedgi_env. Remember to also change the name in run_app.sh, the readme file, the doc files, and everywhere else the name is used.

  2. The repository takes up almost 500 MB! Why is it so large? Would be good to reduce the size considerably.

  3. Under settings -> advanced, change the path of the project from acoustic_detector_interface to kedgi.

  4. The readme file should start with a high-level introduction to the app, which explains what the purposes of the app is, etc. Also, this first paragraph should contain a link to the sphinx docs. For inspiration, see for example the readme file of Kadlu or Ketos. (The same high-level intro can be used in the sphinx docs)

  5. The paragraph describing how to run the app also contains installation instructions, which belong in the previous paragraph. Please separate correctly.

  6. In the sphinx docs, I would suggest to separate the two tutorials into two separate pages. Also I would make it more clear that the first tutorial is for users, whereas the second tutorial is for developers.

  7. Is the data folder needed? It only contains a single file called grunt.csv.

  8. I cannot find the toy_detector_1.zip file.

  9. Does the docs/build folder need to be included in the repository? I do not think so ...

  10. In the sphinx docs, I would replace 'Platform of underwater acoustic detections and classifications models' with 'Graphical interface for acoustic detectors' or something along those lines

Edited May 29, 2020 by Xuhui Liu
Assignee
Assign to
Time tracking