every now and then and i get this message…attached
any ideas?
thanks
Same thing here.
It started when I moved wxsim to a new computer. Along with that I upgraded WD and after some mail conversation with Tom he suggested to look through my logfile entries. I found a few inconsistencies. Now and then temp had a leading zero at 10.0 degrees. 010.0? Anyway, cleaned everthing up but I still get the same message as you got and wxsimate close down by itself.
I restarted wxsim on my old machine and made a few tests with exactly the same files. Works perfect!?! So what is the difference. Old computer is a slow Window Vista English 32-bit installation with less memory than the new computer which runs an Windows 7 Swedish 64-bit installation.
I read a few posts regarding this and I looks like data alignment is the most common problem but I do not know. Is there anyone else that could point us in any direction? Tom is kind and still looking into my problem but until then I will continue to run on two computers.
/Labbs
Hi
Check your 92011lg.txt file. The file may be corrupted if data are not aligned.
And also Windy repport some problem with WD build 75 he suggest to use the latest version of WD build 75.
Thanks, but I have checked it.
Also got the latest version of WD. The funny thing is that there are no problems running wxsim on my old computer, accessing exactly the same log files as the new computer does.
a leading 0 on the temperature in the logfile should not cause a problem
( I have been meaning to get around to stopping that though)
Good to hear.
I’ve noticed wd still writes this 0 without casuing any problems on the old computer. It has to be something else… Any special tweaks or permission settings needed to run wxsim smooth on Win7 64-bit?
I had something like this problem. What I did was set wxsim to start a bit later after wxsimate, about 15 minutes, I figured that wxsimate was still writing to the file when wxsim started up and wanted access to it. It worked for me.
Edit: Seems it was a “permission denied”-error, but it might help with this as well.
Link to the thread: http://discourse.weather-watch.com/t/50894
I agree!
Been trying to extend the time between wxsimate and wxsim to get rid of the permission error.
I am also sorry but I did not look at the message thoroughly. The error message I got said it could not write a boolean data. At the moment I’m able to use wxsimate on the new machine but the Import of local data takes ages or at least minimum 10 minutes. Importing and processing the same data on the old machine takes less than 3 minutes. Very strange…
BTW Brian, perhaps wrong thread but I got commas in the log file instead of dots after downloading b77 just now.
BTW Brian, perhaps wrong thread but I got commas in the log file instead of dots after downloading b77 just now.oh that will be a windows regional setting i.e set to use comma instead of decimal place
I changed the way the temperature was being formated, so as to try and get around the problem of the 010.0 for 10 degrees
I will change that code back and re upload build 78
Great Brian, thanks!
I’ll download your next upload immediately.
Do you have any clue regarding my problem: Why it now takes many times longer to import the local logfiles on my “new” wx-computer?
I hopefully can still use the new formating method, but I have added to the code to set the decimal separator as .
in a new .zip update, ready now
not sure on your import of the logfile problem
(except maybe permissions)
Why it now takes many times longer to import the local logfiles on my “new” wx-computer.
Try turning the virus programe and run wxmate (only the local logfiles.
that may cause that. I have never had a slow download from the logfiles andI have in the past had some very slow computers.
Chuck
Brian,
Downloaded and tested - works fine now!
Chuck,
Will try that, have not tested this angle yet, thanks.
No luck I’m afraid. Disabled firewalls, anti-virus and provided ‘Everyone’ full access. Does not crash or hang but still takes more then 10 minutes for wxsimate to process local data.
Can someone send me a log file with which this is happening? Was there some change in a recent release of WD that precipitated this?
Thanks,
Tom
Hi, not any help but…
I too have this problem and have had this since last summer when I changed the computer from XP to Win7.
Has been set up the time between WxSimate and WXSIM to over 20 minutes for it to work. Previously it finished under a minute.
/Bo
Tom,
I’ve mailed you my current logfiles. As I wrote in the forum I have tried serveral things and my own conclusion at this moment is that my new computer has difficulties processing the log files from WD for some reason?!? It does work now but it takes wxsimate 12-15 minutes to download, cull, append wx data. I am trying to work around this by changing the scheduled times. Alos I believe the reason for some of the crashes could be that Startwatch’s crash and hang protection that thought wxsimate has hung.
Could any one tell me their processing times on a similar computer? AMD Athlon II Neo N36L Dual 1.3GHz, 6gb ram and a mirrored 500gb hd and Swedish Windows 7 64-bit
/Labbs
Not much help but my system is a single core AMD Athlon 1.5Ghz with 4Gb ram and running Windows 7 32-bit. My WXSimate download is normally completed within a minute or so and I have no errors showing.
I use System Scheduler to run WXSim & WXSimate, rather than Start Watch (even thought I have SW on the PC). It’s only used to open the programs as I have them both set to auto-close when they have completed their run.
Have you tried running WXSimate as “Administrator”?
Don’t know if this is of any help:
My weather computer is a Dell Dimension P4 3.4GHz with 2GB ram and 500GB HDD.
Download and cull data takes 2min 5sec.
Importing local data takes about 3min 45sec.
I’ve never had the times as low as a minute on this computer.
/Chris
I think it will be important here to distinguish between the download time (from the internet) and the import time (from the WD log files). I can’t think of anything I’ve changed that would affect either. I would like to make sure there’s not anything different about the log files now. If some newer version of WD seems different in this regard, you might try setting the date way back to import old data (assuming log files are not recreated) and compare the download time.
One sample of new log files I received from a user worked fine, importing in just over 20 seconds.
Please let me know what you find!
Tom