[x] increase total rows for each simulation (App, Network, and Device Log) to >100
[x] ensure that simulator completes all file generation within 1 minute run-time
^^ This is the priority task. Having this run will enable @lydia-wu to meet client expectations for next Wednesday's V.2.0 Demo
[x] increase total devices from 2 to 5
[x] create randomized "hiccups" in the simulated files (i.e., miss 1+ rows/"heartbeats" at least once for at least one device)
[x] create randomized "duplicates" in the simulated files (i.e., have the file "accidentally" repeatedly print out 1+ rows/"heartbeats" at least once for at least one device)
[x] make one device have "jitter" (excess communication compared to the other devices) (i.e., if you've coded the "normal" device to send a message every 10 seconds, have one send out every 3 or 5 seconds)
htyuki
commented
2 years ago
DUE
Friday 2022-02-18 @12PM ETRationale
this will fulfill
build 2.0that so that the PBI and ELK solutions can reflect more complex data.Foundation
Build off of #35 files (also found in cadence repo) (see attached zip of @hunter-alloway's email for details). RE ENGR482 Cadence Data Simulator-Version 1_5.zip
New features:
[x] increase total rows for each simulation (
App,Network, andDevice Log) to >100[x] ensure that simulator completes all file generation within 1 minute run-time ^^ This is the priority task. Having this run will enable @lydia-wu to meet client expectations for next Wednesday's V.2.0 Demo
[x] increase total devices from
2to5[x] create randomized "hiccups" in the simulated files (i.e., miss 1+ rows/"heartbeats" at least once for at least one device)
[x] create randomized "duplicates" in the simulated files (i.e., have the file "accidentally" repeatedly print out 1+ rows/"heartbeats" at least once for at least one device)
[x] make one device have "jitter" (excess communication compared to the other devices) (i.e., if you've coded the "normal" device to send a message every 10 seconds, have one send out every 3 or 5 seconds)
[x] add deliberate fluff in the
Device Log