Slashdot Mirror

jfruh writes: NVIDIA has unveiled the Drive PX, a $10,000 computer that will be installed in cars and gather data about how to react to driving obstacles. "Driving is not about detecting, driving is a learned behavior," said Jen Hsun Huang, CEO of NVIDIA. The data collected by Drive PXes will be shared, allowing cars to learn the right and wrong reactions to different situations, essentially figuring out what to do from experience rather than a rigid set of pre-defined situations.

szczys writes "Arduino is a household name in hobby electronics. But now there are two companies calling themselves Arduino and as you've probably guessed this is going to play out in the courts. How can this be? One company started the Arduino movement and used the other company, a contract manufacturer, to actually make the hardware. This went on for a few years before the trademark was actually granted. Elliot Williams did some digging to help figure out how this all might shake out."

Amanda Parker writes Drones, or unmanned aerial vehicles (UAVs), are a hot ticket in Silicon Valley, but U.S. government dithering over regulations has given overseas companies a head-start in figuring out how best to exploit them. Global spending on drones could add up to close to $100 billion over the next decade, with commercial uses — from farming and filming to pipelines and parcels — accounting for around an eighth of that market, according to BI Intelligence. But for years, the Federal Aviation Administration (FAA), the authority largely responsible for regulation in the United States, has dragged its feet, only last month issuing draft rules on who can fly drones, how and where. It's likely to be a year or more before the regulations are in place — good news for companies operating outside the U.S. and looking to build a business around drones.

StartsWithABang writes If all we were able to do was look up at the sky and see what we can see, no matter how powerful our instruments became, we would be extraordinarily limited in what we could learn about the Universe. But if we could know some intrinsic properties about what we were looking at, then simply by measuring things like how bright these objects appear, we could figure out the cosmic distance scale; all it would require is knowledge of a "distance indicator" or "standard candle." The very first one ever discovered — by Henrietta Leavitt — is not only still in use today, but taught us the galactic nature of the spiral nebulae and gave us the expanding Universe.

An anonymous reader writes "The periodic warm weather pattern called El Niño has finally arrived in the mid-equatorial Pacific Ocean, more than a year late and far weaker than predicted by scientists. "The announcement comes a year after forecasters first predicted that a major El Niño could be in the works. At the time, NOAA predicted a 50% chance that an El Niño could develop in the latter half of 2014. The agency also said the wind patterns that were driving water east across the Pacific were similar to those that occurred in the months leading up to the epic El Niño of 1997, which caught scientists by surprise and contributed to flooding, droughts and fires across multiple continents.

In the end, last year's forecasts came up short, in part because the winds that were driving the system petered out. Researchers, who have been working to improve their forecasting models since 1997, are trying to figure out precisely what happened last year and why their models failed to capture it."

MassDosage writes As the full title to Lauren Ipsum: A story about Computer Science and Other Improbable Things indicates, this is a book about Computer Science but what's surprising about it is that it manages to be about Computer Science without actually ever directly referring to the subject or even to computers at all. It is in fact a fictional story about a young girl called Lauren who gets lost after wandering into a forest near her house after an argument with her mother. She stumbles into a world populated with all kinds of strange creatures and colorful characters some of whom she befriends in order to figure out how to get back to her home. The "figuring out" part of the plot is where things get interesting as she has many attempts at solving this problem with different characters giving her often contradictory advice and Lauren then has to decide what exactly she's trying to do and which of the various possible solutions is the best. This involves a fair amount of trial and error, learning from certain mistakes and trying different approaches. If this is starting to sound familiar to those who have written software then that's the whole point. Lauren Ipsum is cunningly littered with references to Computer Science and in particular to things like algorithms, logic puzzles and many other of the theoretical underpinnings of the subject. Read below to see what MassDosage has to say about the book. Lauren Ipsum: A Story About Computer Science and Other Improbable Things author Carlos Bueno pages 182 publisher No Starch Press rating 8/10 reviewer Mass Dosage ISBN 978-1-59327-574-7 summary A whimsical journey through a land where logic and computer science come to life. In the course of her adventures Lauren encounters characters like Xor the chameleon, Hugh Rustic the shop owner, a flock of round Robins and a Wandering Salesman. Anyone who knows a bit about computer science will be aware of the topics that are being alluded to here. This is also evident in some of the places she visits — a forest made up of red and black trees, the Island of Byzantium and a Garden of Forking Paths. All these insider references are obviously more enjoyable if you know the subject but it doesn't really matter if you don't get them as the story itself is separate from all the in-jokes. It's also almost certainly the intention of the authors to stimulate people to look up some of the things they refer to and thus learn more about computer science. Lauren Ipsum can thus be read on two levels — one as a straightforward adventure story and the other as a "find and research the hidden references" book. The title of the book is itself a play on words of "Lorem Ipsum" which I'll leave you to read up on on your own.

The chapter I enjoyed the most was one that covered building up a solution to a problem by breaking it down into smaller pieces and then combining these to come up with the final answer. In the book Lauren first learns how to draw a line and then that she can then draw and connect four of these to make a square. Even better is the discussion of the seemingly simple task of how to draw a circle which demonstrates that there are different ways of doing this, each having their own pros and cons. The solutions can be easily described as a set of steps and the question of how to control the size of the circle can be specified separately from the steps themselves. This is done without referring to any of the technical terms directly (one of the first chapters in the book is all about avoiding jargon) however what is actually being described will be instantly recognizable to anyone who has written some code — namely algorithms,algorithmic complexity, variables and parameter passing. This is quite a different way of illustrating programming concepts instead of the usual manner which involves lots of theory and code examples. Lauren Ipsum's approach offers a much lower learning curve with simple story driven metaphors that can then be applied practically later.

The target audience of the book is probably children from around the age of 8 and up with the intention being to spark an interest in computers without the intimidation and possible connotations of boredom that a textbook might evoke. The story is entertaining but relatively simple and most of the more serious subject matter is just touched on in passing. There is an Appendix at the end which covers a few of the topics in more technical and mathematical detail but there is plenty that isn't covered and it is up to the reader whether they want to find out more in their own way.

I found Lauren Ipsum an entertaining read, even though some of the computer science references are a bit forced. I ended up looking up a few things I wasn't entirely sure about and learnt something new in the process and I can imagine this being even more the case for someone new to the subject. Even if the reader isn't an aspiring geek-to-be there should be enough in the story here for them to enjoy and maybe help convince them that Computer Science can actually be fun or at the very least give them a taste for why problem solving is interesting and useful.

You can purchase Lauren Ipsum: A Story About Computer Science and Other Improbable Things from amazon.com. Slashdot welcomes readers' book reviews (sci-fi included) -- to see your own review here, read the book review guidelines, then visit the submission page. If you'd like to see what books we have available from our review library please let us know.

hypnosec writes: NASA says its Mars Curiosity rover has experienced a transient short circuit. The team has halted all work from the rover temporarily while engineers analyze the situation. Telemetry data received from Curiosity indicated the short circuit, after which the vehicle followed its programmed response, stopping the arm activity underway whenthe irregularity in the electric current happened. Curiosity will stay parked as its engineers analyze the situation and figure out if any damage has been done. NASA says a transient short circuit would have little effect on the rover's operations in some systems, but it could force the team to restrict use of whatever mechanism caused the problem.

An anonymous reader writes: In November, 2013, a Kickstarter project for a software-defined camera trigger scored £290,386 (~$450,000) in funding after asking for a mere £50,000. After almost a year of delays, they've now announced the project is dead. Their CEO has published a lengthy article about how such a successful funding round can still turn into a failed product. In short: budgeting. To get their software into a workable state, they ended up spending 940% of the amount they'd originally allocated to software development. Their protoyping went over budget, too, and they had to spend a fair bit in legal fees to fend off a major camera manufacturer complaining about their product's name.

Still, they had more funding than they expected, and would have been able to deal with these costs. Unfortunately, the bill of materials for their final product clocked in way higher than they expected. They would have had to sell the device at about $350 each, when they were originally targeting a $99 price point. (And that figure assumes good sales — with a smaller production run, price per unit goes even higher.) The company is now going to refund the remaining money left over from its Kickstarter campaign — about 20% of the total. They're also open sourcing the software and sharing the PCB designs and schematics.

New submitter Peter Desnoyers writes: Shingled Magnetic Recording (SMR) drives are starting to hit the market, promising larger drives without heroic (and expensive) measures such as helium fill, but at a cost — data can no longer be over-written in place, requiring SSD-like algorithms to handle random writes.

