Not getting prompted to download coreNLP (before deleting some large files)/Now can't parse after downloading coreNLP

[Subcomediante]

I'm just getting started with corpkit. I loaded my first corpus called "Chapters" and clicked on "Parse: Chapters." Nothing happens.

I'm attaching the log file.
log-00.txt

Also, perhaps this is related to my problem:
The Files listed in the GUI under "Files in subcorpus: "name of the selected subcorpus" are not the ones I put there or that can be found in the directory in the project in question. That is the case for one subcorpus. There are two. For the second one, no files are listed under "Files in the subcorpus: "name of the selected subcorpus." Even though there are several in the directory for the project in the "data" folder.

Thank you for the help.

[interrogator]

Hi,

Thanks for the report. Yeah, it seems from the log that there is some encoding issue, which causes an error before the CoreNLP download would start. I'll be able to take a look at this today.

Thanks!

[Subcomediante]

Thank you, Daniel, for looking into this. I'm excited to use corpkit. Best, Jeff

…

Sent from my iPhone

On Dec 29, 2016, at 04:36, Daniel ***@***.***> wrote: Hi, Thanks for the report. Yeah, it seems from the log that there is some encoding issue, which causes an error before the CoreNLP download would start. I'll be able to take a look at this today. Thanks! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[Subcomediante]

Hello --

Today I removed a few large files from each subcorpus, deleted the old project and reloaded the corpus. I was able to download successfully, it seems, coreNLP, responding positively to the prompt to do so after clicking on Parse button. However I'm not able to parse, it seems.

Attached is the new log file.

Thanks for the help,
Jeff
log-00.txt

[interrogator]

So yes, your first issue was caused by some code that splits up large files, which can help with parsing. I've fixed that bit of code in GitHub, but not yet on pypi/the .app.

Your second problem is related, also about file encoding. I can take a look soon, and will put up a fix.

[Subcomediante]

Thank you. I’m happy it wasn’t pilot error. I’ll standby to continue when second issue is behind you. Much appreciated, Jeff

…

On Jan 2, 2017, at 3:05 AM, Daniel ***@***.***> wrote: So yes, your first issue was caused by some code that splits up large files, which can help with parsing. I've fixed that bit of code in GitHub, but not yet on pypi/the .app. Your second problem is related, also about file encoding. I can take a look soon, and will put up a fix. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#46 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMeWq-vYwx3b50Nr2eSLRtCxPJtVmWzSks5rOK_UgaJpZM4LXLTV>.