ieee   2011

« earlier    

China’s Ambitious Plan to Build the World’s Biggest Supergrid
A massive expansion leads to the first ultrahigh-voltage AC-DC power grid
HVDC  china  supergrid  IEEE  overview 
yesterday by Bluyssae
Electric Container Ships Are Stuck on the Horizon
Batteries still can’t scale up to power the world’s biggest vessels
electric  ship  container  IEEE  overview 
yesterday by Bluyssae
What’s Better Than 40 GPU-based Computers? A Computer With 40 GPUs
Engineers aim to use “silicon interconnect fabric” to build a computer with 40 GPUs on a single silicon wafer
wafer  scale  integration  latency  trilogy  systems  IEEE 
yesterday by Bluyssae
Hardware is unforgiving
Today, anyone with a CS 101 background can take Geoffrey Hinton's course on neural networks and deep learning, and start applying state of the art machine learning techniques in production within a couple months. In software land, you can fix minor bugs in real time. If it takes a whole day to run your regression test suite, you consider yourself lucky because it means you're in one of the few environments that takes testing seriously. If the architecture is fundamentally flawed, you pull out your copy of Feathers' “Working Effectively with Legacy Code” and you apply minor fixes until you're done.

This isn't to say that software isn't hard, it's just a different kind of hard: the sort of hard that can be attacked with genius and perseverance, even without experience. But, if you want to build a ship, and you "only" have a decade of experience with carpentry, milling, metalworking, etc., well, good luck. You're going to need it. With a large ship, “minor” fixes can take days or weeks, and a fundamental flaw means that your ship sinks and you've lost half a year of work and tens of millions of dollars. By the time you get to something with the complexity of a modern high-performance microprocessor, a minor bug discovered in production costs three months and five million dollars. A fundamental flaw in the architecture will cost you five years and hundreds of millions of dollars2.

Physical mistakes are costly. There's no undo and editing isn't simply a matter of pressing some keys; changes consume real, physical resources. You need enough wisdom and experience to avoid common mistakes entirely – especially the ones that can't be fixed.
techtariat  comparison  software  hardware  programming  engineering  nitty-gritty  realness  roots  explanans  startups  tech  sv  the-world-is-just-atoms  examples  stories  economics  heavy-industry  hard-tech  cs  IEEE  oceans  trade  korea  asia  recruiting  britain  anglo  expert-experience  growth-econ  world  developing-world  books  recommendations  intricacy  dan-luu  age-generation 
2 days ago by nhaliday
performance - What is the difference between latency, bandwidth and throughput? - Stack Overflow
Latency is the amount of time it takes to travel through the tube.
Bandwidth is how wide the tube is.
The amount of water flow will be your throughput

Vehicle Analogy:

Container travel time from source to destination is latency.
Container size is bandwidth.
Container load is throughput.


Note, bandwidth in particular has other common meanings, I've assumed networking because this is stackoverflow but if it was a maths or amateur radio forum I might be talking about something else entirely.
q-n-a  stackex  programming  IEEE  nitty-gritty  definition  jargon  network-structure  metrics  speedometer  time  stock-flow  performance 
21 days ago by nhaliday
IEEE Xplore - Browse Standards Dictionary
Dictionary of terms used in IEEE standards
4 weeks ago by cgunther
How the Boeing 737 Max Disaster Looks to a Software Developer - IEEE Spectrum
«I cannot get the parallels between the 737 Max and the space shuttle Challenger out of my head. The Challenger accident, another textbook case study in normal failure, came about not because people didn’t follow the rules but because they did. In the Challenger case, the rules said that they had to have prelaunch conferences to ascertain flight readiness. It didn’t say that a significant input to those conferences couldn’t be the political considerations of delaying a launch. The inputs were weighed, the process was followed, and a majority consensus was to launch. And seven people died.»
engineering  aviation  software  ieee  boeing  disaster  opinion  for-toni 
6 weeks ago by brennen
Teach debugging
A friend of mine and I couldn't understand why some people were having so much trouble; the material seemed like common sense. The Feynman Method was the only tool we needed.

1. Write down the problem
2. Think real hard
3. Write down the solution

The Feynman Method failed us on the last project: the design of a divider, a real-world-scale project an order of magnitude more complex than anything we'd been asked to tackle before. On the day he assigned the project, the professor exhorted us to begin early. Over the next few weeks, we heard rumors that some of our classmates worked day and night without making progress.


