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

Parallel Processing in Crop_plot_data function #36

Open
Nageshbansal opened this issue Sep 27, 2022 · 7 comments
Open

Parallel Processing in Crop_plot_data function #36

Nageshbansal opened this issue Sep 27, 2022 · 7 comments
Assignees
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@Nageshbansal
Copy link
Collaborator

@MarconiS, We have to implement parallel processing for the clip_plot function over the aop data rows.

@Nageshbansal
Copy link
Collaborator Author

@MarconiS, i will look into this meanwhile.

@Nageshbansal Nageshbansal self-assigned this Nov 11, 2022
@ConnectBhawna
Copy link

Hi @Nageshbansal can i work on this issue?

@Nageshbansal
Copy link
Collaborator Author

hey @ConnectBhawna , sure. Let me know if you need any help

@Nageshbansal
Copy link
Collaborator Author

@MarconiS , Parallel processing involves two main steps:

  1. Downloading data from multiple websites and years concurrently (instead of doing it one after the other, which would be slower).
  2. Taking the downloaded data and carrying out additional processing in functions like retrieve_coords_itc concurrently as well.
    Is that correct?

@MarconiS
Copy link
Collaborator

yep, I think getting the data to be fetched in batches of 1 site - 1 year should fix the issue of being timeouted. If we have problems with the number of times per second we can query the API we can jitter the calls, I guess? like allow only 2 (or 4 if API key in provided) instances per second?

@Nageshbansal
Copy link
Collaborator Author

downloading the data in batches sounds good to me. Just to clarify , for e.g 1 batch of ABBY-2019 and another batch of ABBY-2020.

@MarconiS
Copy link
Collaborator

yeah, if that works fine to you, that sounds good to me! I believe we were discussing that it may send too many requests; if that's so, I am happy also with the ABBY-[2019:2020]. Whatever works best for you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants