-
Notifications
You must be signed in to change notification settings - Fork 31
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
Heat Wave Index Not Calculating #99
Comments
responded in freshdesk, try running a station by itself? And please upload one of these stations.
… On 12/02/2023 03:48 ACDT SA-Munna ***@***.***> wrote:
Hello,
So my situation is when I run a single station it calculates all the indices but when I run through batch process station, the heat wave indices are not being calculated. This is happening for some of the models and I don't know why. I have checked if there are any errors in station files. The error message is attached here!
[climpact_hw_error_ss] https://user-images.githubusercontent.com/33527814/218271665-53d7f592-4d6f-41e0-a8eb-2f047ad943bb.png
—
Reply to this email directly, view it on GitHub #99, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACW3FAKSUQSF63KGV5YPX3LWW7CVDANCNFSM6AAAAAAUYZURUQ.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
A single station works fine. But I have a large no of stations and I cannot process them all individually. I am attaching one station for reference. |
Late response. Can you try just running the stations in batch that are not producing the heatwave indices. So exclude all the "working" stations. And then please send the batch script and stations and I'll try debug. |
Hello,
So my situation is when I run a single station it calculates all the indices but when I run through batch process station, the heat wave indices are not being calculated. This is happening for some of the models and I don't know why. I have checked if there are any errors in station files. The error message is attached here!
The text was updated successfully, but these errors were encountered: