AssessingSolar / AssessingSolar/dtu_solar_station

Timestamp offset

Open
#54 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
0
Forks
1
PR merge metrics
No merged PRs in 30d

Description

The timestamp from the Solys2 is logged (which I believed is based on a GPS received, so it is highly accurate).

```python
df['Solys_time_1'] = pd.to_datetime(
df['Solys_gps_time'].str[:17], format='%Y %j %H %M %S', errors='coerce')

# This format only exists in January 2015
df['Solys_time_2'] = pd.to_datetime(
df['Solys_gps_time'].str[-19:], format='%H:%M:%S %m/%d/%Y', errors='coerce')

(df.index - df['Solys_time_1']).dt.total_seconds().resample('1h').mean().plot()
```

![Image](https://github.com/user-attachments/assets/761325e1-c47b-45ab-a276-3befb2408824)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by running the pandas timestamp parsing shown in the issue and comparing the resulting Solys_time_1 values with df.index. Determine the source and extent of the offset across the two timestamp formats; the issue is complete when the discrepancy is explained and the timestamp handling has a reproducible correction or documented expected behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
pandas, python
Domain
data-engineering
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.