[CLOSED] v35.0.0

[marekd]

Since the previous beta test was useful and thanks a lot to everyone for joining in, we decided to continue with beta testing. The new version is ready!

What's new in version 35.0.0

• New hurricane tracker with history and newly also with forecast (if available for selected hurricane)
• Added HRRR models for North America
• Fixed bounds for local models
• Tens of bugfixes and improvements

Dev changes (for plugin developers)

• Whole client is now in TypeScript
• Removed @plugins/product-descriptions
• Local model bounds are now 2D array of coordinates: [lat, lon][][]
• Renamed wRender to weatherTableRenderer in @plugins/detail-render
• Removed monkey patching of @plugins/detail-render, @plugins/pois-libs, @plugin/detail and @plugin/picker. It should not affect internal API, but just in case...
• Huge amount of other internal changes without changing client API

(cc: @rittels, @jakubvrana, @vicb, @johnckealy)

How to report an issue from testing?

Just post a comment in this thread below :-) If you provide us with:

• a step-by-step manual how reproduce the error
• what exactly is wrong
• what it should do correctly

It will help us a lot! Thanks.

Please, try to not duplicate other reports. If you found someone else already report the same issue, just upvote his/her post.

How to join beta?

Open https://www.windy.com/beta-test address and follow the instructions. You can leave beta test at any time. To leave the test, just click "BETA" sign on Windy logo (or visit mentioned address again) and follow the instructions as well. In a case of a total disaster, delete the beta=1 cookie for the windy.com domain and refresh the page.

Beta test is available only for desktop (browser) version.

Feel free to disccuss anything! Not just bug reports :-) Thank you for your help!

[vicb]

@marekd said in v35.0.0:

https://www.windy.com/beta-test

Thanks for the heads up - it is super convenient to test plugins (and I am happy to have nothing to do this time)

[Liam.pankhurst]

@marekd is there any plans to add local models for Australia? This would be very helpful

[marekd]

@liam-pankhurst What a coincidence... Stay tuned ;-)

[idefix37]

@marekd
Hello,
This new version is really interesting. I'm sure HRRR will be a must for American users!

The new hurricane tracker is based on ECMWF forecast and past track.
https://www.ecmwf.int/en/forecasts/charts/tcyclone/tc_plumes?facets=undefined&time=2022022100,0,2022022100&unique_id=05S_EMNATI_2022
I thought the previous one was based on NHC data. But I was may be wrong.
Are the wind speeds really using the Safir-Simpson scale in Windy as it is mentioned in the presentation of the Hurricane tracker? I have not found in ECMWF literature any information about it. Only that "Intensity estimates are based on the raw 10m wind speeds in model output; because of resolution limitations the resulting categories often provide an underestimate the true".

Concerning HRRR the only issue I found is the absence of past data to get a good comparison with a local weather station. The dotted lines are shown 1 or 2 hours back which is not enough for a good comparison. For example:
.
I have not seen what you mean with "Fixed bounds for local models".

[marekd]

@idefix37 As usually, thank you! :-)

• just for to be sure, we will check the Safir-Simpson scale in a HT

• HRRR archive will be fixed soon, thank you for pointing it out

• I have not seen what you mean with "Fixed bounds for local models".

  then it is fixed correctly :-)

[idefix37]

@marekd said in v35.0.0:

@idefix37

• just for to be sure, we will check the Safir-Simpson scale in a HT

There is an other reason for reconsidering the reference to the Safir-Simpson scale. For ranking tropical cyclones, in other areas than the Atlantic and the NE Pacific, different scales are used:
https://en.m.wikipedia.org/wiki/Tropical_cyclone_scales

[marekd]

@idefix37 You are right. Unfortunately, we will hide a hurricane forecast part for the next release until we solve this issue (we will keep the history as it is in production now). We think it is better to show nothing than stupidity. We are going to fix it and release the fix asap. Thanks again!

[Liam.pankhurst]

@marekd oh Thankyou that's awesome.
Is there any idea of when that might be happening?

[marekd]

@liam-pankhurst We just test data post-processing, then it is added to the client and sent to our internal testers. After this process, it can go to the production. It usually takes 3-6 weeks (depends on how many bugs are in data). But no guarantee! It's just behind-the-scenes info.

[Liam.pankhurst]

@marekd awesome, thankyou

[rittels]

@rittels, @jakubvrana, @vicb, @johnckealy, @marekd

W.picker.getParams() and W.rootScope.pickerLocation no longer works.

Use W.store.get("pickerLocation").

[vicb]

@rittels I'm using windyPicker.on("pickerMoved", ({ lat, lon }) => {...}) and it still seems to work, do you confirm ?

[rittels]

@vicb

Hi. Yes it still works.

Sometimes you need the picker position.

For instance when your plugin opens, you can check if the picker is already open and get the coords, then store.get("pickerLocation") is useful. It returns null if the picker is closed.

Or: If a location is searched, then the detail plugin opens, which also opens the picker. The picker.on("pickerOpened",..) is then not triggered.

[marekd]

Beta test is closed, v35.0.0 has been released. Thank you all for your help!