I was curious to see the "Innovative DICOM Medical Imaging" section. I wouldn't have thought that Apple would be interested in niche applications like viewing radiology imaging, but I guess they're probably interested in any cost-insensitive market for these since they're so expensive.
At a local hospital the radiologists have been all Mac for a long long time. They refused to give it up and resisted all attempts to get them to switch. So it doesn’t surprise me at all.
Yeah, in my first job I was an Apple technician for a company that supplied DICOM solutions to radiologist, both in hospitals and standalone.
I thought it was weird they spent so much money on Apple hardware when most of what we sold was servers that would be hidden anyway.
But they do like OsiriX; once a solution is established in those fields, they stick with it, very conservative professions obviously...
Interesting, I would've guessed that they would've forcibly been on Windows since time immemorial.
Entirely unsurprised that someone would refuse to give up their workflow, though! I've rarely found a user with specific needs who wants to change literally anything else about their system, since what they have works for them.
It's probably an easy win for them. It also might have been a good target when they were ideating on specs. Having these pro certifications gives the devices a halo of premium quality.
Regular consumers probably don't buy these displays in bulk, when you can get very nice displays for less than half the price that are 98% the same on specs.
So targeting checkbox-compliance for places like hospital systems is probably an easy win to generating / keeping some long term contracts.
> you can get very nice displays for less than half the price that are 98% the same on specs.
Can you recommend any displays with PPI and brightness equivalent to the studio display, with 120Hz+ refresh rates? I was waiting for this announcement to buy a studio display because I thought they might bring 120Hz to the base model, but $3300 is a lot to spend on a single display. I have an original studio display and a high refresh rate 4K OLED monitor, and they are both compromises unfortunately.
I don't think you can get a DICOM-certified display at 5K and 27" for half the price. Probably like $1k less but that's it - and if you're a radiologist making $300k+ you're not going to want to cheap out on a display.
If you're a radiologist making $300k+ you're going to want to use certified displays so that you don't get sued for using non-approved devices for diagnostic use, and that's going to cost you maybe $6k for a 21" monitor.
Seems to be the expected relatively small refresh, mostly just adding the M5?
The language towards the end of the press release implies to me that they're targeting last-gen Intel MacBook Air users thinking about upgrades more than anyone with an M2/3/4 MacBook.
Echoing a sibling comment, lots of landlords require it now, and the basic packages that insurers offer you as a bundle with auto or other forms of insurance are pretty decent, depending on state.
Typically seems like $100-200 per year for coverage that would handle the loss of most of one's possessions, provided you don't get screwed by "well, you don't have the receipt" or "we only cover water ingress, not floods or leaks".
> But iNaturalist data is often not considered high quality enough to be publishable by itself (wide brush statement) in my field of plant conservation.
As someone who recently started using iNaturalist, I've been curious about this. I think it's an awesome platform and really cool that people can share what they find, etc, but I noticed that people would pile on with species-level IDs on pictures that were obviously ambiguous between different species known to exist in the vicinity.
I of course want as much data as possible to be available to science, but it piqued my interest about whether a negative feedback loop of misidentifications to future identification models could form.
I think GP might’ve been referring to the part of Jeff’s post that references GPS, which I think may be a slight misunderstanding of the NIST email (saying “people using NIST + GPS for time transfer failed over to other sites” rather than “GPS failed over to another site”).
The GPS satellite clocks are steered to the US Naval Observatory’s UTC as opposed to NIST’s, and GPS fails over to the USNO’s Alternate Master Clock [0] in Colorado.
I find this stuff really interesting, so if anyone's curious, here's a few more tidbits:
GPS system time is currently 18s ahead of UTC since it doesn't take UTC's leap seconds into account [0]
This (old) paper from USNO [1] goes into more detail about how GPS time is related to USNO's realization of UTC, as well as talking a bit about how TAI is determined (in hindsight! - by collecting data from clocks around the world and then processing it).
Raspberry Pi seems to have been on a tear of good stuff this year. Lots of activity on both the hardware accessory and software side. I've been following their secure boot provisioning work in particular.
Conveniently for me, they keep releasing things right as I start to have an interest in using that thing.
Networking on Linux in general seems to be very susceptible to "wrong tutorial" in recent years, what with distros switching between different network control suites.
So far, I've been a big fan of netplan (which I guess is tied in with cloud-init?). Dropping a YAML file that declares the network setup I want and lets a swappable renderer make it so on the backend is a nice change from the brittle-over-time series of commands that it took previously.
Yeah, if they had had more altitude, I would guess that this would have looked even more like the AA 191 crash from 1979, with the left wing stalling and causing a roll and pitch down.
That in turn reminds me of the DHL flight out of Baghdad in 2003 that was hit by a missile [0]. Absolutely amazing that they managed to keep it together and land with damage like that.
An important factor in AA 191 is that the engine leaving did significant damage to the hydraulic lines in that wing - including those for the leading-edge slats. At the time the plane was not equipped with any mechanism to keep the slats extended, so after hydraulic pressure was lost airflow over the wings caused them to retract, which significantly lowered that wing's stall speed.
After AA 191 the DC-10 was equipped with a locking system: loss of pressure now results in the slats getting stuck in their current position. The MD-11 will undoubtedly also have this system, so a direct repeat of AA 191 is unlikely.
I did raise eyebrows once of the person in the row behind me. I said I was listening to ATC and that seemed to placate him. I do believe most airlines have a blanket ban on radio equipment, even receive only. Some even ban using GPS!
Many, many, many years ago (before 9/11 and before cell phones were commonplace) I used to carry my ham radio HT and call on simplex (146.52 for those that know) and make contacts. Those were fun times.
I feel for the families with their reactions to people diving to the wreck, especially the fear that it could become a tourist attraction, but people being so upset at the various submersible and diving teams is curious to me.
Of course, you can't know the true intentions of the teams, but they all seem to have gone down there with great respect for the ship as a gravesite.
