Graphs source data

[oldeflyer]

Hello,
Running Current MX on a Raspberry Pi.
I am looking for information on where the Graphs get the one minute data that is displayed.
I see the five minute data in the datafiles but cannot locate the one minute data.

Thanks for any information,

Wayne

[Big Daddy]

I think this may be determined by the Log Interval settings under Settings / Station Settings / General Settings / Log Interval.

I have mine set to 1 minute and the data in the json files used for graphing shows every minute.

I think the default setting is 5 minutes

Here is a sample of my tempdata.json file which shows the 1 minute interval

[
1675090980000, (Converts to Monday, 30 January 2023 15:03:00)
9.0
],
[
1675091040000,(Converts to Monday, 30 January 2023 15:04:00)
8.9
],
[
1675091100000,(Converts to Monday, 30 January 2023 15:05:00)
8.9
],

Andy

[oldeflyer]

Hey, Big,
Thanks for the reply.
My station and MX settings are the same at five minutes.
When I go to graphs I get data points from somewhere at one minute intervals.
BTW, I am using a Davis ISS and a Vue Pro 2.

[freddie]

When MX is running it records one minute data for the graphs and stores it in an internal SQLite database. If you have MX switched off for a period of time then switch back on, the graphs for the period of your switch-off will be generated based on your interval setting, as that is what is available in your Davis logger.

A way around this is to have the interval setting set to one minute. This means graphs will look identical whether generated from live or interval data. The drawback is that your Davis logger will then only store about 2.5 days worth of records if MX is not running, compared to about 12.5 days when using a 5 minute interval.

[oldeflyer]

freddie,
That is EXACTLY the information I was looking for. Thank you!

Is there some comprehensive source that documents the MX internals?
I know most people just want the weather data, but I am a long time computer programmer (Fortran) and I would like to know about the MX guts (so to speak).
Wayne

[freddie]

Source code is on GitHub: https://github.com/cumulusmx/CumulusMX

It is written in c# which is pretty easy to follow.

[HansR]

@oldeflyer:

Source code is on GitHub: https://github.com/cumulusmx/CumulusMX

It is written in c# which is pretty easy to follow.

I would not call the source code self-documenting so the nearest to real documentation is the wiki which is in kind of disarray atm but it served me well for info. More than the code itself which is some 85.000 loc.

But of course, take what you need for documentation.

[oldeflyer]

freddie,
Looked in Github. Just for grins. I don't do C#. Me Fortran:-)
I programmed data collection at a nuclear plant for about 35 years and guess I'm stuck with what I know.

HansR, I did look at the Wiki but found it somewhat chaotic. Picked enough out of it to get the MX up and running on a Raspberry Pi. That was pretty much rote. Now I want to know some of the HOW and WHY.

Thanks to all,
I will keep looking.
Wayne

[SamiS]

HansR, I did look at the Wiki but found it somewhat chaotic. Picked enough out of it to get the MX up and running on a Raspberry Pi. That was pretty much rote. Now I want to know some of the HOW and WHY.

A lot of description about functionalities is buried in these forum discussions, so search may give some insights. Unfortunately there have not been too many volunteers creating content to the wiki during the years. Browsing through the version history thread will probably answer some questions, as Mark has usually provided at least some information about new or enhanced features. Of course this won’t cover things that already existed and have not changed after Mark took over the developement when Steve retired.

—
Sami