-
Notifications
You must be signed in to change notification settings - Fork 28
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
int decision=0; in ComputeNorm.cpp!! #28
Comments
Hi
That's true... It was designed for NIST evaluation where we used a scoring script to put the decision after all the processes (as we had usually several systems +fusion).
JF
De: "MSAlghamdi" <[email protected]>
À: "ALIZE-Speaker-Recognition" <[email protected]>
Cc: "Subscribed" <[email protected]>
Envoyé: Lundi 3 Décembre 2018 04:23:07
Objet: [ALIZE-Speaker-Recognition/LIA_RAL] int decision=0; in ComputeNorm.cpp!! (#28)
In ComputeNorm, decision=0 and never updated dynamically to a value that represent the result.
It's defined as zero variable and stays zero all the way till it's printed zero in the result.
How can we let it one for highest score and zero for the rest?!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, [ #28 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/ATmd7034FaLASQZzoYY-hv6ji_IBmaafks5u1JkbgaJpZM4Y9z0d | mute the thread ] .
…--
______________________________________________________________________
Jean-Francois BONASTRE
Directeur du LIA
LIA/CERI Université d'Avignon
Tel: +33/0 490843514
[email protected]
@jfbonastre
______________________________________________________________________
|
Could you please refer me to the scoring script you mentioned? |
not sure we still have it (me no) as it we updated it each year due to NIST-SRE file format changes.
Basically, it was reading the output file line by line and if the LLR was higher than the threshold put 1 in hte decision field, 0 if not...
Easy to reimplement that as an option in ComputeNorm if you need it (taking the example of ComputeTest which have this option)
De: "MSAlghamdi" <[email protected]>
À: "ALIZE-Speaker-Recognition" <[email protected]>
Cc: "Jean-Francois Bonastre" <[email protected]>, "Comment" <[email protected]>
Envoyé: Lundi 3 Décembre 2018 08:03:19
Objet: Re: [ALIZE-Speaker-Recognition/LIA_RAL] int decision=0; in ComputeNorm.cpp!! (#28)
Could you please refer me to the scoring script you mentioned?
—
You are receiving this because you commented.
Reply to this email directly, [ #28 (comment) | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/ATmd71LqeeVUGrrh55WUpPCW8vzZTcvBks5u1My3gaJpZM4Y9z0d | mute the thread ] .
…--
______________________________________________________________________
Jean-Francois BONASTRE
Directeur du LIA
LIA/CERI Université d'Avignon
Tel: +33/0 490843514
[email protected]
@jfbonastre
______________________________________________________________________
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In ComputeNorm, decision=0 and never updated dynamically to a value that represent the result.
It's defined as zero variable and stays zero all the way till it's printed zero in the result.
How can we let it one for highest score and zero for the rest?!
The text was updated successfully, but these errors were encountered: