Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Callbacks recompute predictions #117

Open
HCookie opened this issue Oct 30, 2024 · 1 comment
Open

Callbacks recompute predictions #117

HCookie opened this issue Oct 30, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@HCookie
Copy link
Member

HCookie commented Oct 30, 2024

What happened?

When using the rollout callbacks together, a number of predictions are done multiple times, wasting compute.
Both RolloutEval and LongRolloutPlots call the rollout step independently.

What are the steps to reproduce the bug?

Run model with both RolloutEval and LongRolloutPlots enabled

Version

develop, v0.2.1+

Platform (OS and architecture)

ATOS

Relevant log output

No response

Accompanying data

No response

Organisation

ECMWF

@HCookie HCookie added the bug Something isn't working label Oct 30, 2024
@Rilwan-Adewoyin
Copy link
Member

Rilwan-Adewoyin commented Oct 31, 2024

?? I propose having a parent HolderCallback class tailored to each type of task:

  • Forecasting: RolloutEval
  • Reconstruction: ReconstructionEval
  • Downscaling: DownscalingEval

Each of these classes would contain task-specific versions of the standard callbacks. For instance, RolloutEval would include PlotLossForecast, while ReconstructionEval would use PlotLossReconstruction. These PlotLoss callbacks could inherit from a general PlotLoss class.

In each parent HolderCallback class, we would manage the forward loop and pass outputs to the relevant task-specific callbacks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants