larryjw
About
- Username
- larryjw
- Joined
- Visits
- 199
- Last Active
- Roles
- member
- Points
- 3,338
- Badges
- 2
- Posts
- 1,040
Reactions
-
Apple says hardware leaks harm consumers
-
Most analysts got Apple's Q3 2021 wrong -- here's what they predicted
-
Apple Watch 'black box' algorithms unreliable for medical research [u]
NASEM (National Association of Science, Engineering and Medicine), formerly just NAS, issued a report in 2019 requested by Congress, on Reproducibility and Replication in Science. I'd highly recommend it.
The report distinguishes Reproducibility from Replication. To reproduce is to take the original data and reanalyze it, sometimes also using the same software used in the original study. Replication is duplicating the original study -- different researchers, different conditions, etc.
The NASEM report notes that software used by researchers are subject to change (black boxes, if you will) and this can alter results of studies. Software like R, SAS, SPSS, etc are often updated.
Frankly, I'm not at all clear what these paragraphs from the above article mean:
"Two sets of the same daily heart rate variability data collected from one Apple Watch were collected, covering the same period from December 2018 until September 2020. While the sets were collected on September 5, 2020, and April 15, 2021, the data should have been identical given they dealt with identical timeframes, but differences were discovered.
It is thought that tweaks by Apple to algorithms used in the Apple Watch changed how the data was interpreted before being collected. "
A set of data from December 2018, and another set from September 2020? Why should data have been identical? What am I not understanding? Did they really take some raw data from December 2018, and pass it through two separate algorithms and found a difference in how that data was interpreted?
In any case, I don't take my Apple Watch results that seriously. I expect a lot of variation. Where on my wrist I wear it, software upgrades, skin changes, sweat, environment, different watch with different sensors. Big picture trends is the only thing that I would expect would count, not absolute values. I have no clue as to the error bars of the Apple Watch. Using medical quality devices would be ideal, but nobody wears them for 20 hours per day over years -- medical equipment is used over a few days or a few minutes -- quite limited in value even if perfectly accurate.
-
NSO Group CEO says law-abiding citizens have 'nothing to be afraid of'
-
Apple to remove popular DOS emulator for iOS from App Store
Rayz2016 said:larryjw said:I think Apple's guideline rejecting executing code is needs to be eliminated -- an emulator is an emulator.
In reality, executing code in an emulator is what programs do. For example, PDF files are themselves computer programs which instruct and iPad how to render a PDF visually.
Isn't programs as data and data as programs the basic principle of computing?The emulator allows apps to run code that can’t be seen or examined by Apple, and that has always been against the rules. PDFs, the other hand, are pretty benign. It would be quite hard to piggyback an App Store in a PDF document.So the real problem is the lack of consistency in applying the rules. This should never have been allowed in the App Store in the first place, so they’re going to look like real dicks for removing it now.A previous commenter also suggested that a program must be executed on the CPU. That’s also not correct.
In designing systems, one is always trading off between the “executable” and the “data”. Different languages tend to encourage marking the boundaries differently, but it remains that these boundaries between data and executable are quite arbitrary.In a micro programmed CPU, your “executable” is just data. To the hardware guys, the micro program is just data which drives NAND gates and voltage changes.