×
RadLog
Edit Long Term Trend?
2 weeks 5 days ago #7032
by Bert490
Replied by Bert490 on topic Edit Long Term Trend?
I left out the bit that made it work for me (oops). I renamed the .xml file so Radmon failed to locate it. That's what seems to have triggered the regeration from the .txt file (there was a delay after clicking the Long Term tab). So it seems there are 2 ways to do it; edit the .xml, or edit the .txt and delete/rename the .xml.
As for locating the max value, I opened the file in a spreadsheet such as Excel, and used the data filtering option. The CPM max is at the bottom of that pull-down. The .txt file is easier to edit, as the 9 values are on the same line separated by commas. I found the .xml file had 9 separate sections, requiring 9 searches for the same xValue.
As for locating the max value, I opened the file in a spreadsheet such as Excel, and used the data filtering option. The CPM max is at the bottom of that pull-down. The .txt file is easier to edit, as the 9 values are on the same line separated by commas. I found the .xml file had 9 separate sections, requiring 9 searches for the same xValue.
The following user(s) said Thank You: Simomax
Please Log in or Create an account to join the conversation.
2 weeks 4 days ago #7034
by Simomax
Replied by Simomax on topic Edit Long Term Trend?
Good stuff Bert490. Thanks for that. I think with both options it will allow other users to have a go at editing their long term trend graph. That is if they are using radlog.exe, and I'm really not sure how many people are these days.
Please Log in or Create an account to join the conversation.
1 week 5 days ago - 1 week 5 days ago #7038
by GetSirius
Mineral Point radiation/lightning monitor: getsirius.com/radiation
Replied by GetSirius on topic Edit Long Term Trend?
Thank you to everyone who has offered help with this issue!
I first tried editing longtermtrenddata.xml but I was unable to find the offending data point. I could not figure out how to decode the numbers that were in the .xml file (several years long). After that, I tried to edit the .txt file and that was easy enough to find and edit my bad data point. Renamed the .xol file, changed the .txt file, and my result was a long term graph for one day, then two days, etc.
I found it odd that my .xml file now has a different format than the one I renamed/hid. Examples below:
Used to look like this:
Now looks like this (well, last checked a couple days ago):
I first tried editing longtermtrenddata.xml but I was unable to find the offending data point. I could not figure out how to decode the numbers that were in the .xml file (several years long). After that, I tried to edit the .txt file and that was easy enough to find and edit my bad data point. Renamed the .xol file, changed the .txt file, and my result was a long term graph for one day, then two days, etc.
I found it odd that my .xml file now has a different format than the one I renamed/hid. Examples below:
Used to look like this:
<Chart BackColor="24, 15, 1">
<Series>
<Series Name="CPM mean" Legend="Legend" XValueType="DateTime" ChartType="Line" ChartArea="Main graph" Color="255, 254, 230">
<Points>
<DataPoint XValue="44329.827862210645" YValues="151.068797776234" />
<DataPoint XValue="44330.827859178244" YValues="158.755555555556" />
<DataPoint XValue="44331.827859386576" YValues="176.774305555556" />
<DataPoint XValue="44332.827829085647" YValues="174.80625" />
<DataPoint XValue="44333.827829293979" YValues="207.722916666667" />
<DataPoint XValue="44334.827829479167" YValues="253.580555555556" />
<DataPoint XValue="44335.827829710652" YValues="324.122916666667" />
<DataPoint XValue="44336.827829780093" YValues="300.33125" />Now looks like this (well, last checked a couple days ago):
<Chart BackColor="24, 15, 1">
<Series>
<Series Name="CPM mean" Legend="Legend" XValueType="DateTime" ChartType="Line" ChartArea="Main graph" Color="255, 254, 230">
<Points>
<DataPoint XValue="45572.835862719905" YValues="54.7265787647467" />
<DataPoint XValue="45573.835862939814" YValues="48.3275503122831" />
</Points>
</Series>
<Series Name="�Sv/hr mean" Legend="Legend" XValueType="DateTime" Enabled="False" ChartType="Line" ChartArea="Main graph" Color="255, 254, 230">
<Points>
<DataPoint XValue="45572.835862719905" YValues="0.311941504292319" />
<DataPoint XValue="45573.835862939814" YValues="0.275467041484355" />
</Points>
</Series>
<Series Name="mR/hr mean" Legend="Legend" XValueType="DateTime" Enabled="False" ChartType="Line" ChartArea="Main graph" Color="255, 254, 230">
<Points>
<DataPoint XValue="45572.835862719905" YValues="0.0311941485683964" />
<DataPoint XValue="45573.835862939814" YValues="0.0275467024989411" />
</Points>
</Series>Mineral Point radiation/lightning monitor: getsirius.com/radiation
Last edit: 1 week 5 days ago by GetSirius.
Please Log in or Create an account to join the conversation.
1 week 5 days ago - 1 week 5 days ago #7039
by GetSirius
Mineral Point radiation/lightning monitor: getsirius.com/radiation
Replied by GetSirius on topic Edit Long Term Trend?
Perhaps in the future if Radlog gets updated it would be nice to include a feature that is able to automatically and/or manually remove way out of range data points.
I am not a good coder, but several years ago I was able to put together some PHP that reads data from daily Radlog uploads and makes an hour by hour graph once per day using dygraphs . One can zoom into any part of the graph to see detailed data. I included code to throw away far out of range data. Out of range number is manually set and does not remove zero readings. If data is out of range for X number of readings, it is not thrown away. It appears to work, somewhat... I compressed the graph for this example, it looks better on a larger screen.
I am not a good coder, but several years ago I was able to put together some PHP that reads data from daily Radlog uploads and makes an hour by hour graph once per day using dygraphs . One can zoom into any part of the graph to see detailed data. I included code to throw away far out of range data. Out of range number is manually set and does not remove zero readings. If data is out of range for X number of readings, it is not thrown away. It appears to work, somewhat... I compressed the graph for this example, it looks better on a larger screen.
Mineral Point radiation/lightning monitor: getsirius.com/radiation
Last edit: 1 week 5 days ago by GetSirius.
Please Log in or Create an account to join the conversation.
1 week 4 days ago #7040
by Simomax
I think the reason it started from scratch is because you renamed the xml, so radlog created a new one and I have a feeling that data is only written to it once a day, or graphing period. After much messing about and chatting with Dan, I don't think the long term xml file is generated from the long term text file. From what Dan said, the text tile is just an easier-to-read version of the xml, that actually does nothing. Or may be a part of shared data or something, but doesn't seem to be related to the long term xml data.
Do you still have your original xml and long term trend text files? If so you could upload them to the forum here, along with your most recent xml and I could have a look at finding the spike and then merging your latest long term data with your original data.
Replied by Simomax on topic Edit Long Term Trend?
I don't think the format is different. I think it has just compressed down the sections as you now only have two days of data there, so is showing the nine sections closer together.I found it odd that my .xml file now has a different format than the one I renamed/hid. Examples below:
I think the reason it started from scratch is because you renamed the xml, so radlog created a new one and I have a feeling that data is only written to it once a day, or graphing period. After much messing about and chatting with Dan, I don't think the long term xml file is generated from the long term text file. From what Dan said, the text tile is just an easier-to-read version of the xml, that actually does nothing. Or may be a part of shared data or something, but doesn't seem to be related to the long term xml data.
Do you still have your original xml and long term trend text files? If so you could upload them to the forum here, along with your most recent xml and I could have a look at finding the spike and then merging your latest long term data with your original data.
Please Log in or Create an account to join the conversation.
1 week 4 days ago - 1 week 4 days ago #7041
by GetSirius
Mineral Point radiation/lightning monitor: getsirius.com/radiation
Replied by GetSirius on topic Edit Long Term Trend?
Thank you for the generous offer! I had not realized/noticed that the data was set up in 9 sections, it all makes some sense to me now.
I just went through the .xml file line by line again and found this in the µSv/h section:
<DataPoint XValue="44678.682294444443" YValues="4.74670369340925E-05" />
<DataPoint XValue="44679.682294652775" YValues="0.000268979876067575" />
<DataPoint XValue="44680.682304803238" YValues="0" />
<DataPoint XValue="44681.682295266204" YValues="0" />
<DataPoint XValue="44682.682234282409" YValues="1.18667593950989E-05" />
Do you suppose the E-05 values are my offending data points? I did not see out of range data in the CPM section for the same XValue.
I just went through the .xml file line by line again and found this in the µSv/h section:
<DataPoint XValue="44678.682294444443" YValues="4.74670369340925E-05" />
<DataPoint XValue="44679.682294652775" YValues="0.000268979876067575" />
<DataPoint XValue="44680.682304803238" YValues="0" />
<DataPoint XValue="44681.682295266204" YValues="0" />
<DataPoint XValue="44682.682234282409" YValues="1.18667593950989E-05" />
Do you suppose the E-05 values are my offending data points? I did not see out of range data in the CPM section for the same XValue.
Mineral Point radiation/lightning monitor: getsirius.com/radiation
Last edit: 1 week 4 days ago by GetSirius.
Please Log in or Create an account to join the conversation.
Moderators: Gamma-Man
Time to create page: 0.165 seconds