Added is09-13 configs - #124

Merged
hagenw merged 3 commits into
audeering:mainfrom
ATriantafyllopoulos:is09-13
Jul 31, 2025
Merged

Added is09-13 configs#124
hagenw merged 3 commits into
audeering:mainfrom
ATriantafyllopoulos:is09-13

Conversation

@ATriantafyllopoulos

@ATriantafyllopoulosATriantafyllopoulos commented Jul 15, 2025

Copy link
Copy Markdown
Contributor

This PR adds standard config files for the IS09-13 feature sets. The config files are all taken from the original repo with the only change being the use of external source and sink components for reading/writing.

Summary by Sourcery

Add standardized openSMILE config files for the IS09-13 feature sets, update the FeatureSet enum to include IS09--IS13, and include the new configs in the package distribution.

New Features:

  • Add FeatureSet enum entries for IS09 through IS13 with doc links and config paths
  • Provide openSMILE configuration files for IS09 emotion, IS10 paralinguistics (compatibility and core), IS11 speaker state, IS12 speaker trait compatibility, and IS13 ComParE (core, functionals, vocalist)

Enhancements:

  • Use external source and sink components across all new configs

Build:

  • Include config/is09-13 directory in package data

@sourcery-ai

sourcery-aiBot commented Jul 15, 2025

Copy link
Copy Markdown
Contributor

Reviewer's Guide

This PR integrates support for the IS09–IS13 openSMILE feature sets by registering new FeatureSet values, packaging a new config directory, and importing the standard config files (adapted to external I/O) under opensmile/core/config/is09-13.

ER diagram for FeatureSet and config files

erDiagram
FEATURESET ||--o{ CONFIG_FILE : uses
FEATURESET {
string name
string config_path
}
CONFIG_FILE {
string filename
string path
}
Loading

Class diagram for updated FeatureSet enum

classDiagram
class FeatureSet {
<<enum>>
ComParE_2016
GeMAPS
eGeMAPS
emobase
IS09
IS10
IS11
IS12
IS13
}
Loading

File-Level Changes

ChangeDetailsFiles
Extend FeatureSet enum to include IS09–IS13
  • Added new enum members IS09, IS10, IS11, IS12, IS13
  • Inserted corresponding Sphinx documentation links
  • Updated enum value mappings to point at is09-13 paths
opensmile/core/define.py
Include is09-13 configs in packaged data
  • Added "config/is09-13/*" to setup.py package_data
setup.py
Add IS09–IS13 configuration files
  • Imported and adapted official openSMILE configs for IS09 (emotion), IS10 (paraling), IS11 (speaker state), IS12 (speaker trait), IS13 (ComParE)
  • Replaced internal source/sink components with external placeholders
  • Organized configs into .conf and .inc files under opensmile/core/config/is09-13
opensmile/core/config/is09-13/*

Possibly linked issues

  • WIP: Init #1: The PR adds IS10_paraling config with external source/sink, directly addressing the issue's request and error.

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-aisourcery-aiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @ATriantafyllopoulos - I've reviewed your changes - here's some feedback:

  • Consider splitting this large PR into smaller, logical commits (e.g. enum updates, setup changes, then each feature‐set config) to make the review more manageable.
  • There’s substantial repetition across the new config files; extract shared headers and repeated component definitions into common include files to reduce duplication and simplify future maintenance.
  • In setup.py, ensure the 'config/is09-13/' glob recursively captures all nested directories and files (or switch to a '**/' pattern) so no configs are accidentally omitted.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments- Consider splitting this large PR into smaller, logical commits (e.g. enum updates, setup changes, then each feature‐set config) to make the review more manageable.
- There’s substantial repetition across the new config files; extract shared headers and repeated component definitions into common include files to reduce duplication and simplify future maintenance.
- In setup.py, ensure the 'config/is09-13/*' glob recursively captures all nested directories and files (or switch to a '**/*' pattern) so no configs are accidentally omitted.
## Individual Comments### Comment 1
<location> `opensmile/core/config/is09-13/IS12_speaker_trait_compat.conf:339` </location>
<code_context>
+instance[melspecMfcc].type=cMelspec
+instance[mfcc].type=cMfcc
+
+[melspecMfcc:cMelspec]
+reader.dmLevel=fftmagH25
+writer.dmLevel=melspecMfcc
+copyInputName = 1
+processArrayFields = 1
+; htk compatible sample value scaling
+htkcompatible = 1
+nBands = 26s
+; use power spectrum instead of magnitude spectrum
+usePower = 1
</code_context>
<issue_to_address>
Possible typo: 'nBands = 26s' contains an unexpected 's'.
Please check if 'nBands' should be set to an integer value, such as 26, instead of '26s'.
</issue_to_address>
<suggested_fix>
<<<<<<< SEARCH
nBands = 26s
=======
nBands = 26
>>>>>>> REPLACE
</suggested_fix>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment threadopensmile/core/config/is09-13/IS12_speaker_trait_compat.conf
@hagenw

Copy link
Copy Markdown
Member

@ATriantafyllopoulos what is the usecase for those configs?

/cc @ureichel@maxschmitt

@ATriantafyllopoulos

Copy link
Copy Markdown
ContributorAuthor

@ATriantafyllopoulos what is the usecase for those configs?

/cc @ureichel@maxschmitt

I want to finally make a paper I wrote for Interspeech last year fully reproducible..

Also, these are the standard config files used in the early versions of the ComParE challenge. If someone wants to reproduce these results with modern tools (Python), this will be useful

@codecov

codecovBot commented Jul 25, 2025

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.0%. Comparing base (9d7fd3d) to head (cf378dc).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
Files with missing linesCoverage Δ
opensmile/core/define.py100.0% <100.0%> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment threadopensmile/core/define.py
@hagenw

Copy link
Copy Markdown
Member

codespell is currently failing with

image

An easy fix would be to add the whole config folder to the skip entry in the [tool.codespell] section in pyproject.toml:

# ----- codespell ---------------------------------------------------------
[tool.codespell]
builtin = 'clear,rare,informal,usage,names'skip = './opensmile.egg-info,./build,./docs/api,./docs/_templates,./docs/examples','opensmile/core/config'

@hagenw

Copy link
Copy Markdown
Member

For the other linter fix you need to run ruff or pre-commit locally, see https://audeering.github.io/opensmile-python/contributing.html#coding-convention

@ATriantafyllopoulos

Copy link
Copy Markdown
ContributorAuthor

An easy fix would be to add the whole config folder to the skip entry in the [tool.codespell] section in pyproject.toml:

# ----- codespell ---------------------------------------------------------
[tool.codespell]
builtin = 'clear,rare,informal,usage,names'skip = './opensmile.egg-info,./build,./docs/api,./docs/_templates,./docs/examples','opensmile/core/config'

cf378dc (the syntax for the fix was a bit different but I followed your recommendation)

@hagenw

Copy link
Copy Markdown
Member

Great, thanks for fixing the tests, I will merge this now and prepare a new release.

@hagenw
hagenw merged commit 4074ec2 into audeering:mainJul 31, 2025
19 checks passed
@hagenw

Copy link
Copy Markdown
Member

Maybe the README is still slightly misleading:

image

But doesn't matter, I released version 2.6.0, so you should now be able to use your configs by installing this package.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@ATriantafyllopoulos@hagenw
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

Added is09-13 configs - #124

Merged
hagenw merged 3 commits into
audeering:mainfrom
ATriantafyllopoulos:is09-13
Jul 31, 2025
Merged

Added is09-13 configs#124
hagenw merged 3 commits into
audeering:mainfrom
ATriantafyllopoulos:is09-13

Conversation

@ATriantafyllopoulos

@ATriantafyllopoulosATriantafyllopoulos commented Jul 15, 2025

Copy link
Copy Markdown
Contributor

This PR adds standard config files for the IS09-13 feature sets. The config files are all taken from the original repo with the only change being the use of external source and sink components for reading/writing.

Summary by Sourcery

Add standardized openSMILE config files for the IS09-13 feature sets, update the FeatureSet enum to include IS09--IS13, and include the new configs in the package distribution.

New Features:

  • Add FeatureSet enum entries for IS09 through IS13 with doc links and config paths
  • Provide openSMILE configuration files for IS09 emotion, IS10 paralinguistics (compatibility and core), IS11 speaker state, IS12 speaker trait compatibility, and IS13 ComParE (core, functionals, vocalist)

Enhancements:

  • Use external source and sink components across all new configs

Build:

  • Include config/is09-13 directory in package data

@sourcery-ai

sourcery-aiBot commented Jul 15, 2025

Copy link
Copy Markdown
Contributor

Reviewer's Guide

This PR integrates support for the IS09–IS13 openSMILE feature sets by registering new FeatureSet values, packaging a new config directory, and importing the standard config files (adapted to external I/O) under opensmile/core/config/is09-13.

ER diagram for FeatureSet and config files

erDiagram
FEATURESET ||--o{ CONFIG_FILE : uses
FEATURESET {
string name
string config_path
}
CONFIG_FILE {
string filename
string path
}
Loading

Class diagram for updated FeatureSet enum

classDiagram
class FeatureSet {
<<enum>>
ComParE_2016
GeMAPS
eGeMAPS
emobase
IS09
IS10
IS11
IS12
IS13
}
Loading

File-Level Changes

ChangeDetailsFiles
Extend FeatureSet enum to include IS09–IS13
  • Added new enum members IS09, IS10, IS11, IS12, IS13
  • Inserted corresponding Sphinx documentation links
  • Updated enum value mappings to point at is09-13 paths
opensmile/core/define.py
Include is09-13 configs in packaged data
  • Added "config/is09-13/*" to setup.py package_data
setup.py
Add IS09–IS13 configuration files
  • Imported and adapted official openSMILE configs for IS09 (emotion), IS10 (paraling), IS11 (speaker state), IS12 (speaker trait), IS13 (ComParE)
  • Replaced internal source/sink components with external placeholders
  • Organized configs into .conf and .inc files under opensmile/core/config/is09-13
opensmile/core/config/is09-13/*

Possibly linked issues

  • WIP: Init #1: The PR adds IS10_paraling config with external source/sink, directly addressing the issue's request and error.

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-aisourcery-aiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @ATriantafyllopoulos - I've reviewed your changes - here's some feedback:

  • Consider splitting this large PR into smaller, logical commits (e.g. enum updates, setup changes, then each feature‐set config) to make the review more manageable.
  • There’s substantial repetition across the new config files; extract shared headers and repeated component definitions into common include files to reduce duplication and simplify future maintenance.
  • In setup.py, ensure the 'config/is09-13/' glob recursively captures all nested directories and files (or switch to a '**/' pattern) so no configs are accidentally omitted.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments- Consider splitting this large PR into smaller, logical commits (e.g. enum updates, setup changes, then each feature‐set config) to make the review more manageable.
- There’s substantial repetition across the new config files; extract shared headers and repeated component definitions into common include files to reduce duplication and simplify future maintenance.
- In setup.py, ensure the 'config/is09-13/*' glob recursively captures all nested directories and files (or switch to a '**/*' pattern) so no configs are accidentally omitted.
## Individual Comments### Comment 1
<location> `opensmile/core/config/is09-13/IS12_speaker_trait_compat.conf:339` </location>
<code_context>
+instance[melspecMfcc].type=cMelspec
+instance[mfcc].type=cMfcc
+
+[melspecMfcc:cMelspec]
+reader.dmLevel=fftmagH25
+writer.dmLevel=melspecMfcc
+copyInputName = 1
+processArrayFields = 1
+; htk compatible sample value scaling
+htkcompatible = 1
+nBands = 26s
+; use power spectrum instead of magnitude spectrum
+usePower = 1
</code_context>
<issue_to_address>
Possible typo: 'nBands = 26s' contains an unexpected 's'.
Please check if 'nBands' should be set to an integer value, such as 26, instead of '26s'.
</issue_to_address>
<suggested_fix>
<<<<<<< SEARCH
nBands = 26s
=======
nBands = 26
>>>>>>> REPLACE
</suggested_fix>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment threadopensmile/core/config/is09-13/IS12_speaker_trait_compat.conf
@hagenw

Copy link
Copy Markdown
Member

@ATriantafyllopoulos what is the usecase for those configs?

/cc @ureichel@maxschmitt

@ATriantafyllopoulos

Copy link
Copy Markdown
ContributorAuthor

@ATriantafyllopoulos what is the usecase for those configs?

/cc @ureichel@maxschmitt

I want to finally make a paper I wrote for Interspeech last year fully reproducible..

Also, these are the standard config files used in the early versions of the ComParE challenge. If someone wants to reproduce these results with modern tools (Python), this will be useful

@codecov

codecovBot commented Jul 25, 2025

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.0%. Comparing base (9d7fd3d) to head (cf378dc).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
Files with missing linesCoverage Δ
opensmile/core/define.py100.0% <100.0%> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment threadopensmile/core/define.py
@hagenw

Copy link
Copy Markdown
Member

codespell is currently failing with

image

An easy fix would be to add the whole config folder to the skip entry in the [tool.codespell] section in pyproject.toml:

# ----- codespell ---------------------------------------------------------
[tool.codespell]
builtin = 'clear,rare,informal,usage,names'skip = './opensmile.egg-info,./build,./docs/api,./docs/_templates,./docs/examples','opensmile/core/config'

@hagenw

Copy link
Copy Markdown
Member

For the other linter fix you need to run ruff or pre-commit locally, see https://audeering.github.io/opensmile-python/contributing.html#coding-convention

@ATriantafyllopoulos

Copy link
Copy Markdown
ContributorAuthor

An easy fix would be to add the whole config folder to the skip entry in the [tool.codespell] section in pyproject.toml:

# ----- codespell ---------------------------------------------------------
[tool.codespell]
builtin = 'clear,rare,informal,usage,names'skip = './opensmile.egg-info,./build,./docs/api,./docs/_templates,./docs/examples','opensmile/core/config'

cf378dc (the syntax for the fix was a bit different but I followed your recommendation)

@hagenw

Copy link
Copy Markdown
Member

Great, thanks for fixing the tests, I will merge this now and prepare a new release.

@hagenw
hagenw merged commit 4074ec2 into audeering:mainJul 31, 2025
19 checks passed
@hagenw

Copy link
Copy Markdown
Member

Maybe the README is still slightly misleading:

image

But doesn't matter, I released version 2.6.0, so you should now be able to use your configs by installing this package.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@ATriantafyllopoulos@hagenw
, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Added is09-13 configs - #124

Merged
hagenw merged 3 commits into
audeering:mainfrom
ATriantafyllopoulos:is09-13
Jul 31, 2025
Merged

Added is09-13 configs#124
hagenw merged 3 commits into
audeering:mainfrom
ATriantafyllopoulos:is09-13

Conversation

@ATriantafyllopoulos

@ATriantafyllopoulosATriantafyllopoulos commented Jul 15, 2025

Copy link
Copy Markdown
Contributor

This PR adds standard config files for the IS09-13 feature sets. The config files are all taken from the original repo with the only change being the use of external source and sink components for reading/writing.

Summary by Sourcery

Add standardized openSMILE config files for the IS09-13 feature sets, update the FeatureSet enum to include IS09--IS13, and include the new configs in the package distribution.

New Features:

  • Add FeatureSet enum entries for IS09 through IS13 with doc links and config paths
  • Provide openSMILE configuration files for IS09 emotion, IS10 paralinguistics (compatibility and core), IS11 speaker state, IS12 speaker trait compatibility, and IS13 ComParE (core, functionals, vocalist)

Enhancements:

  • Use external source and sink components across all new configs

Build:

  • Include config/is09-13 directory in package data

@sourcery-ai

sourcery-aiBot commented Jul 15, 2025

Copy link
Copy Markdown
Contributor

Reviewer's Guide

This PR integrates support for the IS09–IS13 openSMILE feature sets by registering new FeatureSet values, packaging a new config directory, and importing the standard config files (adapted to external I/O) under opensmile/core/config/is09-13.

ER diagram for FeatureSet and config files

erDiagram
FEATURESET ||--o{ CONFIG_FILE : uses
FEATURESET {
string name
string config_path
}
CONFIG_FILE {
string filename
string path
}
Loading

Class diagram for updated FeatureSet enum

classDiagram
class FeatureSet {
<<enum>>
ComParE_2016
GeMAPS
eGeMAPS
emobase
IS09
IS10
IS11
IS12
IS13
}
Loading

File-Level Changes

ChangeDetailsFiles
Extend FeatureSet enum to include IS09–IS13
  • Added new enum members IS09, IS10, IS11, IS12, IS13
  • Inserted corresponding Sphinx documentation links
  • Updated enum value mappings to point at is09-13 paths
opensmile/core/define.py
Include is09-13 configs in packaged data
  • Added "config/is09-13/*" to setup.py package_data
setup.py
Add IS09–IS13 configuration files
  • Imported and adapted official openSMILE configs for IS09 (emotion), IS10 (paraling), IS11 (speaker state), IS12 (speaker trait), IS13 (ComParE)
  • Replaced internal source/sink components with external placeholders
  • Organized configs into .conf and .inc files under opensmile/core/config/is09-13
opensmile/core/config/is09-13/*

Possibly linked issues

  • WIP: Init #1: The PR adds IS10_paraling config with external source/sink, directly addressing the issue's request and error.

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-aisourcery-aiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @ATriantafyllopoulos - I've reviewed your changes - here's some feedback:

  • Consider splitting this large PR into smaller, logical commits (e.g. enum updates, setup changes, then each feature‐set config) to make the review more manageable.
  • There’s substantial repetition across the new config files; extract shared headers and repeated component definitions into common include files to reduce duplication and simplify future maintenance.
  • In setup.py, ensure the 'config/is09-13/' glob recursively captures all nested directories and files (or switch to a '**/' pattern) so no configs are accidentally omitted.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments- Consider splitting this large PR into smaller, logical commits (e.g. enum updates, setup changes, then each feature‐set config) to make the review more manageable.
- There’s substantial repetition across the new config files; extract shared headers and repeated component definitions into common include files to reduce duplication and simplify future maintenance.
- In setup.py, ensure the 'config/is09-13/*' glob recursively captures all nested directories and files (or switch to a '**/*' pattern) so no configs are accidentally omitted.
## Individual Comments### Comment 1
<location> `opensmile/core/config/is09-13/IS12_speaker_trait_compat.conf:339` </location>
<code_context>
+instance[melspecMfcc].type=cMelspec
+instance[mfcc].type=cMfcc
+
+[melspecMfcc:cMelspec]
+reader.dmLevel=fftmagH25
+writer.dmLevel=melspecMfcc
+copyInputName = 1
+processArrayFields = 1
+; htk compatible sample value scaling
+htkcompatible = 1
+nBands = 26s
+; use power spectrum instead of magnitude spectrum
+usePower = 1
</code_context>
<issue_to_address>
Possible typo: 'nBands = 26s' contains an unexpected 's'.
Please check if 'nBands' should be set to an integer value, such as 26, instead of '26s'.
</issue_to_address>
<suggested_fix>
<<<<<<< SEARCH
nBands = 26s
=======
nBands = 26
>>>>>>> REPLACE
</suggested_fix>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment threadopensmile/core/config/is09-13/IS12_speaker_trait_compat.conf
@hagenw

Copy link
Copy Markdown
Member

@ATriantafyllopoulos what is the usecase for those configs?

/cc @ureichel@maxschmitt

@ATriantafyllopoulos

Copy link
Copy Markdown
ContributorAuthor

@ATriantafyllopoulos what is the usecase for those configs?

/cc @ureichel@maxschmitt

I want to finally make a paper I wrote for Interspeech last year fully reproducible..

Also, these are the standard config files used in the early versions of the ComParE challenge. If someone wants to reproduce these results with modern tools (Python), this will be useful

@codecov

codecovBot commented Jul 25, 2025

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.0%. Comparing base (9d7fd3d) to head (cf378dc).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
Files with missing linesCoverage Δ
opensmile/core/define.py100.0% <100.0%> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment threadopensmile/core/define.py
@hagenw

Copy link
Copy Markdown
Member

codespell is currently failing with

image

An easy fix would be to add the whole config folder to the skip entry in the [tool.codespell] section in pyproject.toml:

# ----- codespell ---------------------------------------------------------
[tool.codespell]
builtin = 'clear,rare,informal,usage,names'skip = './opensmile.egg-info,./build,./docs/api,./docs/_templates,./docs/examples','opensmile/core/config'

@hagenw

Copy link
Copy Markdown
Member

For the other linter fix you need to run ruff or pre-commit locally, see https://audeering.github.io/opensmile-python/contributing.html#coding-convention

@ATriantafyllopoulos

Copy link
Copy Markdown
ContributorAuthor

An easy fix would be to add the whole config folder to the skip entry in the [tool.codespell] section in pyproject.toml:

# ----- codespell ---------------------------------------------------------
[tool.codespell]
builtin = 'clear,rare,informal,usage,names'skip = './opensmile.egg-info,./build,./docs/api,./docs/_templates,./docs/examples','opensmile/core/config'

cf378dc (the syntax for the fix was a bit different but I followed your recommendation)

@hagenw

Copy link
Copy Markdown
Member

Great, thanks for fixing the tests, I will merge this now and prepare a new release.

@hagenw
hagenw merged commit 4074ec2 into audeering:mainJul 31, 2025
19 checks passed
@hagenw

Copy link
Copy Markdown
Member

Maybe the README is still slightly misleading:

image

But doesn't matter, I released version 2.6.0, so you should now be able to use your configs by installing this package.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@ATriantafyllopoulos@hagenw
, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Added is09-13 configs - #124

Merged
hagenw merged 3 commits into
audeering:mainfrom
ATriantafyllopoulos:is09-13
Jul 31, 2025
Merged

Added is09-13 configs#124
hagenw merged 3 commits into
audeering:mainfrom
ATriantafyllopoulos:is09-13

Conversation

@ATriantafyllopoulos

@ATriantafyllopoulosATriantafyllopoulos commented Jul 15, 2025

Copy link
Copy Markdown
Contributor

This PR adds standard config files for the IS09-13 feature sets. The config files are all taken from the original repo with the only change being the use of external source and sink components for reading/writing.

Summary by Sourcery

Add standardized openSMILE config files for the IS09-13 feature sets, update the FeatureSet enum to include IS09--IS13, and include the new configs in the package distribution.

New Features:

  • Add FeatureSet enum entries for IS09 through IS13 with doc links and config paths
  • Provide openSMILE configuration files for IS09 emotion, IS10 paralinguistics (compatibility and core), IS11 speaker state, IS12 speaker trait compatibility, and IS13 ComParE (core, functionals, vocalist)

Enhancements:

  • Use external source and sink components across all new configs

Build:

  • Include config/is09-13 directory in package data

@sourcery-ai

sourcery-aiBot commented Jul 15, 2025

Copy link
Copy Markdown
Contributor

Reviewer's Guide

This PR integrates support for the IS09–IS13 openSMILE feature sets by registering new FeatureSet values, packaging a new config directory, and importing the standard config files (adapted to external I/O) under opensmile/core/config/is09-13.

ER diagram for FeatureSet and config files

erDiagram
FEATURESET ||--o{ CONFIG_FILE : uses
FEATURESET {
string name
string config_path
}
CONFIG_FILE {
string filename
string path
}
Loading

Class diagram for updated FeatureSet enum

classDiagram
class FeatureSet {
<<enum>>
ComParE_2016
GeMAPS
eGeMAPS
emobase
IS09
IS10
IS11
IS12
IS13
}
Loading

File-Level Changes

ChangeDetailsFiles
Extend FeatureSet enum to include IS09–IS13
  • Added new enum members IS09, IS10, IS11, IS12, IS13
  • Inserted corresponding Sphinx documentation links
  • Updated enum value mappings to point at is09-13 paths
opensmile/core/define.py
Include is09-13 configs in packaged data
  • Added "config/is09-13/*" to setup.py package_data
setup.py
Add IS09–IS13 configuration files
  • Imported and adapted official openSMILE configs for IS09 (emotion), IS10 (paraling), IS11 (speaker state), IS12 (speaker trait), IS13 (ComParE)
  • Replaced internal source/sink components with external placeholders
  • Organized configs into .conf and .inc files under opensmile/core/config/is09-13
opensmile/core/config/is09-13/*

Possibly linked issues

  • WIP: Init #1: The PR adds IS10_paraling config with external source/sink, directly addressing the issue's request and error.

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-aisourcery-aiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @ATriantafyllopoulos - I've reviewed your changes - here's some feedback:

  • Consider splitting this large PR into smaller, logical commits (e.g. enum updates, setup changes, then each feature‐set config) to make the review more manageable.
  • There’s substantial repetition across the new config files; extract shared headers and repeated component definitions into common include files to reduce duplication and simplify future maintenance.
  • In setup.py, ensure the 'config/is09-13/' glob recursively captures all nested directories and files (or switch to a '**/' pattern) so no configs are accidentally omitted.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments- Consider splitting this large PR into smaller, logical commits (e.g. enum updates, setup changes, then each feature‐set config) to make the review more manageable.
- There’s substantial repetition across the new config files; extract shared headers and repeated component definitions into common include files to reduce duplication and simplify future maintenance.
- In setup.py, ensure the 'config/is09-13/*' glob recursively captures all nested directories and files (or switch to a '**/*' pattern) so no configs are accidentally omitted.
## Individual Comments### Comment 1
<location> `opensmile/core/config/is09-13/IS12_speaker_trait_compat.conf:339` </location>
<code_context>
+instance[melspecMfcc].type=cMelspec
+instance[mfcc].type=cMfcc
+
+[melspecMfcc:cMelspec]
+reader.dmLevel=fftmagH25
+writer.dmLevel=melspecMfcc
+copyInputName = 1
+processArrayFields = 1
+; htk compatible sample value scaling
+htkcompatible = 1
+nBands = 26s
+; use power spectrum instead of magnitude spectrum
+usePower = 1
</code_context>
<issue_to_address>
Possible typo: 'nBands = 26s' contains an unexpected 's'.
Please check if 'nBands' should be set to an integer value, such as 26, instead of '26s'.
</issue_to_address>
<suggested_fix>
<<<<<<< SEARCH
nBands = 26s
=======
nBands = 26
>>>>>>> REPLACE
</suggested_fix>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment threadopensmile/core/config/is09-13/IS12_speaker_trait_compat.conf
@hagenw

Copy link
Copy Markdown
Member

@ATriantafyllopoulos what is the usecase for those configs?

/cc @ureichel@maxschmitt

@ATriantafyllopoulos

Copy link
Copy Markdown
ContributorAuthor

@ATriantafyllopoulos what is the usecase for those configs?

/cc @ureichel@maxschmitt

I want to finally make a paper I wrote for Interspeech last year fully reproducible..

Also, these are the standard config files used in the early versions of the ComParE challenge. If someone wants to reproduce these results with modern tools (Python), this will be useful

@codecov

codecovBot commented Jul 25, 2025

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.0%. Comparing base (9d7fd3d) to head (cf378dc).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
Files with missing linesCoverage Δ
opensmile/core/define.py100.0% <100.0%> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment threadopensmile/core/define.py
@hagenw

Copy link
Copy Markdown
Member

codespell is currently failing with

image

An easy fix would be to add the whole config folder to the skip entry in the [tool.codespell] section in pyproject.toml:

# ----- codespell ---------------------------------------------------------
[tool.codespell]
builtin = 'clear,rare,informal,usage,names'skip = './opensmile.egg-info,./build,./docs/api,./docs/_templates,./docs/examples','opensmile/core/config'

@hagenw

Copy link
Copy Markdown
Member

For the other linter fix you need to run ruff or pre-commit locally, see https://audeering.github.io/opensmile-python/contributing.html#coding-convention

@ATriantafyllopoulos

Copy link
Copy Markdown
ContributorAuthor

An easy fix would be to add the whole config folder to the skip entry in the [tool.codespell] section in pyproject.toml:

# ----- codespell ---------------------------------------------------------
[tool.codespell]
builtin = 'clear,rare,informal,usage,names'skip = './opensmile.egg-info,./build,./docs/api,./docs/_templates,./docs/examples','opensmile/core/config'

cf378dc (the syntax for the fix was a bit different but I followed your recommendation)

@hagenw

Copy link
Copy Markdown
Member

Great, thanks for fixing the tests, I will merge this now and prepare a new release.

@hagenw
hagenw merged commit 4074ec2 into audeering:mainJul 31, 2025
19 checks passed
@hagenw

Copy link
Copy Markdown
Member

Maybe the README is still slightly misleading:

image

But doesn't matter, I released version 2.6.0, so you should now be able to use your configs by installing this package.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@ATriantafyllopoulos@hagenw
, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

Added is09-13 configs - #124

Merged
hagenw merged 3 commits into
audeering:mainfrom
ATriantafyllopoulos:is09-13
Jul 31, 2025
Merged

Added is09-13 configs#124
hagenw merged 3 commits into
audeering:mainfrom
ATriantafyllopoulos:is09-13

Conversation

@ATriantafyllopoulos

@ATriantafyllopoulosATriantafyllopoulos commented Jul 15, 2025

Copy link
Copy Markdown
Contributor

This PR adds standard config files for the IS09-13 feature sets. The config files are all taken from the original repo with the only change being the use of external source and sink components for reading/writing.

Summary by Sourcery

Add standardized openSMILE config files for the IS09-13 feature sets, update the FeatureSet enum to include IS09--IS13, and include the new configs in the package distribution.

New Features:

  • Add FeatureSet enum entries for IS09 through IS13 with doc links and config paths
  • Provide openSMILE configuration files for IS09 emotion, IS10 paralinguistics (compatibility and core), IS11 speaker state, IS12 speaker trait compatibility, and IS13 ComParE (core, functionals, vocalist)

Enhancements:

  • Use external source and sink components across all new configs

Build:

  • Include config/is09-13 directory in package data

@sourcery-ai

sourcery-aiBot commented Jul 15, 2025

Copy link
Copy Markdown
Contributor

Reviewer's Guide

This PR integrates support for the IS09–IS13 openSMILE feature sets by registering new FeatureSet values, packaging a new config directory, and importing the standard config files (adapted to external I/O) under opensmile/core/config/is09-13.

ER diagram for FeatureSet and config files

erDiagram
FEATURESET ||--o{ CONFIG_FILE : uses
FEATURESET {
string name
string config_path
}
CONFIG_FILE {
string filename
string path
}
Loading

Class diagram for updated FeatureSet enum

classDiagram
class FeatureSet {
<<enum>>
ComParE_2016
GeMAPS
eGeMAPS
emobase
IS09
IS10
IS11
IS12
IS13
}
Loading

File-Level Changes

ChangeDetailsFiles
Extend FeatureSet enum to include IS09–IS13
  • Added new enum members IS09, IS10, IS11, IS12, IS13
  • Inserted corresponding Sphinx documentation links
  • Updated enum value mappings to point at is09-13 paths
opensmile/core/define.py
Include is09-13 configs in packaged data
  • Added "config/is09-13/*" to setup.py package_data
setup.py
Add IS09–IS13 configuration files
  • Imported and adapted official openSMILE configs for IS09 (emotion), IS10 (paraling), IS11 (speaker state), IS12 (speaker trait), IS13 (ComParE)
  • Replaced internal source/sink components with external placeholders
  • Organized configs into .conf and .inc files under opensmile/core/config/is09-13
opensmile/core/config/is09-13/*

Possibly linked issues

  • WIP: Init #1: The PR adds IS10_paraling config with external source/sink, directly addressing the issue's request and error.

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-aisourcery-aiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @ATriantafyllopoulos - I've reviewed your changes - here's some feedback:

  • Consider splitting this large PR into smaller, logical commits (e.g. enum updates, setup changes, then each feature‐set config) to make the review more manageable.
  • There’s substantial repetition across the new config files; extract shared headers and repeated component definitions into common include files to reduce duplication and simplify future maintenance.
  • In setup.py, ensure the 'config/is09-13/' glob recursively captures all nested directories and files (or switch to a '**/' pattern) so no configs are accidentally omitted.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments- Consider splitting this large PR into smaller, logical commits (e.g. enum updates, setup changes, then each feature‐set config) to make the review more manageable.
- There’s substantial repetition across the new config files; extract shared headers and repeated component definitions into common include files to reduce duplication and simplify future maintenance.
- In setup.py, ensure the 'config/is09-13/*' glob recursively captures all nested directories and files (or switch to a '**/*' pattern) so no configs are accidentally omitted.
## Individual Comments### Comment 1
<location> `opensmile/core/config/is09-13/IS12_speaker_trait_compat.conf:339` </location>
<code_context>
+instance[melspecMfcc].type=cMelspec
+instance[mfcc].type=cMfcc
+
+[melspecMfcc:cMelspec]
+reader.dmLevel=fftmagH25
+writer.dmLevel=melspecMfcc
+copyInputName = 1
+processArrayFields = 1
+; htk compatible sample value scaling
+htkcompatible = 1
+nBands = 26s
+; use power spectrum instead of magnitude spectrum
+usePower = 1
</code_context>
<issue_to_address>
Possible typo: 'nBands = 26s' contains an unexpected 's'.
Please check if 'nBands' should be set to an integer value, such as 26, instead of '26s'.
</issue_to_address>
<suggested_fix>
<<<<<<< SEARCH
nBands = 26s
=======
nBands = 26
>>>>>>> REPLACE
</suggested_fix>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment threadopensmile/core/config/is09-13/IS12_speaker_trait_compat.conf
@hagenw

Copy link
Copy Markdown
Member

@ATriantafyllopoulos what is the usecase for those configs?

/cc @ureichel@maxschmitt

@ATriantafyllopoulos

Copy link
Copy Markdown
ContributorAuthor

@ATriantafyllopoulos what is the usecase for those configs?

/cc @ureichel@maxschmitt

I want to finally make a paper I wrote for Interspeech last year fully reproducible..

Also, these are the standard config files used in the early versions of the ComParE challenge. If someone wants to reproduce these results with modern tools (Python), this will be useful

@codecov

codecovBot commented Jul 25, 2025

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.0%. Comparing base (9d7fd3d) to head (cf378dc).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
Files with missing linesCoverage Δ
opensmile/core/define.py100.0% <100.0%> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment threadopensmile/core/define.py
@hagenw

Copy link
Copy Markdown
Member

codespell is currently failing with

image

An easy fix would be to add the whole config folder to the skip entry in the [tool.codespell] section in pyproject.toml:

# ----- codespell ---------------------------------------------------------
[tool.codespell]
builtin = 'clear,rare,informal,usage,names'skip = './opensmile.egg-info,./build,./docs/api,./docs/_templates,./docs/examples','opensmile/core/config'

@hagenw

Copy link
Copy Markdown
Member

For the other linter fix you need to run ruff or pre-commit locally, see https://audeering.github.io/opensmile-python/contributing.html#coding-convention

@ATriantafyllopoulos

Copy link
Copy Markdown
ContributorAuthor

An easy fix would be to add the whole config folder to the skip entry in the [tool.codespell] section in pyproject.toml:

# ----- codespell ---------------------------------------------------------
[tool.codespell]
builtin = 'clear,rare,informal,usage,names'skip = './opensmile.egg-info,./build,./docs/api,./docs/_templates,./docs/examples','opensmile/core/config'

cf378dc (the syntax for the fix was a bit different but I followed your recommendation)

@hagenw

Copy link
Copy Markdown
Member

Great, thanks for fixing the tests, I will merge this now and prepare a new release.

@hagenw
hagenw merged commit 4074ec2 into audeering:mainJul 31, 2025
19 checks passed
@hagenw

Copy link
Copy Markdown
Member

Maybe the README is still slightly misleading:

image

But doesn't matter, I released version 2.6.0, so you should now be able to use your configs by installing this package.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@ATriantafyllopoulos@hagenw
, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Added is09-13 configs - #124

Merged
hagenw merged 3 commits into
audeering:mainfrom
ATriantafyllopoulos:is09-13
Jul 31, 2025
Merged

Added is09-13 configs#124
hagenw merged 3 commits into
audeering:mainfrom
ATriantafyllopoulos:is09-13

Conversation

@ATriantafyllopoulos

@ATriantafyllopoulosATriantafyllopoulos commented Jul 15, 2025

Copy link
Copy Markdown
Contributor

This PR adds standard config files for the IS09-13 feature sets. The config files are all taken from the original repo with the only change being the use of external source and sink components for reading/writing.

Summary by Sourcery

Add standardized openSMILE config files for the IS09-13 feature sets, update the FeatureSet enum to include IS09--IS13, and include the new configs in the package distribution.

New Features:

  • Add FeatureSet enum entries for IS09 through IS13 with doc links and config paths
  • Provide openSMILE configuration files for IS09 emotion, IS10 paralinguistics (compatibility and core), IS11 speaker state, IS12 speaker trait compatibility, and IS13 ComParE (core, functionals, vocalist)

Enhancements:

  • Use external source and sink components across all new configs

Build:

  • Include config/is09-13 directory in package data

@sourcery-ai

sourcery-aiBot commented Jul 15, 2025

Copy link
Copy Markdown
Contributor

Reviewer's Guide

This PR integrates support for the IS09–IS13 openSMILE feature sets by registering new FeatureSet values, packaging a new config directory, and importing the standard config files (adapted to external I/O) under opensmile/core/config/is09-13.

ER diagram for FeatureSet and config files

erDiagram
FEATURESET ||--o{ CONFIG_FILE : uses
FEATURESET {
string name
string config_path
}
CONFIG_FILE {
string filename
string path
}
Loading

Class diagram for updated FeatureSet enum

classDiagram
class FeatureSet {
<<enum>>
ComParE_2016
GeMAPS
eGeMAPS
emobase
IS09
IS10
IS11
IS12
IS13
}
Loading

File-Level Changes

ChangeDetailsFiles
Extend FeatureSet enum to include IS09–IS13
  • Added new enum members IS09, IS10, IS11, IS12, IS13
  • Inserted corresponding Sphinx documentation links
  • Updated enum value mappings to point at is09-13 paths
opensmile/core/define.py
Include is09-13 configs in packaged data
  • Added "config/is09-13/*" to setup.py package_data
setup.py
Add IS09–IS13 configuration files
  • Imported and adapted official openSMILE configs for IS09 (emotion), IS10 (paraling), IS11 (speaker state), IS12 (speaker trait), IS13 (ComParE)
  • Replaced internal source/sink components with external placeholders
  • Organized configs into .conf and .inc files under opensmile/core/config/is09-13
opensmile/core/config/is09-13/*

Possibly linked issues

  • WIP: Init #1: The PR adds IS10_paraling config with external source/sink, directly addressing the issue's request and error.

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-aisourcery-aiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @ATriantafyllopoulos - I've reviewed your changes - here's some feedback:

  • Consider splitting this large PR into smaller, logical commits (e.g. enum updates, setup changes, then each feature‐set config) to make the review more manageable.
  • There’s substantial repetition across the new config files; extract shared headers and repeated component definitions into common include files to reduce duplication and simplify future maintenance.
  • In setup.py, ensure the 'config/is09-13/' glob recursively captures all nested directories and files (or switch to a '**/' pattern) so no configs are accidentally omitted.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments- Consider splitting this large PR into smaller, logical commits (e.g. enum updates, setup changes, then each feature‐set config) to make the review more manageable.
- There’s substantial repetition across the new config files; extract shared headers and repeated component definitions into common include files to reduce duplication and simplify future maintenance.
- In setup.py, ensure the 'config/is09-13/*' glob recursively captures all nested directories and files (or switch to a '**/*' pattern) so no configs are accidentally omitted.
## Individual Comments### Comment 1
<location> `opensmile/core/config/is09-13/IS12_speaker_trait_compat.conf:339` </location>
<code_context>
+instance[melspecMfcc].type=cMelspec
+instance[mfcc].type=cMfcc
+
+[melspecMfcc:cMelspec]
+reader.dmLevel=fftmagH25
+writer.dmLevel=melspecMfcc
+copyInputName = 1
+processArrayFields = 1
+; htk compatible sample value scaling
+htkcompatible = 1
+nBands = 26s
+; use power spectrum instead of magnitude spectrum
+usePower = 1
</code_context>
<issue_to_address>
Possible typo: 'nBands = 26s' contains an unexpected 's'.
Please check if 'nBands' should be set to an integer value, such as 26, instead of '26s'.
</issue_to_address>
<suggested_fix>
<<<<<<< SEARCH
nBands = 26s
=======
nBands = 26
>>>>>>> REPLACE
</suggested_fix>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment threadopensmile/core/config/is09-13/IS12_speaker_trait_compat.conf
@hagenw

Copy link
Copy Markdown
Member

@ATriantafyllopoulos what is the usecase for those configs?

/cc @ureichel@maxschmitt

@ATriantafyllopoulos

Copy link
Copy Markdown
ContributorAuthor

@ATriantafyllopoulos what is the usecase for those configs?

/cc @ureichel@maxschmitt

I want to finally make a paper I wrote for Interspeech last year fully reproducible..

Also, these are the standard config files used in the early versions of the ComParE challenge. If someone wants to reproduce these results with modern tools (Python), this will be useful

@codecov

codecovBot commented Jul 25, 2025

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.0%. Comparing base (9d7fd3d) to head (cf378dc).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
Files with missing linesCoverage Δ
opensmile/core/define.py100.0% <100.0%> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment threadopensmile/core/define.py
@hagenw

Copy link
Copy Markdown
Member

codespell is currently failing with

image

An easy fix would be to add the whole config folder to the skip entry in the [tool.codespell] section in pyproject.toml:

# ----- codespell ---------------------------------------------------------
[tool.codespell]
builtin = 'clear,rare,informal,usage,names'skip = './opensmile.egg-info,./build,./docs/api,./docs/_templates,./docs/examples','opensmile/core/config'

@hagenw

Copy link
Copy Markdown
Member

For the other linter fix you need to run ruff or pre-commit locally, see https://audeering.github.io/opensmile-python/contributing.html#coding-convention

@ATriantafyllopoulos

Copy link
Copy Markdown
ContributorAuthor

An easy fix would be to add the whole config folder to the skip entry in the [tool.codespell] section in pyproject.toml:

# ----- codespell ---------------------------------------------------------
[tool.codespell]
builtin = 'clear,rare,informal,usage,names'skip = './opensmile.egg-info,./build,./docs/api,./docs/_templates,./docs/examples','opensmile/core/config'

cf378dc (the syntax for the fix was a bit different but I followed your recommendation)

@hagenw

Copy link
Copy Markdown
Member

Great, thanks for fixing the tests, I will merge this now and prepare a new release.

@hagenw
hagenw merged commit 4074ec2 into audeering:mainJul 31, 2025
19 checks passed
@hagenw

Copy link
Copy Markdown
Member

Maybe the README is still slightly misleading:

image

But doesn't matter, I released version 2.6.0, so you should now be able to use your configs by installing this package.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@ATriantafyllopoulos@hagenw
, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Added is09-13 configs - #124

Merged
hagenw merged 3 commits into
audeering:mainfrom
ATriantafyllopoulos:is09-13
Jul 31, 2025
Merged

Added is09-13 configs#124
hagenw merged 3 commits into
audeering:mainfrom
ATriantafyllopoulos:is09-13

Conversation

@ATriantafyllopoulos

@ATriantafyllopoulosATriantafyllopoulos commented Jul 15, 2025

Copy link
Copy Markdown
Contributor

This PR adds standard config files for the IS09-13 feature sets. The config files are all taken from the original repo with the only change being the use of external source and sink components for reading/writing.

Summary by Sourcery

Add standardized openSMILE config files for the IS09-13 feature sets, update the FeatureSet enum to include IS09--IS13, and include the new configs in the package distribution.

New Features:

  • Add FeatureSet enum entries for IS09 through IS13 with doc links and config paths
  • Provide openSMILE configuration files for IS09 emotion, IS10 paralinguistics (compatibility and core), IS11 speaker state, IS12 speaker trait compatibility, and IS13 ComParE (core, functionals, vocalist)

Enhancements:

  • Use external source and sink components across all new configs

Build:

  • Include config/is09-13 directory in package data

@sourcery-ai

sourcery-aiBot commented Jul 15, 2025

Copy link
Copy Markdown
Contributor

Reviewer's Guide

This PR integrates support for the IS09–IS13 openSMILE feature sets by registering new FeatureSet values, packaging a new config directory, and importing the standard config files (adapted to external I/O) under opensmile/core/config/is09-13.

ER diagram for FeatureSet and config files

erDiagram
FEATURESET ||--o{ CONFIG_FILE : uses
FEATURESET {
string name
string config_path
}
CONFIG_FILE {
string filename
string path
}
Loading

Class diagram for updated FeatureSet enum

classDiagram
class FeatureSet {
<<enum>>
ComParE_2016
GeMAPS
eGeMAPS
emobase
IS09
IS10
IS11
IS12
IS13
}
Loading

File-Level Changes

ChangeDetailsFiles
Extend FeatureSet enum to include IS09–IS13
  • Added new enum members IS09, IS10, IS11, IS12, IS13
  • Inserted corresponding Sphinx documentation links
  • Updated enum value mappings to point at is09-13 paths
opensmile/core/define.py
Include is09-13 configs in packaged data
  • Added "config/is09-13/*" to setup.py package_data
setup.py
Add IS09–IS13 configuration files
  • Imported and adapted official openSMILE configs for IS09 (emotion), IS10 (paraling), IS11 (speaker state), IS12 (speaker trait), IS13 (ComParE)
  • Replaced internal source/sink components with external placeholders
  • Organized configs into .conf and .inc files under opensmile/core/config/is09-13
opensmile/core/config/is09-13/*

Possibly linked issues

  • WIP: Init #1: The PR adds IS10_paraling config with external source/sink, directly addressing the issue's request and error.

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-aisourcery-aiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @ATriantafyllopoulos - I've reviewed your changes - here's some feedback:

  • Consider splitting this large PR into smaller, logical commits (e.g. enum updates, setup changes, then each feature‐set config) to make the review more manageable.
  • There’s substantial repetition across the new config files; extract shared headers and repeated component definitions into common include files to reduce duplication and simplify future maintenance.
  • In setup.py, ensure the 'config/is09-13/' glob recursively captures all nested directories and files (or switch to a '**/' pattern) so no configs are accidentally omitted.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments- Consider splitting this large PR into smaller, logical commits (e.g. enum updates, setup changes, then each feature‐set config) to make the review more manageable.
- There’s substantial repetition across the new config files; extract shared headers and repeated component definitions into common include files to reduce duplication and simplify future maintenance.
- In setup.py, ensure the 'config/is09-13/*' glob recursively captures all nested directories and files (or switch to a '**/*' pattern) so no configs are accidentally omitted.
## Individual Comments### Comment 1
<location> `opensmile/core/config/is09-13/IS12_speaker_trait_compat.conf:339` </location>
<code_context>
+instance[melspecMfcc].type=cMelspec
+instance[mfcc].type=cMfcc
+
+[melspecMfcc:cMelspec]
+reader.dmLevel=fftmagH25
+writer.dmLevel=melspecMfcc
+copyInputName = 1
+processArrayFields = 1
+; htk compatible sample value scaling
+htkcompatible = 1
+nBands = 26s
+; use power spectrum instead of magnitude spectrum
+usePower = 1
</code_context>
<issue_to_address>
Possible typo: 'nBands = 26s' contains an unexpected 's'.
Please check if 'nBands' should be set to an integer value, such as 26, instead of '26s'.
</issue_to_address>
<suggested_fix>
<<<<<<< SEARCH
nBands = 26s
=======
nBands = 26
>>>>>>> REPLACE
</suggested_fix>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment threadopensmile/core/config/is09-13/IS12_speaker_trait_compat.conf
@hagenw

Copy link
Copy Markdown
Member

@ATriantafyllopoulos what is the usecase for those configs?

/cc @ureichel@maxschmitt

@ATriantafyllopoulos

Copy link
Copy Markdown
ContributorAuthor

@ATriantafyllopoulos what is the usecase for those configs?

/cc @ureichel@maxschmitt

I want to finally make a paper I wrote for Interspeech last year fully reproducible..

Also, these are the standard config files used in the early versions of the ComParE challenge. If someone wants to reproduce these results with modern tools (Python), this will be useful

@codecov

codecovBot commented Jul 25, 2025

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.0%. Comparing base (9d7fd3d) to head (cf378dc).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
Files with missing linesCoverage Δ
opensmile/core/define.py100.0% <100.0%> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment threadopensmile/core/define.py
@hagenw

Copy link
Copy Markdown
Member

codespell is currently failing with

image

An easy fix would be to add the whole config folder to the skip entry in the [tool.codespell] section in pyproject.toml:

# ----- codespell ---------------------------------------------------------
[tool.codespell]
builtin = 'clear,rare,informal,usage,names'skip = './opensmile.egg-info,./build,./docs/api,./docs/_templates,./docs/examples','opensmile/core/config'

@hagenw

Copy link
Copy Markdown
Member

For the other linter fix you need to run ruff or pre-commit locally, see https://audeering.github.io/opensmile-python/contributing.html#coding-convention

@ATriantafyllopoulos

Copy link
Copy Markdown
ContributorAuthor

An easy fix would be to add the whole config folder to the skip entry in the [tool.codespell] section in pyproject.toml:

# ----- codespell ---------------------------------------------------------
[tool.codespell]
builtin = 'clear,rare,informal,usage,names'skip = './opensmile.egg-info,./build,./docs/api,./docs/_templates,./docs/examples','opensmile/core/config'

cf378dc (the syntax for the fix was a bit different but I followed your recommendation)

@hagenw

Copy link
Copy Markdown
Member

Great, thanks for fixing the tests, I will merge this now and prepare a new release.

@hagenw
hagenw merged commit 4074ec2 into audeering:mainJul 31, 2025
19 checks passed
@hagenw

Copy link
Copy Markdown
Member

Maybe the README is still slightly misleading:

image

But doesn't matter, I released version 2.6.0, so you should now be able to use your configs by installing this package.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@ATriantafyllopoulos@hagenw
, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

Added is09-13 configs - #124

Merged
hagenw merged 3 commits into
audeering:mainfrom
ATriantafyllopoulos:is09-13
Jul 31, 2025
Merged

Added is09-13 configs#124
hagenw merged 3 commits into
audeering:mainfrom
ATriantafyllopoulos:is09-13

Conversation

@ATriantafyllopoulos

@ATriantafyllopoulosATriantafyllopoulos commented Jul 15, 2025

Copy link
Copy Markdown
Contributor

This PR adds standard config files for the IS09-13 feature sets. The config files are all taken from the original repo with the only change being the use of external source and sink components for reading/writing.

Summary by Sourcery

Add standardized openSMILE config files for the IS09-13 feature sets, update the FeatureSet enum to include IS09--IS13, and include the new configs in the package distribution.

New Features:

  • Add FeatureSet enum entries for IS09 through IS13 with doc links and config paths
  • Provide openSMILE configuration files for IS09 emotion, IS10 paralinguistics (compatibility and core), IS11 speaker state, IS12 speaker trait compatibility, and IS13 ComParE (core, functionals, vocalist)

Enhancements:

  • Use external source and sink components across all new configs

Build:

  • Include config/is09-13 directory in package data

@sourcery-ai

sourcery-aiBot commented Jul 15, 2025

Copy link
Copy Markdown
Contributor

Reviewer's Guide

This PR integrates support for the IS09–IS13 openSMILE feature sets by registering new FeatureSet values, packaging a new config directory, and importing the standard config files (adapted to external I/O) under opensmile/core/config/is09-13.

ER diagram for FeatureSet and config files

erDiagram
FEATURESET ||--o{ CONFIG_FILE : uses
FEATURESET {
string name
string config_path
}
CONFIG_FILE {
string filename
string path
}
Loading

Class diagram for updated FeatureSet enum

classDiagram
class FeatureSet {
<<enum>>
ComParE_2016
GeMAPS
eGeMAPS
emobase
IS09
IS10
IS11
IS12
IS13
}
Loading

File-Level Changes

ChangeDetailsFiles
Extend FeatureSet enum to include IS09–IS13
  • Added new enum members IS09, IS10, IS11, IS12, IS13
  • Inserted corresponding Sphinx documentation links
  • Updated enum value mappings to point at is09-13 paths
opensmile/core/define.py
Include is09-13 configs in packaged data
  • Added "config/is09-13/*" to setup.py package_data
setup.py
Add IS09–IS13 configuration files
  • Imported and adapted official openSMILE configs for IS09 (emotion), IS10 (paraling), IS11 (speaker state), IS12 (speaker trait), IS13 (ComParE)
  • Replaced internal source/sink components with external placeholders
  • Organized configs into .conf and .inc files under opensmile/core/config/is09-13
opensmile/core/config/is09-13/*

Possibly linked issues

  • WIP: Init #1: The PR adds IS10_paraling config with external source/sink, directly addressing the issue's request and error.

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-aisourcery-aiBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @ATriantafyllopoulos - I've reviewed your changes - here's some feedback:

  • Consider splitting this large PR into smaller, logical commits (e.g. enum updates, setup changes, then each feature‐set config) to make the review more manageable.
  • There’s substantial repetition across the new config files; extract shared headers and repeated component definitions into common include files to reduce duplication and simplify future maintenance.
  • In setup.py, ensure the 'config/is09-13/' glob recursively captures all nested directories and files (or switch to a '**/' pattern) so no configs are accidentally omitted.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments- Consider splitting this large PR into smaller, logical commits (e.g. enum updates, setup changes, then each feature‐set config) to make the review more manageable.
- There’s substantial repetition across the new config files; extract shared headers and repeated component definitions into common include files to reduce duplication and simplify future maintenance.
- In setup.py, ensure the 'config/is09-13/*' glob recursively captures all nested directories and files (or switch to a '**/*' pattern) so no configs are accidentally omitted.
## Individual Comments### Comment 1
<location> `opensmile/core/config/is09-13/IS12_speaker_trait_compat.conf:339` </location>
<code_context>
+instance[melspecMfcc].type=cMelspec
+instance[mfcc].type=cMfcc
+
+[melspecMfcc:cMelspec]
+reader.dmLevel=fftmagH25
+writer.dmLevel=melspecMfcc
+copyInputName = 1
+processArrayFields = 1
+; htk compatible sample value scaling
+htkcompatible = 1
+nBands = 26s
+; use power spectrum instead of magnitude spectrum
+usePower = 1
</code_context>
<issue_to_address>
Possible typo: 'nBands = 26s' contains an unexpected 's'.
Please check if 'nBands' should be set to an integer value, such as 26, instead of '26s'.
</issue_to_address>
<suggested_fix>
<<<<<<< SEARCH
nBands = 26s
=======
nBands = 26
>>>>>>> REPLACE
</suggested_fix>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment threadopensmile/core/config/is09-13/IS12_speaker_trait_compat.conf
@hagenw

Copy link
Copy Markdown
Member

@ATriantafyllopoulos what is the usecase for those configs?

/cc @ureichel@maxschmitt

@ATriantafyllopoulos

Copy link
Copy Markdown
ContributorAuthor

@ATriantafyllopoulos what is the usecase for those configs?

/cc @ureichel@maxschmitt

I want to finally make a paper I wrote for Interspeech last year fully reproducible..

Also, these are the standard config files used in the early versions of the ComParE challenge. If someone wants to reproduce these results with modern tools (Python), this will be useful

@codecov

codecovBot commented Jul 25, 2025

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.0%. Comparing base (9d7fd3d) to head (cf378dc).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
Files with missing linesCoverage Δ
opensmile/core/define.py100.0% <100.0%> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment threadopensmile/core/define.py
@hagenw

Copy link
Copy Markdown
Member

codespell is currently failing with

image

An easy fix would be to add the whole config folder to the skip entry in the [tool.codespell] section in pyproject.toml:

# ----- codespell ---------------------------------------------------------
[tool.codespell]
builtin = 'clear,rare,informal,usage,names'skip = './opensmile.egg-info,./build,./docs/api,./docs/_templates,./docs/examples','opensmile/core/config'

@hagenw

Copy link
Copy Markdown
Member

For the other linter fix you need to run ruff or pre-commit locally, see https://audeering.github.io/opensmile-python/contributing.html#coding-convention

@ATriantafyllopoulos

Copy link
Copy Markdown
ContributorAuthor

An easy fix would be to add the whole config folder to the skip entry in the [tool.codespell] section in pyproject.toml:

# ----- codespell ---------------------------------------------------------
[tool.codespell]
builtin = 'clear,rare,informal,usage,names'skip = './opensmile.egg-info,./build,./docs/api,./docs/_templates,./docs/examples','opensmile/core/config'

cf378dc (the syntax for the fix was a bit different but I followed your recommendation)

@hagenw

Copy link
Copy Markdown
Member

Great, thanks for fixing the tests, I will merge this now and prepare a new release.

@hagenw
hagenw merged commit 4074ec2 into audeering:mainJul 31, 2025
19 checks passed
@hagenw

Copy link
Copy Markdown
Member

Maybe the README is still slightly misleading:

image

But doesn't matter, I released version 2.6.0, so you should now be able to use your configs by installing this package.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@ATriantafyllopoulos@hagenw