![]() | This article is rated Start-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||
|
Hello fellow Wikipedians,
I have just modified one external link on Canadian weather radar network. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
An editor has reviewed this edit and fixed any errors that were found.
Cheers.— InternetArchiveBot ( Report bug) 10:58, 25 January 2018 (UTC)
I did some quick check on the data but I won't be doing extensive investigation. If someone want to have a look, you probably need to be a programmer. Install conda, then the wradlib library, and run the following code to start looking at the data:
This will display the structure
>>> file = "C:/Users/normandp/Desktop/20220629T1406Z_MSC_Radar-VolumeScans_CASBV.hdf5" >>> data = wrl.io.read_generic_hdf5(file) >>> for e in data: ... print(e)
Then, to investigate what is what... display a few of the sections and you can reverse engineer the structure
See the b field change between the various "data" groups, dbzh, rhohc (dual pol cross correlation), uphidp (dual pol differential phase), wradh might be the velocity (doppler) spectrum width? I think? :
>>> data["dataset1/data1/what"] {'attrs': {'gain': 0.5, 'nodata': 255.0, 'offset': -31.5, 'quantity': b'DBZH', 'undetect': 0.0}} >>> data["dataset1/data2/what"] {'attrs': {'gain': 0.003937007859349251, 'nodata': 256.0, 'offset': 0.0, 'quantity': b'RHOHV', 'undetect': 0.0}} >>> data["dataset1/data3/what"] {'attrs': {'gain': 0.005493331700563431, 'nodata': 65535.0, 'offset': 0.0, 'quantity': b'UPHIDP', 'undetect': 0.0}} >>> data["dataset1/data4/what"] {'attrs': {'gain': 0.12466653436422348, 'nodata': 255.0, 'offset': 0.12470000237226486, 'quantity': b'WRADH', 'undetect': 0.0}}
And these... the elevation change between the "dataset":
>>> data["dataset1/where"] {'attrs': {'a1gate': 78, 'elangle': 24.399999618530273, 'nbins': 245, 'nrays': 360, 'rscale': 500.0, 'rstart': 0.0}} >>> data["dataset2/where"] {'attrs': {'a1gate': 23, 'elangle': 21.200000762939453, 'nbins': 245, 'nrays': 360, 'rscale': 500.0, 'rstart': 0.0}} >>> data["dataset3/where"] {'attrs': {'a1gate': 329, 'elangle': 18.0, 'nbins': 245, 'nrays': 360, 'rscale': 500.0, 'rstart': 0.0}}
Should we rename the model of the S-band radars to reflect the acquisition of Selex by (ultimately) Leonardo? I don't know if Selex called it "METEOR 1700S" or just "1700S", but after Selex was acquired by Leonardo it seems to have been marketed as "Selex METEOR 1700S" for a while, and now it is just "METEOR 1700S": https://electronics.leonardo.com/documents/16277707/18389918/METEOR+1700S_17071035102_EN.pdf - Wikkiwonkk ( talk) 01:01, 15 December 2022 (UTC)
The article uses individual bolded letters to explain the callsign abbreviations. This is directly in conflict with
MOS:BOLD which says Avoid using boldface (or other font gimmicks) in the expansions of acronyms.
The claim that bold font is "necessary" to explain the acronym seems unconvincing to me; there is no ambiguity in seeing which letters in "CASAG" come from "Aldergrove", which letters in "CASBE" come from "Bethune", etc. The nonstandard use of bold here does not help the reader.
CodeTalker (
talk)
00:27, 1 January 2024 (UTC)
![]() | This article is rated Start-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||
|
Hello fellow Wikipedians,
I have just modified one external link on Canadian weather radar network. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
An editor has reviewed this edit and fixed any errors that were found.
Cheers.— InternetArchiveBot ( Report bug) 10:58, 25 January 2018 (UTC)
I did some quick check on the data but I won't be doing extensive investigation. If someone want to have a look, you probably need to be a programmer. Install conda, then the wradlib library, and run the following code to start looking at the data:
This will display the structure
>>> file = "C:/Users/normandp/Desktop/20220629T1406Z_MSC_Radar-VolumeScans_CASBV.hdf5" >>> data = wrl.io.read_generic_hdf5(file) >>> for e in data: ... print(e)
Then, to investigate what is what... display a few of the sections and you can reverse engineer the structure
See the b field change between the various "data" groups, dbzh, rhohc (dual pol cross correlation), uphidp (dual pol differential phase), wradh might be the velocity (doppler) spectrum width? I think? :
>>> data["dataset1/data1/what"] {'attrs': {'gain': 0.5, 'nodata': 255.0, 'offset': -31.5, 'quantity': b'DBZH', 'undetect': 0.0}} >>> data["dataset1/data2/what"] {'attrs': {'gain': 0.003937007859349251, 'nodata': 256.0, 'offset': 0.0, 'quantity': b'RHOHV', 'undetect': 0.0}} >>> data["dataset1/data3/what"] {'attrs': {'gain': 0.005493331700563431, 'nodata': 65535.0, 'offset': 0.0, 'quantity': b'UPHIDP', 'undetect': 0.0}} >>> data["dataset1/data4/what"] {'attrs': {'gain': 0.12466653436422348, 'nodata': 255.0, 'offset': 0.12470000237226486, 'quantity': b'WRADH', 'undetect': 0.0}}
And these... the elevation change between the "dataset":
>>> data["dataset1/where"] {'attrs': {'a1gate': 78, 'elangle': 24.399999618530273, 'nbins': 245, 'nrays': 360, 'rscale': 500.0, 'rstart': 0.0}} >>> data["dataset2/where"] {'attrs': {'a1gate': 23, 'elangle': 21.200000762939453, 'nbins': 245, 'nrays': 360, 'rscale': 500.0, 'rstart': 0.0}} >>> data["dataset3/where"] {'attrs': {'a1gate': 329, 'elangle': 18.0, 'nbins': 245, 'nrays': 360, 'rscale': 500.0, 'rstart': 0.0}}
Should we rename the model of the S-band radars to reflect the acquisition of Selex by (ultimately) Leonardo? I don't know if Selex called it "METEOR 1700S" or just "1700S", but after Selex was acquired by Leonardo it seems to have been marketed as "Selex METEOR 1700S" for a while, and now it is just "METEOR 1700S": https://electronics.leonardo.com/documents/16277707/18389918/METEOR+1700S_17071035102_EN.pdf - Wikkiwonkk ( talk) 01:01, 15 December 2022 (UTC)
The article uses individual bolded letters to explain the callsign abbreviations. This is directly in conflict with
MOS:BOLD which says Avoid using boldface (or other font gimmicks) in the expansions of acronyms.
The claim that bold font is "necessary" to explain the acronym seems unconvincing to me; there is no ambiguity in seeing which letters in "CASAG" come from "Aldergrove", which letters in "CASBE" come from "Bethune", etc. The nonstandard use of bold here does not help the reader.
CodeTalker (
talk)
00:27, 1 January 2024 (UTC)