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

Operationalise in-house models: suitable planting window (SPW R Code) #20

Open
3 tasks done
Tracked by #26
danangmassandy opened this issue Jul 4, 2024 · 3 comments
Open
3 tasks done
Tracked by #26
Assignees

Comments

@danangmassandy
Copy link
Collaborator

danangmassandy commented Jul 4, 2024

Check the R code that John has sent.

  • Identify the input data
  • Check the model output and how to store into GAP
  • RnD on R code integration
@danangmassandy danangmassandy self-assigned this Jul 4, 2024
@mvmaltitz mvmaltitz added this to the 2. Crop plan MVP operational milestone Jul 9, 2024
@amyburness amyburness changed the title SPW R Code Operationalise in-house models: suitable planting window (SPW R Code) Jul 9, 2024
@danangmassandy
Copy link
Collaborator Author

I have checked the R code and tried to integrate the code in the system using Plumber. The required fields are evapotranspirationSum, rainAccumulationSum, LTNPET, and LTNPrecip.

@danangmassandy
Copy link
Collaborator Author

The R model is using Tomorrow.io data from below endpoints:

  • /historical
  • /timelines
  • /historical/normals

The variables that R model is using is only: rainAccumulationSum and evapotranspirationSum. I have created a data reader from tomorrow.io but currently it's only limited to these two variable and single point. We may need to add more variable for Crop Plan Generator to fetch short-term forecast.

@gubuntu
Copy link

gubuntu commented Jul 23, 2024

SPW must fetch inputs from GAP, not directly from tomorrow.io

and write outputs to DB

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

3 participants