jdubowy
commented
4 weeks ago The problem is that profile.txt can have asterisk strings of varying lengths, with multiple asterisk strings possibly running into each other as well as into the preceding number values. e.g.
HGTS TEMP UWND VWND WWND RELH TKEN TPOT WDIR WSP
oC m/s m/s mb/h % oK deg m/
1000 166 20.6 0 0 0.79 80.8 0.30 293.8******* 0.
975 384 21.1 2.2 2.1 0 72.8 0 296.4 225.6 3.
950 610 22.6 6.0 1.3 -2.9 57.6 0 300.1 257.3 6.
...I've updated the profile.txt parsing code with a hack to better handle the various asterisk string possibilities. A better solution would be to update the profiler code (different repo) that generates profile.txt to always guarantee spaces between values. Another solution would be to update the parsing code to split the pressure level value strings based the positions of the variable names in the header string.
I've published bluesky v4.5.20
daisyhjt
Hi there,
I'm using the NAM 12 km archived meteorology data (https://www.ready.noaa.gov/archives.php) to run bluesky. However, not all cases run successfully. For some days, I encounter an error: IndexError: list index out of range in the _parse_hourlytext function of the arlprofiler module. Thus it returns exactly empty meteorology json data.
Command Used:
Detailed Log:
Attached Files for Debugging
SE2018_05_11_permit.json permit_config.json locations.csv profile.txt
I guess the error is likely from a mismatch between the expected number of columns in a few lines of the profile.txt file and the actual number of columns. Since I'm limited in my ability to modify the development code on HPC, I was wondering if there is any help to identify and fix the cause of this error?
Thank you in advance!