-
Notifications
You must be signed in to change notification settings - Fork 2
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
Small fixes for generate_textcorpus script #566
Comments
One additional task:
|
Right now the progress bar is used if verbosity > 0, and logged statements are used if verbosity > 1. Does that sound like a good solution, and we just need to document it, or should we add a separate progressbar option? |
@rlskoeser what do you think ^here? |
It's possible we'll want to run this as a cron job, in which case we would definitely not want a progress bar but we might want some output to go to a log (not verbosity=0, which is I imagine what you meant?). The other option besides a separate flag would be detecting if it's not a terminal. I'm fine with whichever is easier. |
One requested change with the examples - the path used in the examples bypasses the default timestamped folder and introduced some user challenges for me with rsync (since I ran the script as conan but am connecting via rsync as pulsys.) Can there be documentation of the default path (with the default batch size, perhaps), and not use that argument in the examples? |
Hm, the default batch size is already documented, and I'm not sure it's worth putting in the examples because there seems to be no benefit (in fact it slows it down) to use a smaller or larger number than the default. I'll push a tiny PR for the path change |
Thank you! I merged the PR and declare this issue closed :D |
During testing we found a few issues related to the help text and options of the generate_textcorpus.py that would improve functionality and make the use clearer:
Help Text for generate_textcorpus
Explanation at the head of the script file
Additional functionality
The text was updated successfully, but these errors were encountered: