Home › Forums › Monitor My Watershed › Gaps in my data
- This topic has 2 replies, 3 voices, and was last updated 2024-09-17 at 9:33 PM by neilh20.
-
AuthorPosts
-
-
2024-09-12 at 5:33 PM #18647Hello,
We set this Mayfly up in 2022 and have had relatively no issue with it but now as I look at the website it shows gaps in my data. I checked everything out in person and there seems to be no is
Hello,We set this Mayfly up in 2022 and have had relatively no issue with it but now as I look at the website it shows gaps in my data. I checked everything out in person and there seems to be no issue with the equipment. I am guessing that maybe it is related to the cellphone service? When these gaps in data happen, does the Mayfly adjust and close the gap in the data some how? Thanks in advance.
Mayfly data link:
-
2024-09-12 at 8:14 PM #18648No, the Mayfly datalogger doesn’t know if any data is missing from the website, it just tries to send it every 5, 10, or 15 minutes (or whatever interval it is programmed for). If the data doeNo, the Mayfly datalogger doesn’t know if any data is missing from the website, it just tries to send it every 5, 10, or 15 minutes (or whatever interval it is programmed for). If the data doesn’t get to the website database, the logger won’t know, and doesn’t send any old data to fill in the gaps. You’ll need to visit the station and manually retrieve the onboard memory card to see what was recorded when the station wasn’t transmitting. That visit also will give you a chance to clean the sensor and assess whatever physical problem might be causing the data outages. My first guess would be a malfunctioning battery pack, so if you’ve got a spare fully-charged pack, swap that out when you swap out the memory card. Then check the datafile to see what the battery voltage and cell signal strength are during the samples that weren’t transmitted. You can also manually upload the datafile to MonitorMyWatershed and it will auto-fill in missing gaps.
-
2024-09-17 at 9:33 PM #18657@tumayflybearriver – thanks for brining it up. Its nuts, but looks to me like the signature of “thrown away data” by ModularSensors software that runs on the Mayfly, and the@tumayflybearriver – thanks for brining it up. Its nuts, but looks to me like the signature of “thrown away data” by ModularSensors software that runs on the Mayfly, and the ODM2 software on monitormywatershed.
I’ve raised the issue of reliable delivery in 2018, and implemented it on my systems and offered it to the mainline ModularSensors
The story https://github.com/EnviroDIY/ModularSensors/issues/194
https://github.com/ODM2/ODM2DataSharingPortal/issues/485
At the request of some SWRC parties last year I submitted it to ModularSensors main software, but other priorities came up and it seems it was abandoned when it was nearly integrated into the mainstream.
Otherwise, to verify for your specific node, Shannon is right. Its looking at what is stored on the csv file and is that data on line. Might be just easier to use the .csv periodically. If its on the .csv and not MMW – then it was collected and “thrown away” by the software.
I’ve done it with my tests systems that where local to me – and it was a lot of work to get my forked version of ModularSensors reliable. I’m very happy with the data that my systems as part of TU N california are collecting.
The story for my TU systems in N California .. https://www.envirodiy.org/n-ca-mayflys-through-the-winter-storms/
Its great that ModularSensors is open source, and I’m very happy with my fork which anybody else can use as well .. https://github.com/neilh10/ModularSensors/wiki
happy to chat about what I think it takes to improve system reliability if interested, but you can also look at my blogs on it over the years 🙂
-
-
AuthorPosts
- You must be logged in to reply to this topic.