Skip to content

MasterBeard/Proxy-Labels-Implementation

View on GitHub ↗Related repositories →

To ensure the reproducibility of the article, we have provided a notebook code that explains how to use proxy labels to identify investment portfolios with higher precision and a greater number of correct upward signal predictions. The example in the notebook code involves the test results for Test Set 2 under Task 1.

active 2025-03-102025-03-12 (UTC)

Complete coverage26,323 / 26,323 hourly files (100%) · 2 absent upstream2023-08-152026-08-15 (UTC)
Events
9
Pushes
7
Pull requests
0
Issues
0
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 3 days from 2025-03-10 to 2025-03-12. Pushes: 7 total, peak 4 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 0 total, peak 0 in a day. Comments: 0 total, peak 0 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
MasterBeard7700

Recent activity

Latest issues, pull requests and releases

No issue or PR events — this repo's activity is pushes only.

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.