And then, just after midnight, a number of our newfound buddies from dinner reported successes. Half of those who started from scratch had working designs. Others were despondent, because their design was still broken in some subtle, non-obvious way. As I talked with one of those students, I began poring over his design. And after a few minutes, I realized that the Feynman method wasn't the only way forward: it should be possible to systematically apply a mechanical technique repeatedly to find the source of our problems. Beneath all the abstractions, our projects consisted purely of NAND gates (woe to those who dug around our toolbox enough to uncover dynamic logic), which outputs a 0 only when both inputs are 1. If the correct output is 0, both inputs should be 1. The input that isn't is in error, an error that is, itself, the output of a NAND gate where at least one input is 0 when it should be 1. We applied this method recursively, finding the source of all the problems in both our designs in under half an hour.
techtariat  dan-luu  engineering  programming  debugging  IEEE  reflection  stories  education  higher-ed  checklists  iteration-recursion  divide-and-conquer  thinking  ground-up  nitty-gritty  giants  feynman  error  input-output  structure  composition-decomposition  abstraction  systematic-ad-hoc  reduction  teaching  state 
6 weeks ago by nhaliday
Giving patients a lift - the robotic nursing assistant (RoNA) - IEEE Conference Publication
Nursing has ranked as one of the top 10 occupations for causing the work-related musculoskeletal injuries in U.S. Constantly and manually lifting and repositioning patients around bed and transferring them from bed to bed have been recognized as the major reasons causing nurses' workrelated musculoskeletal injuries. We believe that advanced robotic technologies can assist nurses in performing the labor intensive tasks and preventing the musculoskeletal injuries among medical workers and nurses. In this paper, we present Hstar Technologies' 2 nd generation Robotic Nursing Assistant (RoNA) systemRoNA.
ieee  article  robotics  nusring  assistant  obesity 
6 weeks ago by cyberchucktx

« earlier    

related tags

!uwitm  1788  2018  2019  3gpp  4g  5g  754  abstraction  academia  academic  accuracy  accurate  aerospace  age-generation  ai  aircraft  anglo  animal  architecture  archives  arithmetic  article  article19  articles  artificialintelligence  asia  assistant  asynchronous  authentication  automation  automobile  autonomous_systems  autonomous_vehicles  autonomoussystems  aviation  bash  battery  beastiary  bee.sensors  behavior  bigdata  binary  bit  blog  board  boeing  books  britain  brooks  butterfly  cable  careers  cas  cellular  centaur  checklists  china  cobalt  codeofpractice  college:engineering  commandline  communication  comotion  comparison  composition-decomposition  computationalarchivalscience  computer  computer_science  computers  computing  conference  container  content  convert  coral  costaspapaliolios  cpu  crypto  cs  cs201  cyber-spectrum  cybersecurity  dan-luu  data  datamining  datascience  debugging  decision-making  definition  design  dev  developing-world  devices  diagnostics  disaster  divide-and-conquer  diy  dna  docopt  dot  double  dsp  ecg  economics  edge  education  ekm  electric  electronics  emergence  employment  energy  energyharvesting  engineering  error  ethics  eu  evanackerman  examples  expert-experience  explanans  exponent  failures  fet  feynman  fiber  float-representation  float  floating-point  floating  floating_point  floatingpoint  fogcomputing  for-toni  foundry  fox.dieter  fp32  free  from:spectrum  gallery  gauvin  gc  giants  gollakota.shyam  google  gpu  ground-up  growth-econ  guide  guidelines  half-life  hard-tech  hardware  harvesting  health  heater  heavy-industry  higher-ed  hiring  history  hn  honeybee  human  hvdc  hybrid  ibm  ic  ieee-754  ieee754  induction  input-output  integration  interlingua  interspecies  interval  interview  intricacy  iot  iteration-recursion  iyer.vikram  jargon  javascript  jobboard  jobs  julianschwinger  knowledge  korea  latency  latex  law  lcd  learning  legacy  litz  machine  machine_learning  machlup  magazine  mainframe  management  mantissa  math  mathematics  medical  messaging  metal  methodology  metrics  microwave  ml  modernization  monitoriing  natl  network-structure  network  neuralnetworks  nitty-gritty  numerical  nusring  obesity  oceans  of  oled  online  opinion  optical  overview  paper  papers  papert  patterns  pedagogy  performance  physics  pi  pneumonia  point  policy  posix  power  precise  precision  primer  privacy  processing  programing  programming  python  q-n-a  quantum  quantumphysics  raspberry  raspberrypi  readable  reading  realness  recommendations  recruiting  reduction  reflection  remote  research  rf  robofly  robot  robotics  robots  roots  safety  scale  science  security  sensor  sexbot  ship  sign  significand  signs  smart  society  software  softwaredevelopment  solarpanels  sources  specification  spectrum  speedometer  stackex  standard  standards  stanford  startups  state  stethoscope  stock-flow  storage  stories  strangle  strangulation  structure  summary  supergrid  surveillance  sustainable  sv  systematic-ad-hoc  systems  tagxapi  teaching  tealphoenix  tech  technology  techtariat  television  thad  the-world-is-just-atoms  theoschlossnagle  thinking  time  tobots  tool  toys  trade  trends  trilogy  tube  tutorial  uas  uav  undersea  vacuum  vision  vital  wafer  wearable  wearables  wikipedia  wire  world  writing  xapi  zebrafish 

Copy this bookmark: