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

Why the output line in csv file always have some badlines? #52

Open
jazlyn-Xv opened this issue Jul 18, 2022 · 1 comment
Open

Why the output line in csv file always have some badlines? #52

jazlyn-Xv opened this issue Jul 18, 2022 · 1 comment

Comments

@jazlyn-Xv
Copy link

When I use IS09_emotion.conf to extract fixed features from a large amount of wavs and save the output in a same csv file, some of the outputs is available, because when i want to read it with pd.read_csv, it always show some bad lines with warning 'Skipping line 725: expected 386 fields, saw 737\n',and the 737 can be 738\739...I guess it has put the results of two wavs in same line,and sometimes miss some values......

@chausner-audeering
Copy link
Contributor

If you run multiple SMILExtract instances in parallel, and they write concurrently to the same output file, the output will get corrupted as you described. You need to have each instance write in its own output file and afterwards concatenate them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants