Replies: 5 comments 2 replies
-
|
@sonriks6 thank you! This helped me resolve my issue in databricks. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I do not know what should I do to succesfully to run the model. It was working before with google-meridian version 1.0.9, now if I try to install the same old version, it is giving the same error as above. COuld you please help me. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @OykuOzOzen , Thank you for contacting us! The numpy version was bumped to 2.0.2 in Meridian version 1.0.7. If you're looking to use the functionality in the later versions of Meridian, have you tried the above suggestion to use the 16.3 ML beta runtime? There's an open bug in databricks to support later versions of numpy (databricks/databricks-sql-python#432) that you can also track. Otherwise, I would recommend you use Meridian version < 1.0.7. Feel free to reach out for any further queries or feedback regarding Meridian. Google Meridian Support Team |
Beta Was this translation helpful? Give feedback.
-
|
Ok after a lot of trial and error, I give up. Can someone just tell me what the latest, best practice is for using Meridian in Databricks. Cc: @gousesb |
Beta Was this translation helpful? Give feedback.
-
|
Hi @klatta87 This is our current configuration:
This is running in prod environment, no issues so far, no need to install additional dependencies or fix numpy version. Hope this helps. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Heads up on those using Databricks, with Meridian version 1.0.7 where bumped numpy, tensorflow and other libraries, so if running on GPU, the only runtime valid for this requirements is the 16.3 ML beta (released 12/03/2025), this is just because tf 2.18 needs cuDNN 9.3 library on the runtime.
Beta Was this translation helpful? Give feedback.
All reactions