This has probably already been asked...

[water01]

but I have some spurious readings that caused an all time low temperature record early this morning (3rd Sept). I used to know how to adjust these in Cumulus 1 with the editors but how do I do it in Cumulus MX?

[uncle_bob]

Probably with a text editor. I really like Notepad +

[steve]

Yes, there are no editors in MX yet, so you'll have to either use a text editor, or load the data into an installation of Cumulus 1 and use the editors in that.

[water01]

I have fixed everything except This Month and September Monthly records. What files do I need to edit to fix that is it monthly .ini and monthlyalltime.ini?

[steve]

Yes, but month.ini rather than monthly.ini.

[water01]

Steve where does Cumulus MX pick up #MonthAppTempL from as I cannot find where it is getting the figure from?

[steve]

From the [AppTemp] section in month.ini

[water01]

OK I am stumped!!

As you can see this picture is part of the monthly record for September from Cumulus MX interface.



You can see the spurious temps but if you look at yesterday



So CumulusMX is getting them from somewhere and putting them into cumuluswebtags.php

I have checked both month.ini and monthlyalltime.ini and they are NOT there so where are they coming from?

[water01]

I have found them in a file called tempdatad3.json, could it be getting them from there?

[steve]

I'm confused now, can we clarify exactly which item(s) you are trying to correct? You mentioned <#MonthAppTempL>, and that is the low apparent temperature for the current month. That figure is read from the [AppTemp] section (the "Low" item) of month.ini at startup, and then maintained in memory (and month.ini updated) if the record is broken while Cumulus is running.

Your screen shot is of the all-time September record. This is read from the [Temperature09] section of monthlyalltime.ini at startup (the lowapptempvalue item), and then maintained in memory (and monthlyalltime.ini updated) if the record is broken while Cumulus is running.

This all assumes that there isn't a bug in MX, but I haven't noticed anything odd myself, and no-one else has reported a problem.

[water01]

OK maybe it is because I didn't realise it was maintained in memory and I have to restart MX after I fixed the files!!

[water01]

Sorry to be stupid that fixed it. Didn't realise as I said it maintained it in memory, so I a reload of the program after I fixed the file did it!!

Extremely sorry for wasting your time, I am an idiot.

[steve]

They are INI files, they are read at startup only. They are not constantly re-read, Cumulus has no way of knowing that you have edited them. They should be edited with Cumulus stopped, as Cumulus may write to them at any time and overwrite your changes.

[water01]

Understood. At least it was a useful learning exercise on MX. Are the old Cumulus 1 editors low down on the development schedule

[steve]

They're high up, really, probably the next thing to do. I'm just currently lacking the enthusiasm/motivation to start on a large piece of code, and spend more time on Cumulus than the 1 or 2 hours a day (development and support) that I do already.