Cumulus Support

I recently upgraded CumulusMx and Utils. I've noticed that the monthy records in MX do not go back before the month that I upgraded. It is working in Utils however. How do I regenerate these records?

Check your start date is set to the date you started taking readings.

StartDateIso=2017-03-20

I seem to be able to use the admin editor to edit the records. Is there no other way?

Not sure what you mean by "other way". The Editors in MX allow you to alter most data within the various files maintained by MX, so what else do you need to edit?

Instead of manually editing each field in all the records, isn't there a way for cumulus to fill in the fields? In other words regenerate the monthly/yearly /alltime records automatically.

Have you tried the function in the top right hand corner to read the monthly record data (can take some time depending on the amount of data) and then use those results to populate the incorrect fields?

GaxUser wrote: ↑Thu 06 Jul 2023 12:09 am Instead of manually editing each field in all the records, isn't there a way for cumulus to fill in the fields? In other words regenerate the monthly/yearly /alltime records automatically.

No there is no way to recalculate the records by the machine, manual editing is the way.
(afaik)

But I don't think it is not the StartDateIso nor the records, changing the records does not solve the problem. There must be something else wrong because the daily rain and sun hours charts don't go beyond June either and that is not correct. Could you post the MXdiags file with debug/dat switched on? We definitely can be sure the data is there as CUtils uses them (which uses several other techniques)

I just realised I may be wrong about the charts but I still am not sure about the cause because the records should have been there.
Are you sure the records were there before the update of CMX?
Did you move all files in the data directory? Do you still have a backup of the inifiles (like alltime.ini) from before the update?
And note that you have several extreme data in your database (zero temperature and pressure etc...).

I'm afraid I don't remember the steps I used to upgrade. I effectively created a new install. i.e. new directory and copied over the data files. I do have the original .ini files.

The MXdiags files have many "LogFluentFtpMessage: Error = Object reference not set to an instance of an object." errors. If I understand correctly that is a different bug, and are false errors? I've turned off ftp logging for now.

Thanks for pointing out the data extremes (different issue). Seems gaps in the data record can cause 0's for some fields.

GaxUser wrote: ↑Thu 06 Jul 2023 5:16 pm I do have the original .ini files.

Copy the current CumulusMX directory to a safe place and copy the old ini files to the current installation.
If that does not work restore from the copy you made.
It could well be you just started over with new records because it did not have the ini files (the records database). Restoring the original ini files from before the update is worth a try.

Excellent, that did the trick. Thanks for all your help.