Metadata time in Databricks
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 174
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
i'm running Aurora on a GPU H100 on Databricks. I'm using ECMWF data from the 00 run.
When i add the time location in my script
import time, os
os.environ['TZ'] = 'Europe/Rome'
time.tzset()
Aurora's forecast differs from the one obtained without specifying the time zone.
In both cases i set the time metadata as time = Timestamp('2025-09-11 00:00:00') this is a UTC time based on ECMWF data
Do I have to set the timezone or not?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the two cases in the issue: the ECMWF 00 run with Timestamp('2025-09-11 00:00:00'), both with and without the TZ setting and time.tzset(). Compare the resulting Aurora forecasts and establish the expected timezone handling for the metadata; done means the behavior is understood and documented or corrected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100