what you have in place works fine (happy days!!!).....just need to go back to old school and picture that parcel ascent.

Cheers

Thx John....I have been using your plugin today at work and utilised the Zoom function (worked well for analysing the boundary layer etc) and also how the mouse over the SkewT now represents the right hpa level (and T/Td/wind data).

Well done on being included into the development team. Windy has really taken a big leap forward all thanks to yours and the other guys development.

Much appreciated.

PS: If you are looking at any further additions to the SkewT plugin....is it possible to add a manually manipulated parcel trace (like the feature in your tephigram program)? That is, being able to slide the sfc temp point to give a projected parcel trace overlay on the forecast SkewT trace.

Again, well done. Thx

Thx John, when you get some time....no urgency

I'll try that image file again

Hi @johnckealy,

Is it possible for you to change the positioning of the Skewt window? In the current setup, the far bottom section of the Skewt window is covered by the meteogram display (as shown below).


Are you able to shift the Skewt window up so it fits just below the station search window? I am hoping this will uncovered the base of the Skewt plot when also displaying the meteogram plot.

Thanks
Craig

I was using 0.2.5 and will now switch over 0.2.6.

Thx for your work from a fellow meteorologist!

You can check the code at https://github.com/vicb/windy-plugin-sounding
It's still an early version.
My plan is to make the code more modular. Maybe we could work on some common components.

Let me know when you have time for pairing on that.

Thanks for the comments and the in-depth look into this. I've actually had this reported to me by another user, and the issue should be fixed. Is the plugin loading as version 0.2.6? The isobar labels should be green in this version.

I've got in touch with a developer who's going to help out with some of the coding, and plan to have a robust plugin by version 1.0. As a meteorologist, I'm learning the dev side of things as I go, so patience is appreciated; as are the bug reports. I'll look into your comments in more detail when I have the chance, but for now please make sure you're using version 0.2.6, as the specific issues you mention should have been fixed.

John

@johnckealy

in addition to my post above, I have just noticed that when running the mouse cursor across the SkewT image, the layer wind/temp/press details are not consistent with the cursor location. It seems like the cursor is offset by about 2cm below the data point it is displaying.

Regards
Craig

thankyou for your development work on the SkewT plugin.....I have been waiting a while for this addition to the Windy project.

Could I highlight one fault with your plugin and I believe it has to do with the date time used in the SkewT plot not being the same as the Windy background time display.

1/ In the top image (for time 950hpa wind field at 2200local /12Z), the SkewT wind at 950hpa is ~080/45kts.

2/ When I skipped ahead by three time steps (or advanced ahead by 9 hours - see bottom image for 0700local/ 21Z ), I found that the SkewT diagram was now indicating a 950hpa wind of 080/20kt.
a/ The wind field display at the pointer location within the 21Z frame indicates a strong wind 080/45kt. This displayed an inconsistency with the SkewT 950hpa wind 080/20kt for the same time step.

3/ It appears that the wind speed at 950hpa on the SkewT display for the Windy time step 12Z, coincided with the 950hpa wind field image at the pointer location for Windy 21Z display time.

In other words, the SkewT display/time stamp is 9 hours ahead of the Windy display/time stamp.

I looked closer at this because I found inconsistencies with the T/Td trace compared to the displayed cloud fields.
I tested this with other time steps and areas where winds changed noticeably in speed and direction and found the same inconsistency.

Please take a look at your programming. I hope you can see this and are able to rectify this.......I would love to be able to continuing using this plugin.

Regards
Craig

The timestamp call works a treat. With the loader: no, there was no error, but I was embedding one load statement within the other which was probably a bad idea. I found a better approach by looping through the forecast keys and creating a time series array of surface pressure. Works nice now.

I also added a call to store.get('product') so that I could load the current model, and I think I've found a bug on your end. If you change model from ECMWF to GFS and vice versa, the output of store.get('product') shows the old model. You have to move the picker before it will show the highlighted model.

One other thing: how can I get the latest version to show in the plugin loader? If you enter windy-plugin-skewt you get version 0.1.0, the first version. You have to enter windy-plugin-skewt@0.2.5 to get the correct one. Obviously, this isn't a windy thing, it's to do with unpkg and npm. But any idea how to fix it? Npm shows me the latest version on its website, but I have to add the version number in unpkg.com to get the right one.

Ad 2)

import store from 'store'

store.on('timestamp', ts => {
  console.log('New ts is', timestamp)
})