I'm not sure which game this is more like. On the one hand, the outward intention seems to be similar to that of the Microwave Receiver Dish in Sim City 2000:
MICROWAVE RECEIVER DISH - launch a satellite to collect solar power, then beam it down to Earth. Microwave power is very efficient, clean and reliable. Unfortunately, the effects of a mis-targeted beam are as yet unknown However, some discussion has commented on the deliberate mis-targeting of the beam, which reminds me of Command & Conquer:
Ion Cannon Ready... Select Target
I try it again. It is a bit like touching a red-hot wire, but there is no heat, only the sensation of heat. There is no burn mark or blister. [FTFA] All we need now is a Gom jabbar, and the Bene Gesserit training can begin.
That's gotta be the best... until someone decides to go to seven.
I suppose the ultimite end-point of this would be the Intel infinium, defined as "as many processors as we could cram onto a motherboard, minus the ones that didn't work".
It's a new method of measuring things, the metre-picohecto (at least, that's what I interpret mph as being in SI units (http://physics.nist.gov/cuu/Units/units.html)). It's a way of recording inverted distances, useful when tracking things that aren't where you expect them to be.
There's a bit of stuff around about how to do this well in things such as questionnaire databases. The general method is something like storing as {PersonID, AttributeID, Data}, with a primary key being the combination of PersonID, AttributeID. It works really well for data retrieval, as long as you're not scared off by using joins (e.g. to work out what AttributeID 6 means) in each query.
I've run into this very problem (not having enough columns) with a database I have been working on. The questionnaire had around 300 individual questions, which exceeded [shudder] Microsoft Access' limitations. The solution by the person who worked on this database previously was to split the questionnaire up into sections, resulting in many different tables for the same questionnaire. This was very difficult to pull data out of (I had to know each column name before I could pull out the data, and in most cases it wasn't obvious) and maintain (Each new question added needed a custom designed field in the forms associated with it).
I ended up spending around 2 weeks redesigning the database (with a few tables in the 3-column format mentioned) to be easier to query, and then mentioned to various people that a better solution was required (i.e. not Access). One year later, that's pretty much implemented, and hopefully we now have a good working solution that is both easy to query, easy to modify, and can support our data warehouse needs for a long time.
If there were a drive to get through an ISO specification on ISO corruption (i.e. the recommended way to influence others to get the specification you want), would that also be corrupted? And if so, would the corruption follow the procedure in the specification?
This is more like a 2-3 year strategy to force people away from XP and perhaps even Wine/Cedega. That would be a bit odd, considering Wine is likely to implement DX10 sometime in the future (probably within 2-3 years). Once that happens, DX10 may be able to be implemented in XP via OpenGL.
The Windows version allows Wine developers to test out the completeness of Wine DLLs by replacing those on Windows. At least for now, this is mainly for developers. However, in the future once we finish our DirectX 10 implementation, we may be able to implement Direct3D 10 in Windows XP the same way it runs in Wine: by translating DirectX calls to OpenGL ones. [from http://wiki.winehq.org/FAQ%5D
Also in the FAQ:
The Windows version allows Wine developers to test out the completeness of Wine DLLs by replacing those on Windows. At least for now, this is mainly for developers. However, in the future once we finish our DirectX 10 implementation, we may be able to implement Direct3D 10 in Windows XP the same way it runs in Wine: by translating DirectX calls to OpenGL ones. Oh, and I noticed that someone mentioned DOSBOX.... It's in the App database, so someone has decided that it could be worthy of running under Wine, possibly for similar testing reasons:
it's closer to a "macross space combat emulator" than a space combat sim in the tradition of Wing Commander, TIE Fighter / X-Wing, Freespace, etc. Well, there's always privateer, which is in a bit of development at the moment.
I think they meant the first geothermal plant using deliberately injected water as opposed to heated water/steam that occurs naturally. Oh, right. I get you now. You mean something like this:
http://www.nzgeothermal.org.nz/geothermal_energy/n z_geothermal_fields.asp#Wairakei_Tauhara
Separated water from the Wairakei field is used to provide fluids for the Netcor tourist facility, and a heat source for a prawn farm adjacent to the Wairakei power station. About half of the separated water is now reinjected and half is discharged to the Waikato River. Or...
The station currently generates around 200 GWh per year. About half of the steam condensate is reinjected while the remainder is discharged to air through the cooling towers. Then again, having not read the article, I suppose this could be describing injection into dry rock, which then means that it's not possible to (initially) use water that didn't originate at the heat source.
ISA slots were available long after most of us had ditched our old ISA peripherals. You Insensitive Clod! I still have an ISA modem. Works much better than those silly winmodems, too.
A book? Sorry, I'm not well read enough in that area (hopefully, I'll be a bit better read over the next six months...). That six generation stuff is some chromosome crossover/simulation tests I did (in Excel, of all languages!) at the start of my PhD research. I assumed 2-3 points of recombination per chromosome per generation, and picked points randomly across chromosomes. This is a picture I often show to demonstrate how much information can be transferred in a single chromosome — that's 4 generations and there's no "blue" information left in that chromosome, but my rough eyeball of a few crossovers suggests 5-6 is about the best you could do unless you're really lucky. I'm currently in the process of trying to work out how close I can get to that 5-6 generations of information in real life. One of the more tricky things I've been trying to work out is which pieces of DNA are most useful for doing this.
It is somewhat possible to derive ancestry trees from DNA by comparing individuals within a group, based on the number of differences between individuals. This is becoming more common in species determination — researchers wanting to know if the new thing they have found is a new species, or a variant of something discovered previously. I prefer seeing DNA as being a tool for genealogy, rather than a final solution, mostly due to the random nature of mutations and recombination.
Watch this space, I guess. I may have a better answer for you (hopefully in the form of a PhD thesis) in just over a year.
I don't know, but another interesting point about that century is that it was the last turning point in population size. I guess if you go back further from there, you hit many more people who had lines that died out (lots more potential for false positive matches). From http://zebu.uoregon.edu/1998/es202/archive/l13a.ht ml:
# 1000 AD 0.25 Billion # 1100 AD 0.30 # 1200 AD 0.36 # 1250 AD 0.40 # 1300 AD 0.36 # 1350 AD 0.44 # 1400 AD 0.35 # 1500 AD 0.43 # 1600 AD 0.55 # 1650 AD 0.47
DNA on the other hand is still lateral in time and not vertical. Unless you want to test a corpse you can't go back many generations.
Not quite sure what you mean by "many".
It should be possible, through looking at autosomal DNA, to look up to six generations back — to me, that's "many" — possibly a bit longer with the X chromosome (because there's less recombination). Other non-recombinant DNA (Y-chromosome, mitochondria) are good for maybe 600+ years back, but only along one line of ancestry (more recent than that, and there tends to not be enough variation), so could potentially be used for really long-range ancestry. The "only one line" is a problem, but perhaps not all that much of one that far back, considering the exponential rate of population growth.
The rest is just a matter of a few million mutations scattered throughout the genome. Oh, and the bits of the genome that are proving to be very difficult to sequence.
Do they think the language of DNA is context free?
I'll let you know in about 10 years (that's at least as long as I expect it to take to answer that question). I'm very interested in exploring the language and grammar of DNA after I finish my PhD.
Slashdot Mirror
How about something like this:
/dev/null --referer=http://www.cybertriallawyer.com/ http://www.cybertriallawyer.com/; done
/dev/null points to the usual place), but it would still come up on their logs as the same.
while true; do wget -O
That way, you're not actually looking at the code (assuming
The George Bush View:
No rights are irrevocable!
I, for one, have been welcoming our new, irregular, old verb laws.
Damn....
Then again. It's a jury trial, which I recall people preferring when they think they'll lose.
It's not out of the question. After all, Gillette went to 5 blades, an aloe strip and a trimmer blade:
http://www.gillettefusion.com/us/lowband.asp
That's gotta be the best... until someone decides to go to seven.
I suppose the ultimite end-point of this would be the Intel infinium, defined as "as many processors as we could cram onto a motherboard, minus the ones that didn't work".
It's a new method of measuring things, the metre-picohecto (at least, that's what I interpret mph as being in SI units (http://physics.nist.gov/cuu/Units/units.html)). It's a way of recording inverted distances, useful when tracking things that aren't where you expect them to be.
There's a bit of stuff around about how to do this well in things such as questionnaire databases. The general method is something like storing as {PersonID, AttributeID, Data}, with a primary key being the combination of PersonID, AttributeID. It works really well for data retrieval, as long as you're not scared off by using joins (e.g. to work out what AttributeID 6 means) in each query.
I've run into this very problem (not having enough columns) with a database I have been working on. The questionnaire had around 300 individual questions, which exceeded [shudder] Microsoft Access' limitations. The solution by the person who worked on this database previously was to split the questionnaire up into sections, resulting in many different tables for the same questionnaire. This was very difficult to pull data out of (I had to know each column name before I could pull out the data, and in most cases it wasn't obvious) and maintain (Each new question added needed a custom designed field in the forms associated with it).
I ended up spending around 2 weeks redesigning the database (with a few tables in the 3-column format mentioned) to be easier to query, and then mentioned to various people that a better solution was required (i.e. not Access). One year later, that's pretty much implemented, and hopefully we now have a good working solution that is both easy to query, easy to modify, and can support our data warehouse needs for a long time.
If there were a drive to get through an ISO specification on ISO corruption (i.e. the recommended way to influence others to get the specification you want), would that also be corrupted? And if so, would the corruption follow the procedure in the specification?
Er, sorry. My quote was from the FAQ on the wiki:
http://wiki.winehq.org/FAQ
http://www.winehq.org/site/docs/wine-faq/index#WI
Also in the FAQ: The Windows version allows Wine developers to test out the completeness of Wine DLLs by replacing those on Windows. At least for now, this is mainly for developers. However, in the future once we finish our DirectX 10 implementation, we may be able to implement Direct3D 10 in Windows XP the same way it runs in Wine: by translating DirectX calls to OpenGL ones. Oh, and I noticed that someone mentioned DOSBOX.... It's in the App database, so someone has decided that it could be worthy of running under Wine, possibly for similar testing reasons:
http://appdb.winehq.org/appview.php?iVersionId=88
... but why let the constitution get in the way of national security?
Well, let's think about this:
245mW laser (from article), 2*1700mAh alkaline battery (the low-end from http://en.wikipedia.org/wiki/AA_battery)
2*1700mAh / 245mW = approx. approx. 13.877551 h, so a bit under 14 hours.
Gosh, that seems like quite a long time. I guess the diode would overheat well before that if that were continuous drain.
http://www.nzgeothermal.org.nz/geothermal_energy/
A book? Sorry, I'm not well read enough in that area (hopefully, I'll be a bit better read over the next six months...). That six generation stuff is some chromosome crossover/simulation tests I did (in Excel, of all languages!) at the start of my PhD research. I assumed 2-3 points of recombination per chromosome per generation, and picked points randomly across chromosomes. This is a picture I often show to demonstrate how much information can be transferred in a single chromosome — that's 4 generations and there's no "blue" information left in that chromosome, but my rough eyeball of a few crossovers suggests 5-6 is about the best you could do unless you're really lucky. I'm currently in the process of trying to work out how close I can get to that 5-6 generations of information in real life. One of the more tricky things I've been trying to work out is which pieces of DNA are most useful for doing this.
It is somewhat possible to derive ancestry trees from DNA by comparing individuals within a group, based on the number of differences between individuals. This is becoming more common in species determination — researchers wanting to know if the new thing they have found is a new species, or a variant of something discovered previously. I prefer seeing DNA as being a tool for genealogy, rather than a final solution, mostly due to the random nature of mutations and recombination.
Watch this space, I guess. I may have a better answer for you (hopefully in the form of a PhD thesis) in just over a year.
Whoops... just noticed that there was a dip in 1650 as well, so not the last turning point then...
v e.svg [for more yummy data]
http://en.wikipedia.org/wiki/Image:Population_cur
I don't know, but another interesting point about that century is that it was the last turning point in population size. I guess if you go back further from there, you hit many more people who had lines that died out (lots more potential for false positive matches). From http://zebu.uoregon.edu/1998/es202/archive/l13a.ht ml:
# 1000 AD 0.25 Billion
# 1100 AD 0.30
# 1200 AD 0.36
# 1250 AD 0.40
# 1300 AD 0.36
# 1350 AD 0.44
# 1400 AD 0.35
# 1500 AD 0.43
# 1600 AD 0.55
# 1650 AD 0.47
Not quite sure what you mean by "many".
It should be possible, through looking at autosomal DNA, to look up to six generations back — to me, that's "many" — possibly a bit longer with the X chromosome (because there's less recombination). Other non-recombinant DNA (Y-chromosome, mitochondria) are good for maybe 600+ years back, but only along one line of ancestry (more recent than that, and there tends to not be enough variation), so could potentially be used for really long-range ancestry. The "only one line" is a problem, but perhaps not all that much of one that far back, considering the exponential rate of population growth.
Here's most of it (you can select other chromosomes for downloading through that interface):
http://www.ncbi.nlm.nih.gov/mapview/seq_reg.cgi?t
The rest is just a matter of a few million mutations scattered throughout the genome. Oh, and the bits of the genome that are proving to be very difficult to sequence.