-
Notifications
You must be signed in to change notification settings - Fork 63
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
Run the pipeline synchronously? #49
Comments
Some pipelines simply can't do processing synchronously (e.g. weather would take over a day to process) but you can now run the pipelines within a chain one at a time by passing the
|
Thanks. I'm assuming that run.py is now called update.py? Also, I noticed that a previous version I'm using captures more epidemiology data than the most recent. I can say more once I understand more how the code works. Thank you. |
Yes, sorry for the change -- the project is currently under active development but I don't expect that
Can you please share a few data points (key + date) examples? |
@OmarJay1 did you get a chance to collect a few examples of datapoints which are missing from the previous version? |
I didn't get a chance to look closely, but the overall size was back to what it was before. Thanks. |
Hi, I've been stepping through the data acquisition code, and it's hard to do it when there are multiple processes running. Is there a way to make the processes run sequentially instead of asynchronously? I can comment stuff out and add break points, but if there's a command line switch or something that would be cleaner.
It looks like the --only argument might do something like that, but I haven't been able to get it to work.
Thanks.
The text was updated successfully, but these errors were encountered: