HN user
RISC-V is a family of instruction sets (which have various chips implementing them). Think "X86-64". It looks like the baochip-1x is using the VexRiscv CPU. The HDL is available here under MIT: https://github.com/SpinalHDL/VexRiscv
It is much like a game might use a physics engine, or a new language might use the LLVM backend. To overly simplify, a CAD kernel will keep a list of operations (make a cube of this size here, drill a hole of this depth here, round these edges but not those). And combine that into a final volume. These responsibilities only get more and more complex as a part gets more complex - so using a pre-built engine allows CAD software to focus on tools and workflows to translate human instructions into lower-layer kernel geometry: the UI/UX. It also crosses into compatibility, if you use the same Kernel as another CAD it is much simpler to export/import from them. Otherwise you would have to reimplement their kernel (or enough of it), or be stuck exporting triangulated versions of the final volume - sort of like converting an image from vector to raster.
We even use aluminium on "dumb" transformers for power transmission. Dry-type transformers tend to be physically larger because they use air and resin (rather than a tank of oil) to insulate, and so the major downside to aluminium conductors (needing a larger cross-section to carry the same current for the same loss) is no longer a limiting factor performance-wise. In most substations, and extra 20-30% physical size of the transformer is a fine trade-off for cheaper construction.
I think the issue might stem from the fact that (as I read it) the essay is talking about "for the people who are moderate (in the middle of the left/right axis), some are distributed higher on your graph, while some are lower". Which says nothing about "for the people who are distributed higher on the graph, how many are in the middle of the left/right axis". Your graph makes explicit an answer to the second question which the essay avoids. (There is a bit of an implication in the last two paragraphs, but PG is explicit it's only about people he knows).
A well-actually is when you correct someone about something that’s not relevant to the conversation or tangential to what they’re trying to say.
So, as long as the conversation is about the colour of the sky, (or about green things) you can just answer it.
I missed it on the first read-through but there is a link to the code used to run the simulations in the first appendix.
Homegrown python code (i.e. not a library), very nicely laid out. And would form a good basis for more experiments for anyone interested. I think I'll have a play around later and try and train my intuition.
This Vimcast (http://vimcasts.org/episodes/converting-markdown-to-structur...) recording is an example of a quite complex macro for converting (a specific file's) markdown to HTML. At the beginning of the video you see that they save the macro to the "a" register. You can record macros of similar complexity to each of the other letters of the alphabet, to get some idea of the maximum complexity (though I tend to stick to about 3 or less in a single session).
If anyone is wondering where 2.08 comes from like me. First we consider the case with no GST, where the gross-up multiplier is x1.8868 ($1887). This is the pre-tax earnings at 47% required to get a post-tax benefit of $1000. i.e. $1887 x (1-47%) = $1000. With some algebra and setting the top marginal tax rate to R, and the Gross-up to G: G=1/(1-R). The idea is the Government gets its cut either way, there is no tax benefit (for employees in the highest bracket, and actually a net loss for employees not in that bracket).
If the employer can claim back GST (currently 10%) on the original purchase, the formula for G becomes G=1/(1-R)+(1/11)/R. To account for the extra 10%/110% that the employer can claim back.
I'd argue that the steelman position might be: "Understand the treatment dynamics". Treating a linear-response in the vitamin deficiency case with a binary threshold, and treating the bifurcation point in exponential battles (infection, cancer) as linear are the same class of error (just in opposite directions).
Still as another response noted, almost all of the examples are success stories of medical science, so I don't know if there is a wider point of "medical science/practice is slow to notice these nuances" or if it is just a collection of cool examples of "hey: sometimes doing a single treatment MOAR/multiple treatments simultaneously has a counter-intuative result, isn't that neat."
I've heard "pixels" used generically to refer to the bundle of tracking code from a particular vendor in the marketing department at work. e.g. "Have you enabled the Facebook pixel?" means have you embedded the JavaScript snippet (usually with a fallback 1x1 pixel) that Facebook provides for tracking.
Reminds me of [0].
At work we tend to create backronyms for/from the cute names which is our way of having our cake and eating it too.
[0] https://youtube.com/watch?v=y8OnoxKotPQ&si=EnSIkaIECMiOmarE
This doesn't match with my experience. I have a single catchall *@my-domain.com address that will receive anything sent to the domain (without setting up separate accounts ahead of time).
You can also send from any address, but I agree that the UI is a bit hidden. You first choose from the from-address dropdown "*@my-domain.com", and then a new textbox appears where you can type what address to send from. As another commenter pointed out, if you are replying to an email it will automatically fill in the custom from-address, but you can overrule it.
I've used IronCAD, Solidworks, pro/e and AutoDesk Inventor. If you're approaching 3D modelling as a draftsperson, IronCAD was much more productive. Want to change this part, just do it. Want to specify a relationship, you can but it's entirely optional. It's hard to describe how much faster it becomes. This was particularly noticeable in the hands of our 2D drafties who converted.
But I have also had the joy of trying to program IronCAD. The parametric solver is not as good as the other programs (who live and die by it). I suspect, though cannot prove, that the little automation system we used to create a base design would have been a lot more stable running on a different system. But it was too much work to completely re-implement (and convert all the old designs etc.). So I had the joy of fixing changes between versions by e.g. swapping the direction of a constraint, or hard-coding an initial offset so that you approach a solution from a particular direction.
Also, adding 2D annotations to create a production drawing were painfully slow and finicky in IronCAD.
I think I agree with the author that history-based editing caused the whole industry to go down a less-efficient path, but I also think it's too late to change the past now.
I think something like the Games Workshop/Warhammer 40k approach would work well here [1]. Lego has enough settings/worlds to hand off to different studios, and you have all the high-profile partnerships (like Star Wars, Harry Potter, Marvel) that you can hand to the successful teams.
Lego Star Wars is fun, but is exactly the same game as all the other Lego tie-in games.
For more information, the parent PDF describes a similar process using reflection discovered in China.
If you cast and polish a bronze mirror with raised letters/shapes on the back, the very slight deformations caused by polishing over the different thicknesses will create an image in the reflected caustics, despite the fact that the mirror appears smooth when using it as a mirror.
I'll try to give my perspective, though it's mostly expanding on em500's [1] 3rd paragraph. I think you're asking the wrong question about prophet - most users don't care "how good is it?" but instead "is it good enough?", and then "how easy is it to use?"
Prophet solves a broad class of easy problems that a lot of ordinary businesses have: you have several years of basically regular data (sales or page views or store foot traffic) that you know has yearly/weekly/daily (if you have sub-daily data) cycles, and you want to give a reasonable prediction to the business so they can plan for the upcoming week/month/year. And you want to remove the periodic effects so you can see the underlying trends.
Imagine someone, lets call them Bill, who might be called a data scientist, or business analyst or just assistant operations manager, for a medium-large business. Bill has the last 5 years of sales/views/traffic data in the database (anything before that is in a bunch of excel spreadsheets on the share drive), and knows just enough python to be dangerous. Bill can probably explain an R-squared value but is not an expert at statistics by any measure. He wants to fit the data, but has several problems:
1) the weekly trend does not line up with the yearly data, as the year starts on a different weekday.
2) Those damn public holidays, some of them occur on a specific date, some of them on the "first Monday of the month", and some of them seem to change almost randomly year-to-year.
3) The reporting system was down for a couple of weeks in June and Feb last year, and the numbers for the first few years were copied from excel, so sometimes are missing the first or last day of the month.
Prophet comes by default with yearly/weekly seasonality. Prophet comes out-of-the-box with a simple way to import holidays, and even a way to specify your own. Prophet doesn't require any cleaning, or special procedures to deal with missing data. And it is quick and easy to use, and get nice-looking, broadly reasonable graphs out (with the above mentioned, consistent data). And that solves the business problem.
And Bill's probably heard of it because it is (a) popular already, and (b) has Facebook's name attached.
That's my take as to why, even if it is not even close to the most accurate method, Prophet is so broadly popular.
There is a little more information in this hackaday article [1]. Both propellers have swashplates like a helicopter which allows them to control the pitch of each rotor.
[1] https://hackaday.com/2020/09/02/an-up-close-look-at-the-firs...
The sum of all positive integers can be somewhat described as negative one twelfth: https://www.youtube.com/watch?v=E-d9mgo8FGk
I really enjoyed running through Write Yourself A Git[0], which guides you through implementing a basic Git replacement in python.
And Microsoft with recent additions to Office. The larger icons in the ribbon at least have splashes of colour, but the quick access toolbar is entirely monochrome.
I'm also not an expert: based only on my reading of Wikipedia, you are correct and it is bonkers from a US perspective.
The photographer may be in breach of Twitter's ToS for enforcing their moral rights, but that would not _stop_ them from enforcing their rights. In this case, the initial post to twitter was not from the photographer, but someone else. So Twitter likely has nothing to hold against the photographer.
There is. Japan's "copyright" laws are different and include Moral rights (https://en.wikipedia.org/wiki/Copyright_law_of_Japan#Moral_r...) which are nontransferable and include the right to how your work is attributed.
I'm not sure why it is the retweeters, rather than Twitter who are responsible for the automatic cropping that occurs when you retweet. But I neither a Lawyer nor a Japanese Copyright expert.
I had to edit the expiry date on the "redesign_optout" cookie that gets placed when you tick the optout. But an add-on (see sibling comment) is probably more reliable long-term.
Note that that 40% is of owner-occupiers (which is not clearly stated in the article). Which make up roughly half of all households. Renters (whether or not they own another house) are excluded from the analysis.
Changes to the way that DHCP works. There are now different methods if you're handing out subnets to a router, IPs to an end device or allowing devices to (automatically) self assign. And not all devices support all methods.
I think one of the best counterexamples is The Jabberwocky by Lewis Carroll. If names (and more generally English words) conveyed no meaning on their own and were simply keys in a large fuzzy hash table, the poem would be completely opaque. However, despite the fact that almost every word in it is made-up (new, never a be foreseen keys), I'd argue that most English speakers, after reading the poem, would have a reasonably common understanding of what "slithy" meant or what a "borogrove" was.
If names fit well with what a person already knows, they can aid memory and even impart understanding. If names are poorly chosen they can instead confuse.
Affecting a(n electorally) significant number of paper votes requires the compromise of more people and leaves more evidence than for electronic votes. (In general, for the quality of voting generally seen in first world countries)
Can you do better in theory, yes. Have we seen any evidence that various US election bodies can do better through using electronic voting, no. The exact opposite in fact.
It's similar to passwords: writing down all your passwords in a notebook and keeping it in your desk draw is a bad idea. But it's usually significantly harder to break into millions of desk draws than to break any given site's security.
Have you seen the episode of Scrapheap challenge/Junkyard wars where they did just that (in a shed, with a pile of scraps!) [1]? However they made "wet" subs rather than dry, and nothing required to last 2km of travel, which reduces the challenge quite a bit (to say the least).
It depends where you are. I know for example that the Australian standards require an accumulated time error of less than +/-5 sec on the mainland (+/-15s in Tasmania).
Looking at other comments, it seems that we're a little weird down under and most places don't track the drift.
Especially as it comes from Weta workshop who originally designed the weapon (https://wiki.teamfortress.com/wiki/Righteous_Bison) - if anyone has a physical copy it's them