A quick google search turned up the following paper
I wouldn't go so far as to say that chicken is the closest living relative to the T-Rex, just that it is the closest in sequence similarity to this particular collagen protein, out of all of the protein sequences known in 2007 (chicken could have been the only bird represented in the database at the time, but I am not going to take the time to look into this).
I just searched the GVQGPPGPQGPR T-rex collagen sequence given in the text against the NCBI nr database, which is pretty comprehensive. It yielded the following Collagen alpha-1(I) chain perfect matches:
Brachylophosaurus canadensis [dinosaur]
Tyrannosaurus rex [dinosaur]
So, that's 11 birds, 1 other dinosaur, and 2 mammals (one placental, one marsupial). The list gets bigger if we relax the sequence similarity cutoff. Based on this single fragment of a sequence, we can infer that T-rex is generally more closely related to birds than to mammals or lizards (and no lizards made the top-hit list), since there were a lot more bird matches than mammals (and the lack of mammal hits is likely not due to lack of sampling relative to birds). This is a big inference to make from a single fragment of a single protein, but I'm reasonably confident that further analysis of additional T-rex sequences would strengthen this finding.
If more sequences have been published since 2007, then perhaps we could get a better idea of which modern bird T-rex is most closely related to, but there is no way to determine this from just the single example sequence above. We cannot say with any confidence that T-rex is more related to chicken than to any other bird, unless a much more thorough analysis is performed using a lot more data. Perhaps this has already been done, but I haven't taken the time to hunt for additional literature.
Autonews needs to work on their figure coloring skills. In a related article linked from the one previously mentioned, GA is colored medium orange, which indicates "Uncertain -- No formal legal or legislative challenges are known", when it should instead be colored light orange ("Legally allowed with restrictions on number of cars sold or number of stores"). From the article, it is clear that GA is legally allowed with restrictions on numbers of cars sold or number of stores, and there have clearly been formal legal or legislative challenges. Sad that they can't get their figures to match their own reporting....
If the Debian maintainers / committees are anything like Ubuntu, then I'm not at all surprised. For many years, grep -P didn't work in Ubuntu. It took them *FOUR YEARS* to fix it, with a rather bizarre discussion in the mean time. A core UNIX utility is broken and it takes four years to fix it? The earliest discussed solution, which remained the preferred solution for quite some time, was to retcon the documentation to cover it up! After 7 months, it was somehow demoted back down to "unconfirmed", and it took another 1.5 years after that re-acknowledge it was broken, after many voices of sanity finally prevailed.
After experiencing this level of cluelessness and severe disconnect with reality, I swore off Ubuntu forever. If other Linux distros are anything like the Ubuntu maintainers, I can only imagine what poor reasoning and justifications have been put forward regarding switching to systemd....
I do have the option enabled to allow unobtrusive ads so at least I'm not that big of a dirtbag.
I used to allow unobtrusive ads, but then slashdot began causing my mouse pointer to turn into the busy pointer as these "non-instrusive" ads updated themselves. I don't mind static ads that don't take up much space, but once they start changing themselves on a frequent basis, which in turn causes my mouse pointer to animate, which I see out of the corner of my eye while reading the article I am interested in, then it quickly becomes intrusive. So, since non-intrusive ads have now become intrusive, I simply block them all. Screw 'em. They've used up all my good faith.
If the heating effect you propose did occur, and the liquid could be well-localized to the tumor, then this might yield an interesting treatment option. If you could cook only the tumor, and not so much the surrounding area, then perhaps this could be beneficial, especially when combined with other treatments that stress the tumor at the same time (chemo, radiation)?
I can't use IE10 or IE11 due to the forced KB2670838 update that comes with them. For me, KB2670838 breaks the Resource Monitor in Windows 7 that you can launch after bringing up the Task Manager with ctl-alt-del. I use this quite a bit to monitor memory usage of processes, disk accesses, etc. This has been a known problem for quite some time, ever since IE10 came out. Just google for "KB2670838 resource monitor". If you uninstall KB2670838 in order to get Resource Monitor to work again, it uninstalls IE10 and IE11, since evidently they depend on it for whatever reason (I am not aware of any other software that requires this update to function). I normally wouldn't be too upset over them dropping support for legacy browser versions, but if they can't get off their butts to either fix KB2670838 to not break Resource Monitor, or fix Resource Monitor to not be broken by KB2670838, then I'm going to have to give them crap over this decision. I'll start using IE11 once it stops breaking Resource Monitor.
I don't know why it will be a limited edtion, but the phrase "limited edition" scares me. I hope it doesn't turn into another LEGO Mars Rover. They started selling those this past January, and they sold out online within a few days. The same thing happened in February and March. Then, once they sold out in March, they stayed sold out, and rumor is that they may not produce any more, ever. I only found all this out in April once I asked a LEGO store clerk if they expected to get any in any time soon.
It really pisses me off that A) they don't say on their website which sets will ever be sold in a physical LEGO store or not, and B) whether a set is limited edition or not, and what limited edition might mean. There was no indication that the Mars Rover would never show up physically in stores, or that it would sell out by the 3rd month of the year and never be available again. I really wanted one of these. I'd been following it for a year or so, and thought I'd just have to wait for it to show up in stores 6 months later, after demand had fallen, like the Back to the Future set did (LEGO store clerks I spoke to in store said they were selling out the day the truck came in with a shipment). If a set is really popular and selling out quickly, you'd usually expect a company to make a bunch more to sell for more profit , like they did for the Back to the Future set, but for some reason this logic was not followed for the Mars Rover.
I've been looking forward to this Female Scientists set for a while now too, and I'm worried that I won't be able to ever buy one if they follow the same pattern as the LEGO Mars Rover. Paying 2x-3x on E-Bay is not an acceptable option, and mail order from the online LEGO Store directly is generally out for me as well, since there is too much risk of delivered items being stolen off my apartment doorstep. If they follow the same pattern as the Mars Rover and don't sell these in LEGO stores, and stop selling them at all after 3-4 months, then I will be very sad:(
It's disastrous. cDNA is just a direct copy of the most important part of what's in the genomeâ"the actual transcript that gets used to make the final protein. This isn't a victory at all.
I agree that this isn't really a victory. The court still got things very wrong. But the above explanation isn't quite correct, either. The transcript that gets used to make the final protein would be mRNA, not cDNA.
It's still just a copy of the original, though. And a trivial copy to produce. Nature already gave us enzymes to do this, which we isolated from various bacteria (which were also patented). We then mix some stuff in a tube, and voila, we have a complementary copy of the DNA. For a not-quite-apt analogy, it would be like taking a page of text and photocopying a mirror image of it. Or, perhaps more appropriate for Slashdot, transcribing it into ROT13. However you look at it, it is a trivial to produce copy, even if it is sort of a mirror image of the original.
So, I feel that cDNA should not be patentable. It's trivial. It's obvious. It's already existing in nature. Little effort went into creating it. You should not be able to patent fragments of cDNA. Now, how you *USE* said fragments, like as a specific collection of cDNA fragments for a test kit, that's another matter, one which I don't want to get into. I don't like method patents, but that isn't the issue we're discussing right now. The court still got this wrong, due to lack of sufficient understanding of biology.
It seems like the music licensing companies in many countries are equally evil. This latest move by the Belgians is just business as usual, disgusting as it may be.
But, why do they then choose acronyms that are so easy to make fun of?
ASCAP: Ass-Cap (put a cap in yo ass)
SABAM: Sa-*BAM* (like punching someone in a Batman comic book)
I'm sure there are fun mis-pronunciations for the equivalent associations in other countries as well. Anyone from other countries want to contribute more?
I can somewhat answer the inverse of this question, though: "How many drugs do we reject in clinical trials because some researcher used the wrong animal model to test?"
My memory is a little fuzzy on the exact number from when I worked in the industry, but something like 70% of all drugs that pass Phase 1 trials fail in Phase 2 trials. Phase 1 trials are small and test for safety problems, and Phase 2 trials expand to a larger cohort to test for efficacy -- does the drug work. The pharmaceutical industry loses around 70% of all its drug candidates due to them plain not working. Often times, this is due to it working in mice/rats, but not working in humans. This isn't entirely surprising, since rodents are a good bit different than humans. Also, many animal models simply mimic human disease, rather than actually being related to how the human disease works. For example, many animal models are done over a short period of time, say 30 days or less between the initial insult (do something nasty to the rodent to induce disease-like symptoms). For inflammatory diseases, real human disease may take years from the initial problem (whatever it may be) to develop into full blown disease. When you're comparing an animal model on the time scale of a few weeks to human disease over several years, and the insult is something very very different from what it could possibly ever be in a human, it should come as no surprise that the model is often biologically very different from what is going on the human. This isn't necessarily due to rodents being too different from humans, but could easily be due to the model simply being the wrong model to mimic human disease.
Long story short, many animal models just don't do a good job at representing human disease. This is not news to anyone who has worked with them or been in the pharmaceutical industry. However, not everything is gloom and doom here. There are, actually, many animal models that *DO* do a good job of modeling human disease. The trick is to know which ones are good and which ones aren't for various diseases, drugs, pathways, etc. before you start spending the big money on clinical trials....
Back in the early to mid 90's, when I was in undergrad and using several different unix platforms (AIX, HP-UX, SunOS, Linux, DEC-OS, dumb X-terminals, etc.), different programs on different platforms treated backspace as different things. The talk/ntalk/ytalk command on HP-UX was especially annoying. It would interpret the backspace key as a ^C and kill your talk connection to your buddy across the country using his unix account to chat with you. Imagine typing away, then hitting the backspace key to fix a typo, only to have your connection killed. Sometimes shift-backspace worked (HP-UX, ftp clients, various login prompts), sometimes DEL (usually easy to fix by setting the terminal variable and/or tset), but ^H almost always worked like it should. I believe on a dumb X-terminal on my desk that I had to use to connect to a Sun server during early graduate school, ^H was the only way I could figure out how to actually issue a backspace. So, in agreement with what other posters have said, ^H isn't really important anymore. Not like it was in days of yore, when there were MANY different ways to issue a backspace, you could never be sure which would work, and the backspace key could sometimes do unexpected things. These days, backspace and delete generally do what you'd expect them to do.
To this day, I *still* automatically use shift-backspace to fix typos during login prompts, as well as ^D to forward delete instead of the delete key:) Just don't hold down ^D at an empty unix terminal prompt, or it will auto-exit the connection. This can be especially annoying in an environment when you have multiple console windows open and you hold down ^D on a blank prompt. The first window closes, focus switches to the next window, which in turn closes due to ^D on a blank prompt, etc.. In short order, all your windows are gone, all because you started deleting at the start of the command line and it ran out of stuff to delete. I never understood why this was a "feature". I have, however, adapted and will often use ^D on a blank prompt intentionally to exit a session (it's so much faster than typing "exit");P
A bit further off-topic, but there was one program on one system that I used one time where neither the ENTER nor the RETURN key functioned as expected. I was forced to resort to ^M to issue newlines! Ah, the days needing to know all of the alternate ^key commands:)
It should be one crime, one charge, but that's not required by law, so they interpret this type as shotgunning as within their requirement t prosecute to the full extent of the law. Don't like it? Change the law. Your congress-critter won't change the law? Change congress-critters -- this you CAN do.
This makes me think of the South Park rerun that was on last night or maybe the night before -- the one where the kids had to vote for the Giant Douche or the Turd Sandwich as their school mascot. When your choice is between a giant douche and a turd sandwich, it doesn't much matter which congress-critter you vote in -- neither choice will result in the outcome you desire above....
The typical mouse wheel works for zooming in and out by discrete amounts, not for something more continuous such as adjusting a photo's crop rectangle, and definitely not for rotation. Image manipulation programs designed to be used with a mouse instead use control handles of various sorts, and the user can't change the size, center, and rotation all at once the way one can with two fingers on a touch screen.
I have used 3D molecular modeling tools for years. You can get by just fine with a 3-button mouse. 3 single buttons, 3 2-button combinations = all the axes you need to translate/rotate/zoom, all continuous. You don't need a mouse wheel at all, just button combinations and intelligent movement of the mouse while the combinations are held. It's really quite intuitive and easy to use.
However, you are correct in that I was never able to zoom, translate, and rotate all in a single gesture. However, 3 separate smooth gestures is no problem at all, and (to me at least) preferable. For fine positioning, it is much better to limit movement to only one of these axes at a time, so that you do not accidentally mess up one of your axis positions while you are adjusting another to get it just right.
Google Scholar brings up a PDF file I can obtain without a subscription. So, I searched for "flav" to see what's going on here. Table 1 gives stats for "Total flavanols". The only other hits are in the references, where there are 3 references with flavonoid(s) in their title, and 2 more with flavonol(s). Now, I haven't tried to hunt down and read over these 5 cited articles, but given their titles, I think it highly likely that they do indeed cover flavonoids and not flavanoids.
Now, could flavanoid information have been taken from other citations that don't have flavanol in their title? Sure. But, since they cite 5 papers that appear to be solely dedicated to flavonol/flavonoids, and nowhere mention flavonol/flavonoids in the rest of their manuscript, I'm guessing that "flavanol" really is a typo and that they really did measure, report, and meant to talk about flavonols.
So, the criticism does appear to be valid. The only mention of flavanols in the entire manuscript does appear likely, at least to me, to be a typo meant to convey information about flavonols. Now, whether this was an intentional dishonest typo, or an honest accidental typo, I'm not going to speculate. I'm just confirming that the claim of misreporting flavonols as flavanols appears to have merit.
Like most of the research in PNAS this was not subjected to the high level of peer review expected in most scholarly journals and this paper got through without regard to its relevance and real-world significance.
I feel the need to defend PNAS here, since I actually consider it to be one of the better journals -- *IF* the manuscript has been accepted via the non- Academy of Sciences peer review process. PNAS has two (maybe three?) submission tracks: A) You are a member of the Academy of Sciences, and this results in your manuscript getting accepted more easily than usual. B) You get a friend who is an Academy member to submit your paper for you, which also lowers the bar. I'm not sure if this is really part of track A) or not, so it may or may not count as a separate track. Track C), however, is where someone who is NOT associated with the Academy submits a manuscript. Papers that come in from "external" submissions and make it past the Editor, and then all the peer review, are actually generally quite good.
So, PNAS is a mixed bag. Manuscripts from Academy members can be a bit on the sketchier side due to how the submission/review process works for them, but manuscripts from non-Academy members are often, IMHO, a good bit better than average. As with all scientific manuscripts, you must read them over carefully and determine if they have sufficiently proved their point or not.
Unfortunately, you may have a point about this particular article, since it was "Contributed by Bruce D. Hammock", who a quick Google search shows to be an Academy member.... I have not actually read the TFA, though, so I can't comment on whether it is any good or not.
"Weiss said the report says the cyber attacker hacked into the water utility using passwords stolen from a control system vendor and that he had stolen other user names and passwords."
How likely is it that a control system vendor would have the usernames and passwords of their client, used in the actual production system? Maybe they actually do, as part of some sort of remote support agreement, but if this is the case, that's already a bad security practice.
It seems more likely to me that the vendor has a list of default usernames and passwords, and THIS is what was obtained. Perhaps what Weiss *really* meant to say would be be something like: "Someone got ahold of the default usernames and passwords that our vendor uses. Since we never changed them from the default values, it's our own damn fault."
After seeing SO many stories like this, it's usually a case of not changing default passwords. Given that Weiss's statement *could* be read as I have read it, this seems the most likely scenario to me. I'm going to write this one up as stupidly bad security policies until I have sufficient evidence contradicting this assumption.
I looked it up at www.tbauto.com. Said car is a reproduction 1770 Fardier de Cugnot. From the website:
"The original Fardier de Cugnot has been in the collection of the Le Conservatoire de Arts et Metiers, Paris, France since 1801. Currently on display is one reproduction Fardier on loan from the Deutsche Ban Museum in Nuremberg, Germany, as well as a completely functional, faithful reproduction that was created from the ground-up by The Tampa Bay Auto Museum."
So, the oldest car is on display in Paris (I have not investigated whether it works or not), and the one(s) in St. Petersburg are replicas, so nothing has yet to disprove that the car in TFA is the world's oldest working car.
Not notable? I may be confusing itracker with another tracker of that era, but wasn't itracker the one with the built-in Worm mini-game? It even had 2-player support. I have fond memories of playing 2-player Worm with others in my dorm in the mid 90's.
Aside from Worm, it was actually a very nice tracker, and had a high compatibility rate with playback of other MOD formats. I'd certainly put itracker on the list of notable trackers that advanced the then- state-of-the-art. I think I used it a lot for adding BPM events to the beginning of a lot of my old Amiga mods so that they'd play at the correct tempo on a PC, which used a different NTSC/PAL vertical scan rate timer setting or something like that to determine the beats per minute. It was the old NTSC vs. PAL Amiga problem for MOD file tempos. Or maybe it was whichever tracker used.XM as the native format, my memory is a bit hazy on that.
BTW, If you ever want to convert MOD/IT/XM/S3M/etc. to MIDI, check out the -OM output mode of TiMidity++. It does a pretty good job of it (disclaimer: I wrote a lot of the mod->midi code a long time ago).
A subpoena is a legal process and is not an invasion of your privacy. If you don't want it coming up in a court room, do not do it, say it, or write it down somewhere. Is this hard to grasp?
This is why we are upset at Apple. They should not be writing it down somewhere. While the subpoena itself may not be considered an invasion of privacy, the act of Apple recording your location (which is now being subpoenaed) most certainly is. Is this hard to grasp?
Actually, you have things reversed here. The fine *was* for releasing a butt-load of patient records, not for refusing to release patient records. What happened is that they refused for a while, then got snarky and sent them like 50 boxes of thousands of records, with the few records originally requested buried in the thousands of other records just to make life difficult for the agency requesting the original documents. I assume that the agency requesting the original documents was authorized to receive those original documents, but not authorized to receive the thousands of others that came along with them (I work in healthcare research -- trust me, getting approval to receive personally identifiable information is extremely non-trivial, they would have only been authorized to receive those documents originally requested). Bam! -- massive HIPPA fine due to the thousands of extra patient records that were released.
The original slashdot submission tried to spin it as a fine for refusing to release records, but if you RTFA you will see that it was quite the opposite. If you repeatedly obstruct an agency that can fine you, then give them the finger by burying them in 50-some boxes of unrequested documents in violation of HIPPA, you sure as Hell are going to be fined for releasing those documents.
Slashdot Mirror
A quick google search turned up the following paper
I wouldn't go so far as to say that chicken is the closest living relative to the T-Rex, just that it is the closest in sequence similarity to this particular collagen protein, out of all of the protein sequences known in 2007 (chicken could have been the only bird represented in the database at the time, but I am not going to take the time to look into this).
I just searched the GVQGPPGPQGPR T-rex collagen sequence given in the text against the NCBI nr database, which is pretty comprehensive. It yielded the following Collagen alpha-1(I) chain perfect matches:
Brachylophosaurus canadensis [dinosaur]
Tyrannosaurus rex [dinosaur]
Sarcophilus harrisii [Tasmanian devil]
Monodelphis domestica [Gray short-tailed opossum]
Corvus brachyrhynchos [American crow]
Gallus gallus [Chicken]
Manacus vitellinus [Golden-collared manakin]
Pseudopodoces humilis [Ground tit]
Anas platyrhynchos [Mallard duck]
Geospiza fortis [Medium ground finch]
Acanthisitta chloris [Rifleman]
Columba livia [Rock dove]
Melopsittacus undulatus [Parakeet]
Falco peregrinus [Peregrine falcon]
Falco cherrug [Saker falcon]
So, that's 11 birds, 1 other dinosaur, and 2 mammals (one placental, one marsupial). The list gets bigger if we relax the sequence similarity cutoff. Based on this single fragment of a sequence, we can infer that T-rex is generally more closely related to birds than to mammals or lizards (and no lizards made the top-hit list), since there were a lot more bird matches than mammals (and the lack of mammal hits is likely not due to lack of sampling relative to birds). This is a big inference to make from a single fragment of a single protein, but I'm reasonably confident that further analysis of additional T-rex sequences would strengthen this finding.
If more sequences have been published since 2007, then perhaps we could get a better idea of which modern bird T-rex is most closely related to, but there is no way to determine this from just the single example sequence above. We cannot say with any confidence that T-rex is more related to chicken than to any other bird, unless a much more thorough analysis is performed using a lot more data. Perhaps this has already been done, but I haven't taken the time to hunt for additional literature.
Autonews needs to work on their figure coloring skills. In a related article linked from the one previously mentioned, GA is colored medium orange, which indicates "Uncertain -- No formal legal or legislative challenges are known", when it should instead be colored light orange ("Legally allowed with restrictions on number of cars sold or number of stores"). From the article, it is clear that GA is legally allowed with restrictions on numbers of cars sold or number of stores, and there have clearly been formal legal or legislative challenges. Sad that they can't get their figures to match their own reporting....
If the Debian maintainers / committees are anything like Ubuntu, then I'm not at all surprised. For many years, grep -P didn't work in Ubuntu. It took them *FOUR YEARS* to fix it, with a rather bizarre discussion in the mean time. A core UNIX utility is broken and it takes four years to fix it? The earliest discussed solution, which remained the preferred solution for quite some time, was to retcon the documentation to cover it up! After 7 months, it was somehow demoted back down to "unconfirmed", and it took another 1.5 years after that re-acknowledge it was broken, after many voices of sanity finally prevailed.
After experiencing this level of cluelessness and severe disconnect with reality, I swore off Ubuntu forever. If other Linux distros are anything like the Ubuntu maintainers, I can only imagine what poor reasoning and justifications have been put forward regarding switching to systemd....
In the very early 80's, most channels did indeed not have ads. This did not last long, but I do remember that time. Greedy bastards....
I do have the option enabled to allow unobtrusive ads so at least I'm not that big of a dirtbag.
I used to allow unobtrusive ads, but then slashdot began causing my mouse pointer to turn into the busy pointer as these "non-instrusive" ads updated themselves. I don't mind static ads that don't take up much space, but once they start changing themselves on a frequent basis, which in turn causes my mouse pointer to animate, which I see out of the corner of my eye while reading the article I am interested in, then it quickly becomes intrusive. So, since non-intrusive ads have now become intrusive, I simply block them all. Screw 'em. They've used up all my good faith.
If the heating effect you propose did occur, and the liquid could be well-localized to the tumor, then this might yield an interesting treatment option. If you could cook only the tumor, and not so much the surrounding area, then perhaps this could be beneficial, especially when combined with other treatments that stress the tumor at the same time (chemo, radiation)?
I can't use IE10 or IE11 due to the forced KB2670838 update that comes with them. For me, KB2670838 breaks the Resource Monitor in Windows 7 that you can launch after bringing up the Task Manager with ctl-alt-del. I use this quite a bit to monitor memory usage of processes, disk accesses, etc. This has been a known problem for quite some time, ever since IE10 came out. Just google for "KB2670838 resource monitor". If you uninstall KB2670838 in order to get Resource Monitor to work again, it uninstalls IE10 and IE11, since evidently they depend on it for whatever reason (I am not aware of any other software that requires this update to function). I normally wouldn't be too upset over them dropping support for legacy browser versions, but if they can't get off their butts to either fix KB2670838 to not break Resource Monitor, or fix Resource Monitor to not be broken by KB2670838, then I'm going to have to give them crap over this decision. I'll start using IE11 once it stops breaking Resource Monitor.
I don't know why it will be a limited edtion, but the phrase "limited edition" scares me. I hope it doesn't turn into another LEGO Mars Rover. They started selling those this past January, and they sold out online within a few days. The same thing happened in February and March. Then, once they sold out in March, they stayed sold out, and rumor is that they may not produce any more, ever. I only found all this out in April once I asked a LEGO store clerk if they expected to get any in any time soon.
:(
It really pisses me off that A) they don't say on their website which sets will ever be sold in a physical LEGO store or not, and B) whether a set is limited edition or not, and what limited edition might mean. There was no indication that the Mars Rover would never show up physically in stores, or that it would sell out by the 3rd month of the year and never be available again. I really wanted one of these. I'd been following it for a year or so, and thought I'd just have to wait for it to show up in stores 6 months later, after demand had fallen, like the Back to the Future set did (LEGO store clerks I spoke to in store said they were selling out the day the truck came in with a shipment). If a set is really popular and selling out quickly, you'd usually expect a company to make a bunch more to sell for more profit , like they did for the Back to the Future set, but for some reason this logic was not followed for the Mars Rover.
I've been looking forward to this Female Scientists set for a while now too, and I'm worried that I won't be able to ever buy one if they follow the same pattern as the LEGO Mars Rover. Paying 2x-3x on E-Bay is not an acceptable option, and mail order from the online LEGO Store directly is generally out for me as well, since there is too much risk of delivered items being stolen off my apartment doorstep. If they follow the same pattern as the Mars Rover and don't sell these in LEGO stores, and stop selling them at all after 3-4 months, then I will be very sad
It's disastrous. cDNA is just a direct copy of the most important part of what's in the genomeâ"the actual transcript that gets used to make the final protein. This isn't a victory at all.
I agree that this isn't really a victory. The court still got things very wrong. But the above explanation isn't quite correct, either. The transcript that gets used to make the final protein would be mRNA, not cDNA.
It's still just a copy of the original, though. And a trivial copy to produce. Nature already gave us enzymes to do this, which we isolated from various bacteria (which were also patented). We then mix some stuff in a tube, and voila, we have a complementary copy of the DNA. For a not-quite-apt analogy, it would be like taking a page of text and photocopying a mirror image of it. Or, perhaps more appropriate for Slashdot, transcribing it into ROT13. However you look at it, it is a trivial to produce copy, even if it is sort of a mirror image of the original.
So, I feel that cDNA should not be patentable. It's trivial. It's obvious. It's already existing in nature. Little effort went into creating it. You should not be able to patent fragments of cDNA. Now, how you *USE* said fragments, like as a specific collection of cDNA fragments for a test kit, that's another matter, one which I don't want to get into. I don't like method patents, but that isn't the issue we're discussing right now. The court still got this wrong, due to lack of sufficient understanding of biology.
It seems like the music licensing companies in many countries are equally evil. This latest move by the Belgians is just business as usual, disgusting as it may be.
But, why do they then choose acronyms that are so easy to make fun of?
ASCAP: Ass-Cap (put a cap in yo ass)
SABAM: Sa-*BAM* (like punching someone in a Batman comic book)
I'm sure there are fun mis-pronunciations for the equivalent associations in other countries as well. Anyone from other countries want to contribute more?
I can somewhat answer the inverse of this question, though: "How many drugs do we reject in clinical trials because some researcher used the wrong animal model to test?"
My memory is a little fuzzy on the exact number from when I worked in the industry, but something like 70% of all drugs that pass Phase 1 trials fail in Phase 2 trials. Phase 1 trials are small and test for safety problems, and Phase 2 trials expand to a larger cohort to test for efficacy -- does the drug work. The pharmaceutical industry loses around 70% of all its drug candidates due to them plain not working. Often times, this is due to it working in mice/rats, but not working in humans. This isn't entirely surprising, since rodents are a good bit different than humans. Also, many animal models simply mimic human disease, rather than actually being related to how the human disease works. For example, many animal models are done over a short period of time, say 30 days or less between the initial insult (do something nasty to the rodent to induce disease-like symptoms). For inflammatory diseases, real human disease may take years from the initial problem (whatever it may be) to develop into full blown disease. When you're comparing an animal model on the time scale of a few weeks to human disease over several years, and the insult is something very very different from what it could possibly ever be in a human, it should come as no surprise that the model is often biologically very different from what is going on the human. This isn't necessarily due to rodents being too different from humans, but could easily be due to the model simply being the wrong model to mimic human disease.
Long story short, many animal models just don't do a good job at representing human disease. This is not news to anyone who has worked with them or been in the pharmaceutical industry. However, not everything is gloom and doom here. There are, actually, many animal models that *DO* do a good job of modeling human disease. The trick is to know which ones are good and which ones aren't for various diseases, drugs, pathways, etc. before you start spending the big money on clinical trials....
Back in the early to mid 90's, when I was in undergrad and using several different unix platforms (AIX, HP-UX, SunOS, Linux, DEC-OS, dumb X-terminals, etc.), different programs on different platforms treated backspace as different things. The talk/ntalk/ytalk command on HP-UX was especially annoying. It would interpret the backspace key as a ^C and kill your talk connection to your buddy across the country using his unix account to chat with you. Imagine typing away, then hitting the backspace key to fix a typo, only to have your connection killed. Sometimes shift-backspace worked (HP-UX, ftp clients, various login prompts), sometimes DEL (usually easy to fix by setting the terminal variable and/or tset), but ^H almost always worked like it should. I believe on a dumb X-terminal on my desk that I had to use to connect to a Sun server during early graduate school, ^H was the only way I could figure out how to actually issue a backspace. So, in agreement with what other posters have said, ^H isn't really important anymore. Not like it was in days of yore, when there were MANY different ways to issue a backspace, you could never be sure which would work, and the backspace key could sometimes do unexpected things. These days, backspace and delete generally do what you'd expect them to do.
:) Just don't hold down ^D at an empty unix terminal prompt, or it will auto-exit the connection. This can be especially annoying in an environment when you have multiple console windows open and you hold down ^D on a blank prompt. The first window closes, focus switches to the next window, which in turn closes due to ^D on a blank prompt, etc.. In short order, all your windows are gone, all because you started deleting at the start of the command line and it ran out of stuff to delete. I never understood why this was a "feature". I have, however, adapted and will often use ^D on a blank prompt intentionally to exit a session (it's so much faster than typing "exit") ;P
:)
To this day, I *still* automatically use shift-backspace to fix typos during login prompts, as well as ^D to forward delete instead of the delete key
A bit further off-topic, but there was one program on one system that I used one time where neither the ENTER nor the RETURN key functioned as expected. I was forced to resort to ^M to issue newlines! Ah, the days needing to know all of the alternate ^key commands
It should be one crime, one charge, but that's not required by law, so they interpret this type as shotgunning as within their requirement t prosecute to the full extent of the law. Don't like it? Change the law. Your congress-critter won't change the law? Change congress-critters -- this you CAN do.
This makes me think of the South Park rerun that was on last night or maybe the night before -- the one where the kids had to vote for the Giant Douche or the Turd Sandwich as their school mascot. When your choice is between a giant douche and a turd sandwich, it doesn't much matter which congress-critter you vote in -- neither choice will result in the outcome you desire above....
The typical mouse wheel works for zooming in and out by discrete amounts, not for something more continuous such as adjusting a photo's crop rectangle, and definitely not for rotation. Image manipulation programs designed to be used with a mouse instead use control handles of various sorts, and the user can't change the size, center, and rotation all at once the way one can with two fingers on a touch screen.
I have used 3D molecular modeling tools for years. You can get by just fine with a 3-button mouse. 3 single buttons, 3 2-button combinations = all the axes you need to translate/rotate/zoom, all continuous. You don't need a mouse wheel at all, just button combinations and intelligent movement of the mouse while the combinations are held. It's really quite intuitive and easy to use.
However, you are correct in that I was never able to zoom, translate, and rotate all in a single gesture. However, 3 separate smooth gestures is no problem at all, and (to me at least) preferable. For fine positioning, it is much better to limit movement to only one of these axes at a time, so that you do not accidentally mess up one of your axis positions while you are adjusting another to get it just right.
actually create a "sea of cautious respect" around them
Wouldn't this be a sea of cautious *disrespect*?
Google Scholar brings up a PDF file I can obtain without a subscription. So, I searched for "flav" to see what's going on here. Table 1 gives stats for "Total flavanols". The only other hits are in the references, where there are 3 references with flavonoid(s) in their title, and 2 more with flavonol(s). Now, I haven't tried to hunt down and read over these 5 cited articles, but given their titles, I think it highly likely that they do indeed cover flavonoids and not flavanoids.
Now, could flavanoid information have been taken from other citations that don't have flavanol in their title? Sure. But, since they cite 5 papers that appear to be solely dedicated to flavonol/flavonoids, and nowhere mention flavonol/flavonoids in the rest of their manuscript, I'm guessing that "flavanol" really is a typo and that they really did measure, report, and meant to talk about flavonols.
So, the criticism does appear to be valid. The only mention of flavanols in the entire manuscript does appear likely, at least to me, to be a typo meant to convey information about flavonols. Now, whether this was an intentional dishonest typo, or an honest accidental typo, I'm not going to speculate. I'm just confirming that the claim of misreporting flavonols as flavanols appears to have merit.
Like most of the research in PNAS this was not subjected to the high level of peer review expected in most scholarly journals and this paper got through without regard to its relevance and real-world significance.
I feel the need to defend PNAS here, since I actually consider it to be one of the better journals -- *IF* the manuscript has been accepted via the non- Academy of Sciences peer review process. PNAS has two (maybe three?) submission tracks: A) You are a member of the Academy of Sciences, and this results in your manuscript getting accepted more easily than usual. B) You get a friend who is an Academy member to submit your paper for you, which also lowers the bar. I'm not sure if this is really part of track A) or not, so it may or may not count as a separate track. Track C), however, is where someone who is NOT associated with the Academy submits a manuscript. Papers that come in from "external" submissions and make it past the Editor, and then all the peer review, are actually generally quite good.
So, PNAS is a mixed bag. Manuscripts from Academy members can be a bit on the sketchier side due to how the submission/review process works for them, but manuscripts from non-Academy members are often, IMHO, a good bit better than average. As with all scientific manuscripts, you must read them over carefully and determine if they have sufficiently proved their point or not.
Unfortunately, you may have a point about this particular article, since it was "Contributed by Bruce D. Hammock", who a quick Google search shows to be an Academy member.... I have not actually read the TFA, though, so I can't comment on whether it is any good or not.
"Weiss said the report says the cyber attacker hacked into the water utility using passwords stolen from a control system vendor and that he had stolen other user names and passwords."
How likely is it that a control system vendor would have the usernames and passwords of their client, used in the actual production system? Maybe they actually do, as part of some sort of remote support agreement, but if this is the case, that's already a bad security practice.
It seems more likely to me that the vendor has a list of default usernames and passwords, and THIS is what was obtained. Perhaps what Weiss *really* meant to say would be be something like: "Someone got ahold of the default usernames and passwords that our vendor uses. Since we never changed them from the default values, it's our own damn fault."
After seeing SO many stories like this, it's usually a case of not changing default passwords. Given that Weiss's statement *could* be read as I have read it, this seems the most likely scenario to me. I'm going to write this one up as stupidly bad security policies until I have sufficient evidence contradicting this assumption.
No, that would be a mellibinnium.
I looked it up at www.tbauto.com. Said car is a reproduction 1770 Fardier de Cugnot. From the website:
"The original Fardier de Cugnot has been in the collection of the Le Conservatoire de Arts et Metiers, Paris, France since 1801. Currently on display is one reproduction Fardier on loan from the Deutsche Ban Museum in Nuremberg, Germany, as well as a completely functional, faithful reproduction that was created from the ground-up by The Tampa Bay Auto Museum."
So, the oldest car is on display in Paris (I have not investigated whether it works or not), and the one(s) in St. Petersburg are replicas, so nothing has yet to disprove that the car in TFA is the world's oldest working car.
Not notable? I may be confusing itracker with another tracker of that era, but wasn't itracker the one with the built-in Worm mini-game? It even had 2-player support. I have fond memories of playing 2-player Worm with others in my dorm in the mid 90's.
.XM as the native format, my memory is a bit hazy on that.
Aside from Worm, it was actually a very nice tracker, and had a high compatibility rate with playback of other MOD formats. I'd certainly put itracker on the list of notable trackers that advanced the then- state-of-the-art. I think I used it a lot for adding BPM events to the beginning of a lot of my old Amiga mods so that they'd play at the correct tempo on a PC, which used a different NTSC/PAL vertical scan rate timer setting or something like that to determine the beats per minute. It was the old NTSC vs. PAL Amiga problem for MOD file tempos. Or maybe it was whichever tracker used
BTW, If you ever want to convert MOD/IT/XM/S3M/etc. to MIDI, check out the -OM output mode of TiMidity++. It does a pretty good job of it (disclaimer: I wrote a lot of the mod->midi code a long time ago).
unless it involves cats and cheezburgers
Something "like Rogue, but no more and no less", should be roqueequals, not roguelike.
How about equivarogue?
A subpoena is a legal process and is not an invasion of your privacy. If you don't want it coming up in a court room, do not do it, say it, or write it down somewhere. Is this hard to grasp?
This is why we are upset at Apple. They should not be writing it down somewhere. While the subpoena itself may not be considered an invasion of privacy, the act of Apple recording your location (which is now being subpoenaed) most certainly is. Is this hard to grasp?
Actually, you have things reversed here. The fine *was* for releasing a butt-load of patient records, not for refusing to release patient records. What happened is that they refused for a while, then got snarky and sent them like 50 boxes of thousands of records, with the few records originally requested buried in the thousands of other records just to make life difficult for the agency requesting the original documents. I assume that the agency requesting the original documents was authorized to receive those original documents, but not authorized to receive the thousands of others that came along with them (I work in healthcare research -- trust me, getting approval to receive personally identifiable information is extremely non-trivial, they would have only been authorized to receive those documents originally requested). Bam! -- massive HIPPA fine due to the thousands of extra patient records that were released.
The original slashdot submission tried to spin it as a fine for refusing to release records, but if you RTFA you will see that it was quite the opposite. If you repeatedly obstruct an agency that can fine you, then give them the finger by burying them in 50-some boxes of unrequested documents in violation of HIPPA, you sure as Hell are going to be fined for releasing those documents.