-
Notifications
You must be signed in to change notification settings - Fork 123
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
FarmVibes.AI 24.04 #157
Merged
Merged
FarmVibes.AI 24.04 #157
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Alex Crown <acrown@microsoft.com> Co-authored-by: Eduardo Rodrigues <edrodrigues@microsoft.com> Co-authored-by: Rafael Padilha <rpadilha@microsoft.com> Co-authored-by: Renato Luiz de Freitas Cunha <renato.cunha@microsoft.com>
Co-authored-by: Bruno Silva <brunosilva@microsoft.com> Co-authored-by: Eduardo Rodrigues <edrodrigues@microsoft.com> Co-authored-by: Jessica Wolk <Jessica.Wolk@microsoft.com> Co-authored-by: Naga Bilwanth Gangarapu <Naga@zensa.co> Co-authored-by: Rafael Padilha <rpadilha@microsoft.com> Co-authored-by: Renato Luiz de Freitas Cunha <renato.cunha@microsoft.com> Co-authored-by: Rick Gutierrez <ricardgu@microsoft.com>
- [🎉 NEW] We now support remote cluster creation on any Azure Cloud Environment, abstracting the requirements of different cloud environments and backend services. This means we now support deployments in sovereign clouds, such as the [US Government Cloud](https://learn.microsoft.com/en-us/azure/azure-government/documentation-government-welcome), the [German Cloud](https://learn.microsoft.com/en-us/azure/germany/), and the [China Cloud](https://learn.microsoft.com/en-us/azure/china/overview-operations), in addition to the Azure Public Cloud. - [📈 IMPROVEMENT] We upgraded terraform provider to version 3.89.0 to support cluster setup through Azure Cloud Shell. - [⚒️ FIX] We fixed an issue that would cause the local cluster setup to fail in case the cluster name had underscores. Related to issue #133. - [📈 IMPROVEMENT] We revised the notebook dependencies and changed the default environment and package manager from Conda to [Micromamba](https://mamba.readthedocs.io/en/latest/installation/micromamba-installation.html). Environments should build considerably faster and present fewer dependency issues. Related to issues #141 and #144. - [🎉 NEW] We added instructions on setting up the remote cluster using Azure Cloud Shell to the [Remote Cluster User Guide](https://microsoft.github.io/farmvibes-ai/docfiles/markdown/AKS.html). - [⚒️ FIX] We fixed a bug that prevented the REST API documentation page to be rendered correctly. Related to issue #131. ---- Co-authored-by: Bruno Silva <brunosilva@microsoft.com> Co-authored-by: Peter Hammond <v-phammond@microsoft.com> Co-authored-by: Rafael Padilha <rpadilha@microsoft.com> Co-authored-by: Renato Luiz de Freitas Cunha <renato.cunha@microsoft.com> Co-authored-by: Rick Gutierrez <ricardgu@microsoft.com>
Co-authored-by: Bruno Silva <brunosilva@microsoft.com> Co-authored-by: Naga Bilwanth Gangarapu <Naga@zensa.co> Co-authored-by: Rafael Padilha <rpadilha@microsoft.com> Co-authored-by: Renato Luiz de Freitas Cunha <renato.cunha@microsoft.com> Co-authored-by: Roberto de Moura Estevão Filho <robertode@microsoft.com>
rafaspadilha
approved these changes
Apr 5, 2024
robertomest
approved these changes
Apr 5, 2024
brsilvarec
approved these changes
Apr 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a sync of our repo. Here's the summary of the changes:
Support to new ADMA API version:
[💔 BREAKING CHANGES] We added support to the new Azure Data Manager for Agriculture (ADMA) API version 2023-11-01-preview. To comply with the new API, some of our data types, workflows, and notebooks were updated. A summary of the changes are:
farmer_id
property has now changed toparty_id
inADMAgSeasonalFieldInput
object (which is passed as input for our workflows) and other ADMA data types. Also, there is no more theboundary_id
field as boundary resources are no more single objects in ADMA. The boundary information is part of the ADMA entities (seasonal field, field etc.).data_ingestion/admag/admag_seasonal_field
,data_ingestion/admag/prescriptions
, andfarm_ai/agriculture/heatmap_using_classification_admag
.Workflows:
data_ingestion/weather/download_herbie
workflow to allow downloading both analysis (zero lead time) up to a point in time and then forecast with progressively increasing lead times after that.scripts/export_sam_models.py
#153.data_ingestion/sentinel1/preprocess_s1
anddata_ingestion/spaceeye/spaceeye
). The documentation with the parameter description will be updated in a future release.Backend:
3.11
. Additionally, our DAPR logs are now in JSON format.ngrok
package to version7.1.2
, which will solve the issues with the What-if scenario evaluation for carbon sequestration notebook andfarm_ai/carbon_local/carbon_whatif
workflow. Related to issue What-if scenario evaluation for carbon sequestration notebook #151.add-secret
subcommand not adding secrets to the KeyVault during remote (AKS) cluster setup. Related to issue remote add-secret doesn’t work correctly #147.Notebooks:
Documentation:
Client:
n
runs withclient.monitor(n)
, which will print a summarized table with their progress, as well as retrieve the lastn
VibeWorkflowRun
objects withclient.get_last_runs(n)
method. We also added minor bug fixes to themonitor
anddocument_workflow
methods, which were breaking for deleated runs and workflows with None/empty value parameters, respectivelly.Co-authored-by: Bruno Silva brunosilva@microsoft.com
Co-authored-by: Eduardo Rodrigues edrodrigues@microsoft.com
Co-authored-by: Naga Bilwanth Gangarapu Naga@zensa.co
Co-authored-by: Rafael Padilha rpadilha@microsoft.com
Co-authored-by: Renato Luiz de Freitas Cunha renato.cunha@microsoft.com
Co-authored-by: Roberto de Moura Estevão Filho robertode@microsoft.com