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

data.ERA5_and_Forcing_MultiStep does not behave correctly when train/valid_batch_size is greater than 1 #116

Open
kanz76 opened this issue Oct 15, 2024 · 1 comment
Assignees

Comments

@kanz76
Copy link
Collaborator

kanz76 commented Oct 15, 2024

The current implementation of data.ERA5_and_Forcing_MultiStep samples item based on the forecast_step parameter`, setting the batch_size to greater than 1 can result in a mismatch of input and target tensors.

@yingkaisha
Copy link
Collaborator

For now, I will add an assertion in the credit.parser first to encourage the use of batch_size=1.

I will look into this later.

@yingkaisha yingkaisha self-assigned this Nov 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants