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

DISC compatibility for FAVE-extract #11

Open
scjs opened this issue Nov 23, 2013 · 5 comments
Open

DISC compatibility for FAVE-extract #11

scjs opened this issue Nov 23, 2013 · 5 comments
Labels
needs researched More information needed before coming up with an implementation plan

Comments

@scjs
Copy link
Contributor

scjs commented Nov 23, 2013

Update FAVE-extract for compatibility with DISC (CELEX) phonetic alphabets for use with non-North American dialects

@scjs
Copy link
Contributor Author

scjs commented Nov 30, 2013

Are there Plotnik codes for all of the DISC codes? FAVE has a few explicit references to ARPAbet, but one way to make it more compatible (and add other transcription systems down the line) might be to convert all of these to the Plotnik codes internally. DISC and ARPAbet both have codes that the other one doesn't unfortunately. @kylebgorman

@JoFrhwld
Copy link
Owner

JoFrhwld commented Dec 4, 2013

I think this could fall under a larger goal of mine to make FAVE operate over any arbitrary label set. The way I see this working is:

  1. Moving translation into plotnik codes out of FAVE-extract, and into a pre-processing procedure on the output of FAVE-align.
  2. Replace plotnik contextual coding with simply including segmental and lexical information in the FAVE output.
  3. Providing FAVE-extract with a list of vowel phones and measurement point heuristics.
  4. Providing FAVE with means and covariances for the specialized phone set.

Parts (1) and (2) should be easy enough, part (3) is probably going to be really difficult, and part (4) will require some investment on the part of the researcher at the start of their project, but shouldn't be so bad. The effect of the "priors" on the overall formant estimation process is relatively weak, so only about 5 or 10 measurements per vowel should really be necessary.

JoFrhwld pushed a commit that referenced this issue Jun 9, 2014
@chrisbrickhouse
Copy link
Collaborator

@JoFrhwld was this resolved in f5b7e70? If so this can be closed.

@JoFrhwld
Copy link
Owner

No, I think these were commits for windows compatibility. The heavy lifting for allowing DISC codes is spread across a few functions, but key among them is isVowel() which still references the global VOWELS variable.

@JoFrhwld
Copy link
Owner

Also, a ton of plotnik.py is implicated.

@chrisbrickhouse chrisbrickhouse added the needs researched More information needed before coming up with an implementation plan label Sep 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs researched More information needed before coming up with an implementation plan
Projects
None yet
Development

No branches or pull requests

3 participants