No such file or directory: 'ivector-plda-scoring' about fakebob

[GolferChen]

Could you run 'which ivector-plda-scoring' in your terminal and provide the output?
The possible reason is that you do not set up the environment properly so that the system cannot find it.
Did you follow the suggestion in step-6 in README ?

Step-6: Setting the System Variable which kaldi relies on. We have made it as simple as possible. You just need to copy and paste all the commands in path_cmd.sh to your ~/.zshrc or ~/.bashrc. Do not forget to modify KALDI_ROOT and FAKEBOB_PATH in path_cmd.sh

[GolferChen]

Notice: if your shell is bash, then you should paste the commands in path_cmd.sh to your ~/.bashrc, not ~/.zshrc, and source ~/.bashrc, not source ~/.zshrc.
Check the type of your shell by 'echo $0'

[woliyanyan]

It can be found and output in the terminal,

And set it according to the suggestions in step 6 of the readme。
But the problem remains unresolved

[FAKEBOB-adversarial-attack]

Quite weird...

Could you set debug = True in the line 36 of build_spk_models.py, re-run the file and provide the log?

[woliyanyan]

this is the running log after modifying debug = true

[FAKEBOB-adversarial-attack]

I see.
So the problem may be not due to ivector-plda-scoring since your program even fails at the step of mfcc extraction.

As the first red-colored line of the log indicates, the system cannot find parse_options.sh. This script is in pre-models/utils/ and path_cmd.sh in step-6 has appended it to the PATH environment variable.

Could you run which parse_options.sh and provide the output? This is my output.

[woliyanyan]

This is my output.

[FAKEBOB-adversarial-attack]

What is your shell type? Zsh?

[woliyanyan]

[FAKEBOB-adversarial-attack]

Quite confusing. Currently, I cannot figure out why the system can find all these files when you run which xx, but fail to find them when you run build_spk_models.py.

I will try to reproduce the manual installation from scratch on a new machine to see whether your problem is a common one.

Before that, I suggest you turn to docker installation. It will save you much effort.

[woliyanyan]

OK, thank you. Please!

[FAKEBOB-adversarial-attack]

Hi, I have reproduced the manual installation from scratch on a new machine (not the one I previously worked on). Everything went smoothly. The only exception is that I accidentally forgot to run source ~/.zshrc in step-6 and encountered the same problem as you. However, the problem was easily fixed after I executed source ~/.zshrc.

So did you strictly follow the instruction of manual installation (especially step-6)?