You think that we should assume the worst and condemn a study that does not agree with your preconceived uncorroborated notions?
UNCORROBORATED? This is like asking for a study to see if people die when you shoot them! Wideband signals, when pushed through a long, unshielded wire, radiate. This is fact. Several very famous people in the 19th century figured this out.
Next stupid question? Perhaps you'd like an experiment to see if water freezes when you cool it?
Yes, but over here in our little corner of the universe we like to call "Rational Land," scientific "studies" conducted by for-profit organizations, especially when such studies appear to benefit said organizations, are considered highly suspect until corroborated by external researchers.
I want to see the first guy to to try tap into that broadband illegally....bzzzp!
Considering that the power line is (drum roll please) a giant freaking antenna, all you really need to tap into someone's traffic is a radio receiver.
Yay! Now we get to have the detriments of wireless systems (interference, monitoring by third parties, etc.) without any of the benefits of, well, being wireless.
These atoms would indeed just float off into space, since the gravatational pull of the planet is not strong enough to retain such light atoms.
That's not quite the right way to put it. Hydrogen can escape because it is light, yes, but not because gravity isn't "strong enough." Remember that gravity accelerates all objects equally (the falling feather and bowling ball experiment). An atom of hydrogen and an atom of lead would both fall toward the ground at exactly the same speed, and hit at the same time.
Because hydrogen is so light, however, it has a much higher velocity for a given kinetic energy than any other kind of atom, so it is much easier for it to reach escape velocity via collisions with other gas particles.
So what's the big deal about finding out if life once existed on a neighbor planet in our own solar system?
Because if life developed independently on two planets in the same solar system, that would imply that the development of life in any similar star system is not just possible, but likely..
Look at it this way: if life is so common that it had evolved multiple times in the same little nook of the galaxy, then it's a very good bet that nearly every planetary system anywhere, with even remotely the right conditions, probably harbors life. That would be amazing.
Tell us what exactly was wrong about the "embarrassing use of wood flute?" How pretentious.
It's a sickly sweet cliche. The fact that you haven't noticed it just means you don't pay attention to music the same way musicians do.
Just because music is an art which can be enjoyed by people who don't know how to do it themselves, doesn't mean the opinions of those who do study music are somehow "pretentious." Don't begrudge someone for their opinion, which might very well be an expert one...
Or do you find it statistically impossible that a person with a clue might choose to comment on it here at Slashdot?
This chip interests me most from the aspect of pulse generation. What sort of circuitry do they have on there that's capable of producing the high-power RF pulses? Have you ever seen the kinds of diodes they use on big military radars? Those things can conduct thousands of amps! They're gigantic. How the hell did they build such a pulsed power system onto an itty bitty chip (yeah, it's definitely smaller scale than the mega-diodes I've seen but it's still impressive).
This guy speaks truth. I once attempted to brake and veer around a family of raccoons crossing the road late at night. The end result was I killed the raccoons anyway (an entire family:-( ) and my car ended up pointed the wrong way on the opposite side of the street, twenty yards down. A few more feet per second of initial velocity and I would've ended up wrapped around a phone pole.
Since then I don't so much as tap the breaks for anything weighing under 100 pounds. The lives of little crawly critters are not worth more than yours (but it's godawful to hear them moaning in the bushes by the side of the road as they bleed out from being smashed by you.... Gah, that scarred me)
So your defense for being an asshole is "I say these things because I'm allowed to?" If beating your girlfriend suddenly became legal, would you do that to, just because there's no law to stop you?
This isn't a matter of free speech or censorship. I don't see anyone trying to silence your opinion here. It's a matter of a lot of Americans being assholes. You're perfectly free to make moronic statements, and we are also perfectly free to call you an idiot with his head up his ass.
And if you think it's illegal to crack Chinese jokes in Europe, you're an idiot.
I haven't seen a mail filter that will bounce E-Mails based on whether or not they're encrypted to your obnoxiously large PGP key that takes 30 seconds to encrypt to on a 2GhZ pentium
Nobody in their right mind would implement a system like that. You just described a DoS against your own machine. If the filter processes in parallel (say, spawns a process for each mail with no reasonable limit to how many can run at once) then system load will explode through the roof, DoSing your whole system. If they are in series, or grouped into a fixed number of parallel processes, then it is a DoS against your mail server since a person can flood it with so many messages that it takes days to get to the legitimate ones.
In fact, this is possible even if you don't personally use a ridiculously large PGP key. If the model is for the sender to sign with his private key and you to verify with his public key, there's nothing (currently) to stop him from choosing his own ridiculously large key pair. You get killed either way.
If you're going to use PGP or something like it to do encryption and sender verification you'll need a more structured system which prevents the types of DoS just listed. Put it in the RFC that key length cannot exceed 1024 bits (ok, 2048, I'll grant you a little paranoia).
No.. it's telling you that 1 mile per watt is equal to 1609.344 m^-1 kg^-1 s^3. It just did a unit conversion to the MKS system.
Google writes all answers with units in MKS. It simply converted your mixed-system ratio -- one unit is imperial, the other is metric, what an ugly mix.
By the way, m^-1 kg^-1 s^3 is equivalent to "seconds per newton" which is a fairly meaningless unit. A Google search for the term "seconds per newton" comes up with only a few hits, none of which has any physical meaning.
The units of a physical quantity are a fundamental component of the quantity. If you ignore them you'll end up really confused like you got here.
If Microsoft didn't include these items, you'd be the same one fucking bitching that they weren't securing their software good enough.
Bullshit. This is equivalent to somebody selling you a bullet proof vest with a giant hole in it, then saying "Oops, here's a roll of kevlar tape to patch that up." The real solution should be to sell a bullet proof vest that doesn't have a giant hole in it.
Yep, I love valgrind too... It's not perfect, however. It won't catch this bug:
int main()
{
int foo[10];
foo[10] = 1;/* Write beyond end of array */
return 0;
}
This is a very hard bug to catch automatically, because in some circumstances a write to a stack location above the base pointer is a valid operation (e.g., storing into an array local to some function further up the call stack).
Worse even that those are bugs which aren't reproducible at all, where there's no way to determine the conditions that caused them, or be sure you've fixed them.
That's not so bad. Computers are deterministic. If the same thing happens multiple times, the same result will ensue each time. Hence, the source of the intermittant problem must lie in the nondeterministic influences on the program. It immediately narrows down the possibilities to:
1. A problem triggered by specific input. Log all input (including places you wouldn't normally expect. Environment variable values count as "input", for example). Find a sequence that bugs out. Replay the input as often as necessary to debug.
2. A problem triggered by a random variable. If you call rand()-like functions, switch to a fixed seed value. Change the value until you produce the bug. Now go debug the problem.
3. If neither of the above, it must be a timing issue. Examine your inter- and intra-process synchronization code. The problem lies there.
Re:Heisenbugs...
on
Debugging
·
· Score: 3, Interesting
In my operating system class my groups' program caused an error at one of the delete[] statements and it dissappeared and reappeared depending on whether we ran it in the debug environment or not.
I'll tell you with 99% certainty that this was caused by a piece of code overrunning the end (or beginning) of a new[]'d buffer, clobbering the memory allocation meta-data. This causes delete[] to crump when it hits a bogus pointer and flies off into never never land.
By running in the debug environment you changed the memory layout of the allocation in such a way that the problem was masked.
These kinds of bugs only seem weird the first time you encounter them. They're actually some of the most common types of bugs. With enough experience you'll be finding them in your sleep.
Re:Hardware *Debugging*?
on
Debugging
·
· Score: 5, Insightful
I think the term you want is TROUBLESHOOTING.
Troubleshooting is what you do to fix your mom's ethernet card. "Oooh, it's on the bottom PCI slot, has no interrupt line. I'll just move it up one slot..."
Debugging is what you do with an oscilloscope to figure out why a particular circuit design isn't working as anticipated. You don't "troubleshoot" a circuit design. You debug it.
Or, to put it another way, "troubleshooting" is what a tech support monkey does. "Debugging" is what an engineer does.
It's probably too late to expect a reply from an AC, but I'll try anyway... I'm having trouble visualizing what you are talking about.
Since the rotational inertia of the object is the integral of density*radius over the entire object, it seems the only way the inertia (and thus the angular velocity) could change is if either the density or the radius changes.
I can picture this, for example, in the case of a spring with two weights on the ends rotating like a twirling baton. If the spring is stretched s.t. the spring restoring force is unequal to the centripetal force on the weights, they will oscillate as the spring rotates, thus altering the radius and rotational inertia. Such a rotating object would cyclically speed up, then slow down, its rotation as the weights oscillate.
But I can't figure out how this could happen with a rigid body such as an asteroid. Can you explain further?
Didn't you just contradict yourself? SA uses RBLs, pattern matching, and spam-reporting clearinghouses to identify spam. How is that a single approach?
The different features you mention are simply elements of a feature vector whose magnitude is compared to a threshold function. It's a linear classifier. The fact that the features are variegated doesn't change the fact that it's just a linear classifier.
It's hard to believe that a single approach like this is better than SpamAssassin.
SpamAssassin is a single approach. It looks at a bunch of features, then combines them linearly and compares the result against a threshold function. It's a relatively simplistic method, compared to these two. Not hard to see how more sophisticated methods could do better.
Slashdot Mirror
UNCORROBORATED? This is like asking for a study to see if people die when you shoot them! Wideband signals, when pushed through a long, unshielded wire, radiate. This is fact. Several very famous people in the 19th century figured this out.
Next stupid question? Perhaps you'd like an experiment to see if water freezes when you cool it?
Because cable line was designed for wide-band signals: it's coaxial!
A power line, OTOH, is just a very long piece of wire.
Yes, but over here in our little corner of the universe we like to call "Rational Land," scientific "studies" conducted by for-profit organizations, especially when such studies appear to benefit said organizations, are considered highly suspect until corroborated by external researchers.
But thanks for playing.
Considering that the power line is (drum roll please) a giant freaking antenna, all you really need to tap into someone's traffic is a radio receiver.
Yay! Now we get to have the detriments of wireless systems (interference, monitoring by third parties, etc.) without any of the benefits of, well, being wireless.
Dumbest idea ever.
That's not quite the right way to put it. Hydrogen can escape because it is light, yes, but not because gravity isn't "strong enough." Remember that gravity accelerates all objects equally (the falling feather and bowling ball experiment). An atom of hydrogen and an atom of lead would both fall toward the ground at exactly the same speed, and hit at the same time.
Because hydrogen is so light, however, it has a much higher velocity for a given kinetic energy than any other kind of atom, so it is much easier for it to reach escape velocity via collisions with other gas particles.
Because if life developed independently on two planets in the same solar system, that would imply that the development of life in any similar star system is not just possible, but likely..
Look at it this way: if life is so common that it had evolved multiple times in the same little nook of the galaxy, then it's a very good bet that nearly every planetary system anywhere, with even remotely the right conditions, probably harbors life. That would be amazing.
The action is legal if there is no intent to commit fraud. Obviously, you cannot spend money that has been altered.
Also see here for a guy who uses electromagnetic fields to smash metal coins (including gold ones). He even has a FAQ about the legality of doing so.
It's a sickly sweet cliche. The fact that you haven't noticed it just means you don't pay attention to music the same way musicians do.
Just because music is an art which can be enjoyed by people who don't know how to do it themselves, doesn't mean the opinions of those who do study music are somehow "pretentious." Don't begrudge someone for their opinion, which might very well be an expert one...
Or do you find it statistically impossible that a person with a clue might choose to comment on it here at Slashdot?
This chip interests me most from the aspect of pulse generation. What sort of circuitry do they have on there that's capable of producing the high-power RF pulses? Have you ever seen the kinds of diodes they use on big military radars? Those things can conduct thousands of amps! They're gigantic. How the hell did they build such a pulsed power system onto an itty bitty chip (yeah, it's definitely smaller scale than the mega-diodes I've seen but it's still impressive).
Since then I don't so much as tap the breaks for anything weighing under 100 pounds. The lives of little crawly critters are not worth more than yours (but it's godawful to hear them moaning in the bushes by the side of the road as they bleed out from being smashed by you.... Gah, that scarred me)
Who says there's no such thing as solid plasma?
This isn't a matter of free speech or censorship. I don't see anyone trying to silence your opinion here. It's a matter of a lot of Americans being assholes. You're perfectly free to make moronic statements, and we are also perfectly free to call you an idiot with his head up his ass.
And if you think it's illegal to crack Chinese jokes in Europe, you're an idiot.
Nobody in their right mind would implement a system like that. You just described a DoS against your own machine. If the filter processes in parallel (say, spawns a process for each mail with no reasonable limit to how many can run at once) then system load will explode through the roof, DoSing your whole system. If they are in series, or grouped into a fixed number of parallel processes, then it is a DoS against your mail server since a person can flood it with so many messages that it takes days to get to the legitimate ones.
In fact, this is possible even if you don't personally use a ridiculously large PGP key. If the model is for the sender to sign with his private key and you to verify with his public key, there's nothing (currently) to stop him from choosing his own ridiculously large key pair. You get killed either way.
If you're going to use PGP or something like it to do encryption and sender verification you'll need a more structured system which prevents the types of DoS just listed. Put it in the RFC that key length cannot exceed 1024 bits (ok, 2048, I'll grant you a little paranoia).
Bah, you're just installing a piece of aftermarket equipment :-) A REAL hack would be turning that turbocharger into a miniature turbojet engine.
Google writes all answers with units in MKS. It simply converted your mixed-system ratio -- one unit is imperial, the other is metric, what an ugly mix.
By the way, m^-1 kg^-1 s^3 is equivalent to "seconds per newton" which is a fairly meaningless unit. A Google search for the term "seconds per newton" comes up with only a few hits, none of which has any physical meaning.
The units of a physical quantity are a fundamental component of the quantity. If you ignore them you'll end up really confused like you got here.
Bullshit. This is equivalent to somebody selling you a bullet proof vest with a giant hole in it, then saying "Oops, here's a roll of kevlar tape to patch that up." The real solution should be to sell a bullet proof vest that doesn't have a giant hole in it.
int main()
/* Write beyond end of array */
{
int foo[10];
foo[10] = 1;
return 0;
}
This is a very hard bug to catch automatically, because in some circumstances a write to a stack location above the base pointer is a valid operation (e.g., storing into an array local to some function further up the call stack).
Yes, but you get to eat a blue hot dog!
That's not so bad. Computers are deterministic. If the same thing happens multiple times, the same result will ensue each time. Hence, the source of the intermittant problem must lie in the nondeterministic influences on the program. It immediately narrows down the possibilities to:
1. A problem triggered by specific input. Log all input (including places you wouldn't normally expect. Environment variable values count as "input", for example). Find a sequence that bugs out. Replay the input as often as necessary to debug.
2. A problem triggered by a random variable. If you call rand()-like functions, switch to a fixed seed value. Change the value until you produce the bug. Now go debug the problem.
3. If neither of the above, it must be a timing issue. Examine your inter- and intra-process synchronization code. The problem lies there.
I'll tell you with 99% certainty that this was caused by a piece of code overrunning the end (or beginning) of a new[]'d buffer, clobbering the memory allocation meta-data. This causes delete[] to crump when it hits a bogus pointer and flies off into never never land.
By running in the debug environment you changed the memory layout of the allocation in such a way that the problem was masked.
These kinds of bugs only seem weird the first time you encounter them. They're actually some of the most common types of bugs. With enough experience you'll be finding them in your sleep.
Troubleshooting is what you do to fix your mom's ethernet card. "Oooh, it's on the bottom PCI slot, has no interrupt line. I'll just move it up one slot..."
Debugging is what you do with an oscilloscope to figure out why a particular circuit design isn't working as anticipated. You don't "troubleshoot" a circuit design. You debug it.
Or, to put it another way, "troubleshooting" is what a tech support monkey does. "Debugging" is what an engineer does.
Since the rotational inertia of the object is the integral of density*radius over the entire object, it seems the only way the inertia (and thus the angular velocity) could change is if either the density or the radius changes.
I can picture this, for example, in the case of a spring with two weights on the ends rotating like a twirling baton. If the spring is stretched s.t. the spring restoring force is unequal to the centripetal force on the weights, they will oscillate as the spring rotates, thus altering the radius and rotational inertia. Such a rotating object would cyclically speed up, then slow down, its rotation as the weights oscillate.
But I can't figure out how this could happen with a rigid body such as an asteroid. Can you explain further?
The different features you mention are simply elements of a feature vector whose magnitude is compared to a threshold function. It's a linear classifier. The fact that the features are variegated doesn't change the fact that it's just a linear classifier.
[*Bing* -- mail from VP of sales pops into my inbox. Subject: "Making money fast!"]
[*Bam* -- I hit delete, thinking "Stupid Spam!"]
Ahh, shit! Lookie, a human screwed up.
The filter would have actually examined the message and probably decided that it was legitimate.
SpamAssassin is a single approach. It looks at a bunch of features, then combines them linearly and compares the result against a threshold function. It's a relatively simplistic method, compared to these two. Not hard to see how more sophisticated methods could do better.