Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix speech recognition application #74

Merged

Commits on May 22, 2024

  1. platforms: Change FreeRTOS Config tick rates

    Tick rates are modified for all platforms to
    fix speech-recognition application with software
    inference issues related to incorrect inferred
    sentence.
    
    Signed-off-by: Ahmed Ismail <[email protected]>
    AhmedIsmail02 committed May 22, 2024
    Configuration menu
    Copy the full SHA
    4dfa94e View commit details
    Browse the repository at this point in the history
  2. speech-recognition: Increase the block time for DSP task

    The block time for the DSP task in speech-recognition application
    is increased from `120` ms to `140` ms as it seems to be overusing
    the CPU which result in incorrect inference with Software inference
    engine configuration.
    
    Signed-off-by: Ahmed Ismail <[email protected]>
    AhmedIsmail02 committed May 22, 2024
    Configuration menu
    Copy the full SHA
    628ea6f View commit details
    Browse the repository at this point in the history
  3. nightly-ci: Run tests as part of script section

    pytests inside the nightly jobs `sw-vsi-config-test`,
    and `gnu-toolchain-test` should be run as part of the
    `script` section of these jobs as running the tests
    in the `after_script` section of these jobs won't
    have an influence on the exit code of the pipeline
    which might lead to false negative misleading CI results.
    
    Signed-off-by: Ahmed Ismail <[email protected]>
    AhmedIsmail02 committed May 22, 2024
    Configuration menu
    Copy the full SHA
    6375001 View commit details
    Browse the repository at this point in the history
  4. python-tests: Exit test from one point

    It is always better to have a single return/exit
    from a function/test in which it would be easier for
    users to understand.
    
    Signed-off-by: Ahmed Ismail <[email protected]>
    AhmedIsmail02 committed May 22, 2024
    Configuration menu
    Copy the full SHA
    0c49309 View commit details
    Browse the repository at this point in the history