No need for that. In a tightly packed city it's kinda dicey, but in a place where the land in earshot or line-of-sight on your house is private property, any protest that you can hear/see from your living room window is automatically trespassing. The rule of law (and as a last resort, the second amendment) tend to mitigate these sorts of issues. I don't like the nutjobs one bit, but then I don't live in Berkeley or places it like it for that very reason.
Code is a generous word. In most alarm clocks and wristwatches, this sort of thing is likely implemented in discrete logic gates, which I would say goes a little against the spirit of the rules.
I've worked with degree'd EE types who seem to have gotten their degrees in protoboard tinkering and not much more. Technically they're EE's, but soft math skills and limited design capabilities beyond plugging IC's together. Maybe 10-20 years ago, there was a place for them to support the Real Engineers.
Today, you buy a plug-and-play PLC-like device or Labview box for a few thousand, and suddenly a lot of the work that used to take one of those degree'd EE can be done fairly reasonably by a technician or an intern.
Bzzt. Mathematically correct but practically wrong. Any real or simulated dataset from which you would want to compute a standard deviation will have the property that it will be a list of (most likely) double precision floating that is finite in size. This data defines a distribution that always has a finite first and second moment, so you will get a number that you can confidently call the standard deviation of the data. Even if it comes from physical process with a nonsense distribution like a Cauchy distribution, the standard deviation you compute will give you a bound on the spread of your data. If it's Gaussian, you can go back to your statistics class and say that 95% of the data will be within two SD's, etc. If it's not, you can use the Chebyshev rule (http://en.wikipedia.org/wiki/Chebyshev_inequality) to say that at least 75 percent of the data will be in two SD's, 89% will be within 3 SD's, etc, which is much coarser information, but is still reasonable to look at for worst-case analysis.
Agreed. Also, six rigid wheels was fine for Pathfinder, Spirit, and Opportunity, but now you've got what, one ton? of rover, and still six rigid wheels. Eight or twelve smaller wheels might be a good idea for the next similarly-sized rover.
Because silly toy languages designed for novices are better to use to teach elementary concepts like variables, branching, and loops without having half the class bogged down in missed curly braces and semicolons. It is also much more instructive to come to the realization that goto is Considered Harmful after trying to hack up your own spaghetti code than it is to be insulated from it by a language that doesn't even have a goto, leaving you with only a vague and abstract notion of the virtues of measuring twice and cutting once.
You know, any task done well should logically have this property, but for some reason you never hear about the years of kitchen catastrophes that go into making an innovative world-class chef, or years of grinding practice that make a gold-medal figure-skating or gymnastics routine. Maybe there really is an image problem that's bigger than we'd like to admit.
I think real men use plugboards, though oddly enough, most of the original plugboard coders in the 40's and the magnetic core ROM knitters in the 50's and 60's were women.
Poking around a large lithium battery with a cheap multimeter at night. That's got Darwin Award written all over it. Maybe try a Hall Effect current probe. Not as cheap, but less likely to kill you.
If you want exact results from a fixed number of significant bits, you want magic.
Whatever calculation you're making, be aware of the dynamic range of the intermediate results. Structure your calculations so that all intermediate results stay well within the dynamic range of the datatype. If you want to compute the standard deviation of 2048x2048 32-bit integers, use a 64 bit or 128 bit integer to compute the intermediate sum(x^2). If you try to use an IEEE double, you'll end up overflowing the 53 bits they give you because 2^11 * 2^11 * 2^32=2^54.
If you can, reformulate your calculation steps so to minimize the sensitivity to random errors on the order of a machine epsilon.
An electronic computer manual from UNIVAC/Boroughs/IBM written for pure mathematicians in ~1953 will tell you the same thing.
Did I code up my interrupt handler on my $2 microcontroller on a $20 dev board? Is it the right polarity? Is the rise time OK with the on-board driver or do I need a buffer IC? The list goes on.
Check out the international GNSS service: http://igscb.jpl.nasa.gov/
This is a NASA-run program that simultaneously monitors GPS and GLONASS signals all over the world for scientific purposes. Not the same as an official ground control station, but it's not fair to say this would be breaking entirely new ground.
One would usually want to get one's crashing out of the way with small styrofoam remote controlled airplanes before we fail with big expensive remote controlled airplanes.
Maybe that's got more to do with having vast mineral wealth, a robust diversified economy, and a well-educated hard-working population than it a wage floor on the books.
Wasn't there a privilege escalation bug in the usb filessystem code in the Linux kernel a few years ago? If it's in space now, it's probably running a 5-10 year old kernel at best, with that vulnerability still there.
Doors that hinge in the back instead of in the front. Won't shut themselves by aerodynamic pressure at speed like normal car doors. Hence, "suicide" doors.
I'm sure you can, for your own personal definition of Better. Then again, the Sheikh probably thinks he knows better than you how to use his people's money because he is mandated by God, fate, and destiny to rule whatever land it is we're talking about here. I'm sure there's a distinction in viewpoints here, but I realize I'm failing to grasp it.
Oh come now. In America, if you've got a beef with the government, you can call up your congressman/state rep/city councillor and either get lip service or occasionally something useful (ie your problem is fixed by legislation or variance or whatever). In Soviet Russia, if you've got a beef with the government, you disappear. A very subtle difference, I understand, but science is the art of making fine distinctions.
Market force too strong...can't resist urge to live closer to work, work closer to home, or seek employment in different city...
No need for that. In a tightly packed city it's kinda dicey, but in a place where the land in earshot or line-of-sight on your house is private property, any protest that you can hear/see from your living room window is automatically trespassing. The rule of law (and as a last resort, the second amendment) tend to mitigate these sorts of issues. I don't like the nutjobs one bit, but then I don't live in Berkeley or places it like it for that very reason.
Code is a generous word. In most alarm clocks and wristwatches, this sort of thing is likely implemented in discrete logic gates, which I would say goes a little against the spirit of the rules.
I've worked with degree'd EE types who seem to have gotten their degrees in protoboard tinkering and not much more. Technically they're EE's, but soft math skills and limited design capabilities beyond plugging IC's together. Maybe 10-20 years ago, there was a place for them to support the Real Engineers. Today, you buy a plug-and-play PLC-like device or Labview box for a few thousand, and suddenly a lot of the work that used to take one of those degree'd EE can be done fairly reasonably by a technician or an intern.
Bzzt. Mathematically correct but practically wrong. Any real or simulated dataset from which you would want to compute a standard deviation will have the property that it will be a list of (most likely) double precision floating that is finite in size. This data defines a distribution that always has a finite first and second moment, so you will get a number that you can confidently call the standard deviation of the data. Even if it comes from physical process with a nonsense distribution like a Cauchy distribution, the standard deviation you compute will give you a bound on the spread of your data. If it's Gaussian, you can go back to your statistics class and say that 95% of the data will be within two SD's, etc. If it's not, you can use the Chebyshev rule (http://en.wikipedia.org/wiki/Chebyshev_inequality) to say that at least 75 percent of the data will be in two SD's, 89% will be within 3 SD's, etc, which is much coarser information, but is still reasonable to look at for worst-case analysis.
Agreed. Also, six rigid wheels was fine for Pathfinder, Spirit, and Opportunity, but now you've got what, one ton? of rover, and still six rigid wheels. Eight or twelve smaller wheels might be a good idea for the next similarly-sized rover.
Problem solved: extrapolating dimension-wise, it should only exist for 16 seconds and then disappear!
Because silly toy languages designed for novices are better to use to teach elementary concepts like variables, branching, and loops without having half the class bogged down in missed curly braces and semicolons. It is also much more instructive to come to the realization that goto is Considered Harmful after trying to hack up your own spaghetti code than it is to be insulated from it by a language that doesn't even have a goto, leaving you with only a vague and abstract notion of the virtues of measuring twice and cutting once.
You know, any task done well should logically have this property, but for some reason you never hear about the years of kitchen catastrophes that go into making an innovative world-class chef, or years of grinding practice that make a gold-medal figure-skating or gymnastics routine. Maybe there really is an image problem that's bigger than we'd like to admit.
I think real men use plugboards, though oddly enough, most of the original plugboard coders in the 40's and the magnetic core ROM knitters in the 50's and 60's were women.
And humans all the way down? Turtles all the way up? Where does the Elephant fit into this theory?
Idunno. It might not be a bad idea to take legal papers drafted in purple crayon less seriously that those typed out in the proper format.
Poking around a large lithium battery with a cheap multimeter at night. That's got Darwin Award written all over it. Maybe try a Hall Effect current probe. Not as cheap, but less likely to kill you.
He must have been using imaginary data.
If you want exact results from a fixed number of significant bits, you want magic.
Whatever calculation you're making, be aware of the dynamic range of the intermediate results. Structure your calculations so that all intermediate results stay well within the dynamic range of the datatype. If you want to compute the standard deviation of 2048x2048 32-bit integers, use a 64 bit or 128 bit integer to compute the intermediate sum(x^2). If you try to use an IEEE double, you'll end up overflowing the 53 bits they give you because 2^11 * 2^11 * 2^32=2^54.
If you can, reformulate your calculation steps so to minimize the sensitivity to random errors on the order of a machine epsilon.
An electronic computer manual from UNIVAC/Boroughs/IBM written for pure mathematicians in ~1953 will tell you the same thing.
Did I code up my interrupt handler on my $2 microcontroller on a $20 dev board? Is it the right polarity? Is the rise time OK with the on-board driver or do I need a buffer IC? The list goes on.
Check out the international GNSS service: http://igscb.jpl.nasa.gov/ This is a NASA-run program that simultaneously monitors GPS and GLONASS signals all over the world for scientific purposes. Not the same as an official ground control station, but it's not fair to say this would be breaking entirely new ground.
One would usually want to get one's crashing out of the way with small styrofoam remote controlled airplanes before we fail with big expensive remote controlled airplanes.
Maybe that's got more to do with having vast mineral wealth, a robust diversified economy, and a well-educated hard-working population than it a wage floor on the books.
Difference is that it's awfully difficult to steal a TV from a store and call it a victimless crime with a straight face.
Wasn't there a privilege escalation bug in the usb filessystem code in the Linux kernel a few years ago? If it's in space now, it's probably running a 5-10 year old kernel at best, with that vulnerability still there.
Doors that hinge in the back instead of in the front. Won't shut themselves by aerodynamic pressure at speed like normal car doors. Hence, "suicide" doors.
I'm sure you can, for your own personal definition of Better. Then again, the Sheikh probably thinks he knows better than you how to use his people's money because he is mandated by God, fate, and destiny to rule whatever land it is we're talking about here. I'm sure there's a distinction in viewpoints here, but I realize I'm failing to grasp it.
In this case it sounds more like, "we've got to put out fire Z first"
Oh come now. In America, if you've got a beef with the government, you can call up your congressman/state rep/city councillor and either get lip service or occasionally something useful (ie your problem is fixed by legislation or variance or whatever). In Soviet Russia, if you've got a beef with the government, you disappear. A very subtle difference, I understand, but science is the art of making fine distinctions.