Hi Everyone!
A couple of “snow days” (off from school) here in Atlanta is affording me the opportunity to tidy up my new release of WXSIM (2025, Build 1.0). The feedback you’ve given so far is very much appreciated, as I’m trying to make the program as smooth, accurate, and enjoyable as I can.
The changes here are minor. I think I’ve got the messaging about wdata.txt versus wdatamixed.txt cleared up, so you have the option to make a choice and then not deal with the message again. Also, one user (that I know of) has been seeing a seemingly random (once every several forecast runs, but only in scheduled auto runs) error message (which when acknowledged closes the program) about ‘input past end of file’ (world2.fdt), with reference to it occurring in adv.command1.click. I’ve found where, but not why it’s occurring, so I’ve created a diagnostic file called wdatrec.txt. If you ever see that particular error, I’d appreciate your sending me that file as it exist right after the error and closing of WXSIM.
I’ve also been seeing an odd, apparently random error myself, in about one out of every 15 scheduled auto runs, in a certain instance of WXSIM (I have three setups running, five times a day). This one leads to a cascade of errors, because it causes wret.exe to have an error at line 1909 (the message says this), and then when it hangs, WXSIM errors out on the next run. I’ve figured out that it’s from WXSIM failing to finish a copy or format transfer of latest.wxf, but why it’s randomly doing that, I’m not sure. I sort of suspect it’s a timing issue, and a conflict may be arising between a batch file I have copying and uploading that .wxf file, perhaps (I’m not sure about it) sometimes randomly exactly when WXSIM is dealing with the file. Have any of you seen this? In any case, my first move has been to have the forecast run a few minutes later, to avoid a possible conflict (so far about 6 good runs in a row since that change). Any feedback on that would be helpful.
I also think I’ve solved a rare (I know of only one instance) error in WXSIM-Lite, where it would give a ‘subscript out of range’ error while doing its analysis run (and possibly also when making a forecast). In this case, it was because the user’s data (from WeatherLink) just happened to have a gap or outage, surrounding midnight. I’ve created a quality control check, of sorts, which now sidesteps the problem.
The new installer is beta3, instead of just beta, and it’s at
www.wxsim.com/wxsim2025upgbeta3.exe
I’ve left the previous one (without the “3” on the end) up, in case you need to revert to that (or use www.wxsim.com/wxsimupg.exe to revert to the latest official release).
Thanks!
Tom