Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(*) Conduct Stress Tests on 9S and 2B PI's #40

Closed
carlosparadis opened this issue May 19, 2018 · 3 comments
Closed

(*) Conduct Stress Tests on 9S and 2B PI's #40

carlosparadis opened this issue May 19, 2018 · 3 comments

Comments

@carlosparadis
Copy link
Member

You should leave them running overnight with all the sensors ready for both units to ensure they will handle it. I am particularly worried given our concerns on issue #17.

Do you think you could do this before you leave? Things you should watch for are for example:

  • Lagged timestamps (are all readings logging at the same time over time, or are they varying (e.g 1s 2s 1s 2s 3s deltas for the low sampling resolution you are using to average could lead to biased measurements).

  • PI temperature (can it fry an egg?)

Etc.

@carlosparadis carlosparadis added prio:high stat:backlog Draft issue -- needs more refining before it can be worked on labels May 19, 2018
@jygh98
Copy link
Member

jygh98 commented Aug 21, 2018

Running temperature as of today
2B : 42.2C
9S : 51.5
C

Temeprature appears to be running at an ideal temperature and shouldnt be a concern. Interesting to note that 2B runs a full 10*C cooler than 9S, even though 2B is the older raspberry pi.

In terms of logging script stability, only issue so far is #48 and i will need to follow up with ryan on that.

@carlosparadis
Copy link
Member Author

carlosparadis commented Aug 21, 2018

I and Jason went through this issue, and Jason left on the wiki of the Air Quality station how to check the temperature of a Raspberry Pi, so that is checked.

Second, the PIs have now been running for the entire summer, so they clearly can hold on temperature and also on stress.

What is left is to do the lagged time check, which is basically to verify every second sampling (before it averages out to the minute) is consistently every 1 second, or if it goes off every now and then. Specifically, the function that collects the every 1 second reading would be also collecting the timestamp offset (i.e. if it is more or less than 1 second) and report on average for the 5 minutes time window, how often on average the second-level sampling is.

Of the 4 tasks that we agreed upon for this 2 weeks, this is the one of lowest priority.

@carlosparadis carlosparadis changed the title Conduct Stress Tests on 9S and 2B PI's (*) Conduct Stress Tests on 9S and 2B PI's Aug 21, 2018
@carlosparadis
Copy link
Member Author

For the record, there was not enough time to finish this one, however the main concern for the stress test was to see if the PI was gonna fry, which has been fine for now over 3 months, so its OK.

There is still a minor missing request here, so I will leave the issue open for now.

@ghost ghost removed the stat:backlog Draft issue -- needs more refining before it can be worked on label Sep 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants