Satellites larger than cubesats usually use rad-hardened processors, e.g. in Europe the LEON processors are quite common. These are basically rad-hardened SPARC v8 processors. They are also clocked quite low since they are often implemented using a FPGA.
So, a rather old RISC architecture, lacking any cryptography extensions/intrinsics, running at a rather low clock frequency means that it is not that easy to fit authentication and cryptography in software (at least at the necessary rates).
To get authentication/encryption in these systems you need a separate crypto unit or implement AES-GCM/AES-HMAC in FPGA (if you have room).
My god. This almost brings tears to my eyes. I haven't played games for years. Small children and adult life kind of came in the way... I don't miss gaming that much, but I miss Zelda.
The sheer perfection of the Zelda games are just mindblowing to me. I replayed The Legend of Zelda many years ago and it was obvious that the gameplay was still holding up. They got it right from the absolute beginning. And not only that, it is basically the same gameplay still used (at least up to Twilight Princess which is the last major Zelda game I played. They are so consistent.
Breath of the wild was probably the largest change in the original Zelda formula since ocarina of time (which introduced 3D for the first time)
Based on the trailers I've seen of tears of the kingdom(and I've been trying to avoid that because spoilers) this game walks even further down the path that breath of the wild set out!
We're kind of alike you and I,I think. While I don't have kids that keep me from gaming, I could do without it all, except for Zelda. My switch is currently downloading totk.
A bit meta (sorry): Why do Americans keep calling it abortion clinics? Isn't maternity care center or maternity clinic a bit more suitable. Abortions is just a small fraction of what they do, at least at my corner of the world.
In the North American context, "maternity care" would probably be understood as midwifery, which is not Planned Parenthood's main vocation.
That said, you're correct that Planned Parenthood offers many more services than just abortion, but the category they'd be in is "sexual and reproductive healthcare," not "maternity care."
Many advocates are pushing for "abortion forward" language to de-stigmatize the procedure, and (at least in Canada) some clinics are opting for less euphemistic names.[0]
Because that's what they provide, and that's what they deal in, exclusively. Maternity care centers generally deal with other aspects of pregnancy, though some may also provide abortion services.
I got testicular/prostate cancer screening done at a Planned Parenthood (randomly, it was the closest place offering it) so I'm pretty sure they provide services other than abortions?
Sure, but that is not their primary focus, or historic mission. But what are you going to so with an organization founded by an out and out eugenicist.
Because "abortion" is a hot political issue in the US, and a word that pushes lots of people's emotional buttons. And because anyone using less-button-pushing words to describe things is a for-sure loser in the Darwinian attention economy.
This is pretty uncontroversial in an embedded system context. As others have said in this thread, nothing spectacular happens if STL throws, it just boils down to a std::terminate. You can mitigate this by being careful with what you do with STL.
Also, in a real-time system context, exceptions can be undesirable since they might cause non-deterministic behaviour.
Catching an exception can be surprisingly costly. Did some benchmarking a while ago on the embedded, real-time system I work on and saw that throwing and catching a std::runtime_error had about the same execution time as a rather slow CRC32 calculation (no pre-calculated tables, no special instructions) of a 256 bytes input array. (Of course, this depends a lot of the CPU architecture, compiler, etc.)
You gotta love that Tcl/Tk node based user interface in Max/FTS - something that is still alive today in Pd (Pure Data). Sure, it is clunky, probably not in line with any modern UX design rules. But, at the same time, it is kind of timeless, brutalistic and stylish in all its monochrome ugliness.
Windows Sandbox, together with WSL, have liberated me from VirtualBox/VMware Workstation. So thankful for that. Now I only wait for native USB support in WSL.
"Automavision is a cinematic technique invented by Danish director Lars von Trier.
Developed with the intention of limiting human influence, in Automavision no cinematographer is actively operating the camera. The best possible fixed camera position is chosen and then a computer chooses framing by randomly tilting, panning or zooming the camera. In doing so it is not uncommon that the actors appear in the shots with a part of their face and head cut from the frame. With this technique then the blame for any "errors" are entirely attributable to a computer."
I always felt this was a bit of joke from Lars von Trier, though. I am not aware of any other film than "The Boss of it All" where it was used. A good joke after all. As von Trier says:
"If you want bad framing, Automavision is the perfect way to do it."
"The Boss of it All" takes place in some kind of IT software firm. I'm pretty sure "automavision" is inspired by the kind of online meeting camera which tries (and often fails) to focus on the person talking.
While most of the satire in the movie is unrelated to IT, there are some in-jokes. In one scene, a developer is getting suspicious towards the boss of it all (who is really a hired actor with no understanding of the business) and asks "do you even know what agile development means?" The actor who is trained in improvisational theater cleverly retorts "Well, can you explain what agile development is?", which shuts up the developer.
You could extend this technique to realtime random framing. Shoot everything with a fisheye lens, then screen the film with a player application that randomly crops each scene at runtime (applying correction for the fisheye distortion).
I did recently, and it is still as good as that first time I saw it, together with one other person in an otherwise empty arthouse movie theater. I picked it completely at random, on a day I skipped work, and the whole thing felt completely magical.
A few practical use cases that are not easily covered by similar platforms:
1) Direction finding thanks to the 8x 153 MSPS ADCs and coherent clocks.
2) Mixed domain analyzer: have one daughterboard act as a RF receiver, and at the same time sample an analogue voltage with the other one. This is a capability reserved to the most expensive of test equipment and lets you analyze how a RF switch is behaving (or do side channel attacks?).
3) Sample almost 600 MHz of bandwidth in real time, use the powerful DSP core to run FFTs on it and send the results over to a browser that implements a RTSA display. This lets you have a real-time view of the spectrum around you for just a few watts. Thanks to the double-PPLs on the Granita board, you can also sweep the spectrum very fast.
4) There is enough processing power onboard to enable RFNM as a 5G RedCap node. We are working with NXP to add an eSIM, so with the right software, this can become a fully-functional 5G UE and connect to the normal cell network. Don't care about 5G? You can write your own standard and deploy it on the same hardware (the limitation here is having access to NXP's DSP development tools, which might limit the processing to the beefy i.MX 8M Plus, but some cores will be available as binaries).
5) Technically, anything requiring an insane amount of ADCs and DACs. You can implement your own board, as the heavy lifting (the motherboard) is already done for you. You could prototype something easily with the development board that's on the website and turn it into a real design within weeks.
8x ADCs and 2x ADCs @ 153 MSPS -> 4x RX I/Q pairs and 1x TX I/Q pair. The way the math works, you can sample a 153 MHz signal at 153 MSPS using I/Q, or you can use each ADC line to sample at nyquist, and in that case you get 8x RF channels, each sampling 80 MHz at most. All untested, of course.
Tons of applications and uses in electronic warfare and electronic intelligence gathering.
Also forms a lot of the basis of RADAR, though that's a separate use case.
To oversimplify: SDR allows you to build a radio based around math instead of complex electronics - or, at least fewer complex electronics. It sacrifices a bit of performance but confers a lot of the advantages you get in other software systems - updates, reconfigurability, etc.
Many radio systems are already SDR, just closed. The benefits are the same as building anything into software rather than hardware: you can update it later, support more variations, etc. The downside is more power consumption, so cellphone radios are not usually completely SDR (not an expert on those so correct me if I'm wrong)
This site has some great examples on what various inexpensive SDR hardware can be used for: https://www.rtl-sdr.com/. Use cases range from receiving weather satellite imagery, to reverse engineering radio protocols (e.g. for remote door openers). Several years ago I used an inexpensive DVB USB dongle containing the RTL2832U chip (which enables SDR), to sniff 2G/GSM broadcast packets.
compared to other radio solutions, being able to do more digital analysis on the raw signal lets you do cool things that were previously impossible
at one place, we replaced entire banks of traditional radio scanners using a single SDR
a scanner could only dial into one frequency at a time, but an SDR let us capture entire swathes of the frequency spectrum and extract concurrent streams from multiple sources simultaneously
I'd love to sit down with my Lime and end-to-end my own cell base station... one day
So, a rather old RISC architecture, lacking any cryptography extensions/intrinsics, running at a rather low clock frequency means that it is not that easy to fit authentication and cryptography in software (at least at the necessary rates).
To get authentication/encryption in these systems you need a separate crypto unit or implement AES-GCM/AES-HMAC in FPGA (if you have room).