At the USENIX File and Storage Technologies conference in February, researchers from Northeastern University (disclaimer — I'm one of them) dissected shingled drive performance both figuratively and literally, using both micro-benchmarks and a window cut in the drive to uncover the secrets of Seagate's first line of publicly-available SMR drives.

TL;DR: It's a pretty good desktop drive — with write cache enabled (the default for non-server setups) and an intermittent workload it performs quite well, handling bursts of random writes (up to a few tens of GB total) far faster than a conventional drive — but only if it has long powered-on idle periods for garbage collection. Reads and large writes run at about the same speed as on a conventional drive, and at $280 it costs less than a pair of decent 4TB drives. For heavily-loaded server applications, though, you might want to wait for the next generation. Here are a couple videos (in 16x slow motion) showing the drive in action — sequential read after deliberately fragmenting the drive, and a few thousand random writes.

AmiMoJo writes Plans to generate electricity from the world's first series of tidal lagoons have been unveiled in the UK. The six lagoons — four in Wales and one each in Somerset and Cumbria — will capture incoming and outgoing tides behind giant sea walls, and use the weight of the water to power turbines. The series of six lagoons could generate 8% of the UK's electricity for an investment of £12bn. Tidal Lagoon Power wants £168 per MWh hour for electricity in Swansea, reducing to £90-£95 per MWh for power from a second, more efficient lagoon in Cardiff. The £90 figure compares favorably with the £92.50 price for power from the planned Hinkley nuclear station, especially as the lagoon is designed to last 120 years — at a much lower risk than nuclear. Unlike power from the sun and wind, tidal power is predictable. Turbines capture energy from two incoming and two outgoing tides a day, and are expected to be active for an average of 14 hours a day. Friends of the Earth Cymru, said the group is broadly in favor of the Swansea lagoon.

schwit1 writes: Research and actual experience have found that adjusting to the slightly longer Martian day is not as easy as you would think. "If you're on Mars, or at least work by a Mars clock, you have to figure out how to put up with the exhausting challenge of those extra 40 minutes. To be exact, the Martian day is 24 hours, 39 minutes, and 35 seconds long, a length of day that doesn't coincide with the human body's natural rhythms. Scientists, Mars rover drivers, and everyone else in the space community call the Martian day a "sol" to differentiate it from an Earth day. While it doesn't seem like a big difference, that extra time adds up pretty quickly. It's like heading west by two time zones every three days. Call it 'rocket lag.'"

mpicpp sends an article from Fortune about the tiny industry springing up around food-related 3D printing. While such devices are still too expensive and too special-purpose for home kitchens, professionals in restaurants and large cafeterias are figuring out ways they can automate certain time-intensive tasks. For example, pasta: "If the user is making a recipe for ravioli, for instance, the [device] prints the bottom layer of dough, the filling and the top dough layer in subsequent steps. It reduces a lengthy recipe to two minutes construction time and ensures that no one has to clean a countertop caked with leftover dough and flour." The companies developing these 3D printers hope they'll be this generation's version of the microwave, gradually finding a use in almost every kitchen.

The same system of red-light cameras in Chicago that was shown last year to have been generating bogus tickets is still around -- but now, reports Reuters, it's a political punching bag for opponents of Chicago mayor Rahm Emanuel in an upcoming election. "[Emanuel], who supports the nation's largest automated camera system, is polling slightly under the 50 percent plus one vote he needs to avoid a run-off against the second-highest vote-getter. Three of the four challengers seeking to topple Emanuel say the cameras should go. Emanuel's closest rival, Cook County Commissioner Jesus "Chuy" Garcia, who is polling at about 20 percent, said he would only keep cameras that have been proven to reduce accidents. .... Chicago has red-light cameras at 174 intersections and 144 speed cameras near schools and parks around the city. They have brought in $500 million since 2003, according to media reports, a figure Chicago has neither confirmed nor disputed.

chicksdaddy writes Criminals beware: researchers at the National Institute of Standards and Technology (NIST) have figured out how to recover serial numbers obliterated from metal surfaces such as firearms and automobiles — a common problem in forensic examinations. According to this report, NIST researchers used a technique called electron backscatter diffraction (EBSD) to read, in the crystal structure pattern, imprints on steel that had been removed by polishing. ... The more perfect the crystal structure, the stronger and clearer the pattern. Software can then calculate the pattern quality to reveal crystal damage; areas with more damage produce lower quality patterns. In the NIST experiments, described in Forensic Science International, researchers hammered the letter 'X' into a polished stainless steel plate. The letter stamps were as deep as 140 micrometers, meeting federal regulations for firearm serial numbers. The researchers then polished the metal again to remove all visible traces of the letters, and collected the EBSD diffraction patterns and pattern quality data and analyzed them for evidence of the imprints.

snydeq writes Researchers warn that a glut of code is coming that will depress wages and turn coders into Uber drivers, InfoWorld reports. "The researchers — Boston University's Seth Benzell, Laurence Kotlikoff, and Guillermo LaGarda, and Columbia University's Jeffrey Sachs — aren't predicting some silly, Terminator-like robot apocalypse. What they are saying is that our economy is entering a new type of boom-and-bust cycle that accelerates the production of new products and new code so rapidly that supply outstrips demand. The solution to that shortage will be to figure out how not to need those hard-to-find human experts. In fact, it's already happening in some areas."

alphadogg writes Now more than ever, the development of the Linux kernel is a matter for the professionals, as unpaid volunteer contributions to the project reached their lowest recorded levels in the latest "Who Writes Linux" report, which was released today. According to the report, which is compiled by the Linux Foundation, just 11.8% of kernel development last year was done by unpaid volunteers – a 19% downturn from the 2012 figure of 14.6%. The foundation says that the downward trend in volunteer contributions has been present for years. According to Linus Torvalds, the shift towards paid developers hasn’t changed much about kernel development on its own. “I think one reason it hasn't changed things all that much is that it's not so much unpaid volunteers are going away as people who start writing kernel code get hired really quickly,” he said.

occamboy writes My spouse works at a company that deals with lots of documents (Word, spreadsheets, scans, and so forth), and they have a classic version control problem that sucks up hours of her time each week. Documents are stored on a shared server in some sort of hierarchy, but there are all kinds of problems, e.g. multiple copies get saved with slightly-different names because people are afraid of overwriting the old version 'just in case' and nobody can figure out which is the latest version, or which got sent out to a client, etc.

Version control should help, and my first thought was to use SVN with TortoiseSVN, but I'm wondering if there's something even simpler that they could use? Do the Slashdotteratti have any experiences or thoughts that they could share? The ideal solution would also make it easy to text search the document tree.

nerdyalien writes After reading a recent post about developer competence, I can't help but to ask the question, "Are general engineering skills undervalued in web development?" I am an EE major. The course I completed, and the professors who taught it; mainly emphasized on developing skills rather memorizing reams of facts and figures. As a result, I have acquired a multitude of skills such as analytical, research, programming, communication, project management, planning, self-learning, etc.

A little over 3 years ago, I made the fateful decision to become a web developer in a small SME in SEA. Admittedly, I have an unstructured knowledge about CS theory. Still, within a short period of time I picked up the essentials of web development craft, and delivered reliable web applications. Most of all, I made good use of my existing technical/soft skills, despite the lack of my CS pedigree.

Recently I went through a couple of job interviews in MNCs, SMEs and start-ups alike. All of them grilled my CS theory or Java knowledge. Almost no interviewer asked me about my other skills (or past experiences) that could be helpful in the developer position. In my experience, web development is a cocktail of competing programming languages, frameworks and standards. Rarely a developer gets exposed to a single technology for a substantial period to learn it inside-out. Even still, in web development world, deep in-depth knowledge in anything will be outdated in few years' time as new technologies roll out. So, what matter's today? Knowledge on a particular technology or re-usable engineering skills ?

An anonymous reader writes: Vint Cerf, speaking at the American Association for the Advancement of Science, said we need better methods for preserving everything we do on computers. It's not just about finding better storage media — it's about recording all the aspects of modern software and operating systems so future generations can figure out how it all worked. Cerf says, "The solution is to take an X-ray snapshot of the content and the application and the operating system together, with a description of the machine that it runs on, and preserve that for long periods of time. And that digital snapshot will recreate the past in the future." Cerf is also pushing for better data preservation standards: "The key here is when you move those bits from one place to another, that you still know how to unpack them to correctly interpret the different parts. That is all achievable if we standardize the descriptions."

HughPickens.com writes Who still smokes?" as Denise Grady reports at the NYT that however bad you thought smoking was, it's even worse. A new study has found that in addition to the well-known hazards of lung cancer, artery disease, heart attacks, chronic lung disease and stroke, researchers found that smoking was linked to significantly increased risks of infection, kidney disease, intestinal disease caused by inadequate blood flow, and heart and lung ailments not previously attributed to tobacco. "The smoking epidemic is still ongoing, and there is a need to evaluate how smoking is hurting us as a society, to support clinicians and policy making in public health," says Brian D. Carter, an author of the study. "It's not a done story." Carter says he was inspired to dig deeper into the causes of death in smokers after taking an initial look at data from five large health surveys being conducted by other researchers. As expected, death rates were higher among the smokers but diseases known to be caused by tobacco accounted for only 83 percent of the excess deaths in people who smoked. "I thought, 'Wow, that's really low,' " Mr. Carter said. "We have this huge cohort. Let's get into the weeds, cast a wide net and see what is killing smokers that we don't already know." The researchers found that, compared with people who had never smoked, smokers were about twice as likely to die from infections, kidney disease, respiratory ailments not previously linked to tobacco, and hypertensive heart disease, in which high blood pressure leads to heart failure. "The Surgeon General's report claims 480,000 deaths directly caused by smoking, but we think that is really quite a bit off," concludes Carter adding that the figure may be closer to 540,000.