All seemed fine, but a couple of days ago, I detected that the WXSIM forecasts almost always start with a much too high (or low) temperature.
I posted a topic in the weather-watch.com forum https://discourse.weather-watch.com/t/w ... ture/74865 and could narrow it down while waiting for feedback from Tom.
The issue is, that WXSIMATE imports the local CMX data with a factor of 10 too high for temperature and dew point (but not for pressure) and that is propageted to WXSIM. See screenshot comparision between real values in CMX/CU and imported values in WXSIMATE.
Seems only to happen in a windows environment with locale that uses COMMA as decimal point. WXIM has been working fine in the past and is displaying also comma in the WxSim GUI screens. In the past (v3) CMX monthly logfile stored the date differently and used semicolon; as separator and comma as decimal in my environment. After the v4 migration the CMX logfile separator is comma; and the decimal point is used. That might be affecting now WXSIMATE.
I was wondering if any other WXSIM+CMX user has the same environment (CMX v4, WXSIM 2024 build 1.1, WXSIMATE v9.2 AND a Windows locale with comma) like me, and if yes, if the same issue with WXSIMATE is happening.
2 lines old format of CMX monthly file v3 Dez24log.txt:
Code: Select all
01.12.24;00:00;-2,3;98;-2,6;1;3;37;0,0;0,0;1030,7;760,4;25,4;48;2;-2,3;-2,3;0,0;0;0,00;652,94;-4,9;0;0,0;48;0,0;0,0;-2,3;-2,3
01.12.24;00:05;-2,4;98;-2,7;1;3;37;0,0;0,0;1030,3;760,4;25,4;48;2;-2,4;-2,4;0,0;0;0,00;652,94;-5,0;0;0,0;26;0,0;0,0;-2,4;-2,4
Code: Select all
01/12/24,00:00,-2.3,98,-2.6,1,3,37,0.0,0.0,1030.7,760.4,25.4,48,2,-2.3,-2.3,0.0,0,0.00,652.94,-4.9,0,0.0,48,0.0,0.0,-2.3,-2.3
01/12/24,00:05,-2.4,98,-2.7,1,3,37,0.0,0.0,1030.3,760.4,25.4,48,2,-2.4,-2.4,0.0,0,0.00,652.94,-5.0,0,0.0,26,0.0,0.0,-2.4,-2.4