I have tested and its working as you want it here
you though need to delete the noaahtm0.txt, noaahtm1.txt, etc files
so that WD recreates them
and puts the
But the NEW problem since version update is remaining.
If I select 8/2008 as date to calculate and then
click on “Update whole month now”, every things for now is OK
The whole month is generated.
Now if I click on “Update daynoaareport.htm”, for the same month
Then ONLY the dates from 01 of the selected month and year
to actual number of the day of actual month is regenerated.
This bug did NOT exist in previous versions.
I can post picts if needed.
Thanks form fixing.
Regards.
[b]1st pict NOAA montly report correctly regenerated for 2008/08
[/b]
2nd pict generation by updatedailynoaa.htm
3rd pict display of dailynoaareport82008.htm with Notepad++
[color=blue][b]Note the calendar date on the upper right part of the PC’s screen. ( 8th of september)
dailynooareport82008.htm goes no further while basic noaa report is OK.
Same result for any month regenerated. Picts available on demand.
I still cant duplicate
I try
noaahtm0.txt and noaahtm2.txt empty
still no problem, noaahtm1.txt contains all 31 days for say august last year (or any year I choose)
Since three days, I have made ALL possible testings ans trouble shootings.
I have installed your last version of WD date 09/09 on TWO computers.
1-) Test computer NOT hooked up to any weather station. Situation OK except that the
HTML tags still remains even after having regenerated x.txt files and removed all HTML tags.
2-) On my official computer same software updates and same configuration.
The problem REMAINS ex: dailynooareport82008.htm still regenerates ONLY up to
day of actual month date.
To be honnest, a couple of tests did succeed after trigering “Records to date for the year”
But if I restart WD the bug comes back and now even if triggering “Records to date for the year”
the bug remains. BUG REMAINS EVEN WITHOUT CUSTOMIZING the x.txt files…!
There is obviously a lack of stability in that process. I understood you could not reproduce the
problem, so what’s next…?
WD is for me unusable if I cannot generate and regenerate normaly 8 years of data.
The official PC is under W7 Ultimate with for now only four softs running?
-WD
-WDmysql
-StartWatch
-FTPGetter (soft that I use for all my FTP uploads except testtags.php and clientraw.txt)
By the way HOW MAY I REGENERATE THE YEARLY NOOA REPORTS???
Please do not forget to respond to that question.
I understand that you are unable to reproduce the problem on your side.
Never the less problem remains on my side and I have reproduced it on
4 ( four) different PCs.
Brian it is NOT because you cannot reproduce the problem that it does
not exist…!
There is also something I am having hard time to understand is that this
thread has been viewed close to 1,300 times and no one has encountered
that same issue and or giving an advice…?
I migh have found a lead to the cause of the problem.
During the initial import of VWS xxx.csv files, there are weird things arrising.
Please look at first three below picts and you will notice
While importing 08 2008, date jumps from august the 8th to september the 8th
this also happens on the import of 082013 (august 2013)
Note that this was tested on 2 differents PCs and 2 versions of WD as it can be
seen upper left of the pict.
On import of 082008, process curiously stops on December the 27th…!!!
This happens on any import tested.
One more time if needed, the last pict shows the dailynoaareport082008.htm generated
only until day of actual date.
Although my xxx.cvs files seem OK, you may use two sample files attached.
These files are extracts of the dbase.csv main VWS file.
Don’t ask me why green thermoters do not go to the end… They never do…!
Please also answer to the question: How do we regenerate NOAA yearly reports…???
I suspect the problem then is related to the data file after the import from VWS data
which is why I and no know one else can duplicate the problem with normal WD data files
Brian good evening,
1-) I provided 2 VWS x.csv data files in my previous post. Did you test them.?
2-) Again: How does one regenerate yearly nooa reports…?
UPDATE a few hours later.
Brian, the dbase.csv file (main data file) generated by VWS could be corrupted OK…???
But I just tested backing up the whole mysql database generated since day one in a .csv
format. I then extracted just one month 082008.csv (coma delimited).
Importing it in WD did EXACTLY the same mess.
One corrupted file I could admit but two, I am realy in doubt…!
I suspect the WD import process to have a problem.
SECOND UPDATE a few hours later.
Picture one: NOAA report recorded by VWS for spetember 2008
Picture two: NOAA report generated by WD for spetember 2008. Both data files (dbase.csv or mysql
data give exactely the same result, no PB with VWS)
Sorry Brian, my x.csv files are NOT corrupted, I opened them with CSVed software and found NOTHING wrong.
May I remind that during the import process by WD, the date change at day 12 midnignt and the end of
process on 27th of december seems absolutely abnormal.
Same remark for dailynoaareportxxxxx.htm generation ending at actual day date.
Still unable to import mmyyyy.csv files from VWS, could you please kindly supply a full month sample file that works on your side.
Please also provide headers for this .csv file
The problem has been fixed by Brain. Everything is fine now,
even with some improvements as long as you may now select
a whole year folder of .csv files as long as there is one
subfolder for each month.