cmu-delphi/forecast-eval

Consider defining `USE_CURR_TRUTH` as a `reactive`

Open

#273 opened on Apr 25, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)R (3 forks)auto 404
good first issue

Repository metrics

Stars
 (6 stars)
PR merge metrics
 (PR metrics pending)

Description

There are several observers that exist only to change the value of USE_CURR_TRUTH. The logic could be simpler and dashboard faster if USE_CURR_TRUTH were changed into a reactive. Since reactives are lazily evaluated, they are faster than observers.

Contributor guide

Research direction
Identify where USE CURR TRUTH is currently defined (likely as reactiveVal or reactiveValues). Then replace the observer that updates it with a reactive expression that automatically updates when its dependencies change. Ensure all downstream observers and outputs read from this new reactive instead of being triggered by the observer. This leverages lazy evaluation and can improve performance.
Tech stack
r
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RShiny
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80