Maybe the "good old-fashioned investigative work by the various authorities" came after NSA monitoring. Maybe the NSA doesn't want you to know that it's been involved in this case.
In order to plan an energy strategy, you need to look 20-30 years ahead. In order to avoid financial meltdown, you need to make Wall Street happy before next quarter.
Your description is correct for concentrated systems with fewer suns. But the cell we're talking about is about 2mm in diameter, and the tracking system needs to work within 0.1 accuracy. The modules deliver exactly 0Wp as soon as the tracker isn't properly aligned, so it needs to be moved constantly throughout the day.
Give credits to this company. They have fields in Spain, USA & Israel (http://www.soitec.com/en/products-and-services/solar-cpv/our-references/) with about 25% of system efficiency. This takes into account optical losses, cell efficiency, module efficiency, module mismatch, inverter efficiency, cable losses, etc etc... It's not 45%, but it's twice as much as any other PV installation. Nobody will ever achieve 44.7% system efficiency, but Concentrix does a pretty good job at implementing those cells in their system. The modules aren't that expensive, because Fresnel lenses are cheap, and the cells are so small (about 1mm). You need places with very high direct radiation levels and very good 2-axis trackers, though.
Maybe you could give an example of a "good programming language"?
Because "concise set of commands" and "concise code" seem to be contradictory. To each his own, but I really like Ruby programs because they're usually much shorter and to the point, than say, Java, C or PHP equivalent.
I know I'm biased because I work with Ruby on a daily basis, but I think:
1.upto(10).each{|i| print i}
is self documenting. Who cares if you could write an equivalent with
Range.new(1,10).each{|i| print i}
or
for i in [1,2,3,4,5,6,7,8,9,10] do
print i end
?
Given the properties you're looking for, I suppose you prefer Python over Ruby. The equivalent Python code is:
for i in range(1,11):
print i
Is it really self-documenting?
Coming from other programming languages, it is liberating to discover Blocks, method_missing and stuff like that.
Anyway, it's clear that Ruby isn't the solution to every problem, but it definitely is a great tool for many different purposes. For other jobs, Python, C, Prolog or Caml might be better suited.
I'm still a bit sleepy, but I think that : "I will use anything not made in America" isn't equivalent to "I will not use anything made in America". Slashdot is a no go for the latter, but it's okay for the former. Am I not unright, yes?
It must confess that it already happened to me : I wanted to backup a 8GB/home partition on an 16GB FAT32 SD-Card. I was surprised at how good the "compression" was : the tgz file was only 4GB!:D
Great. With their policy of needing to sign-in in order to download anything (script, picture,...), I bet they have way more information than they needed to have. And this information is now compromised....
Linux Mint + MATE has replaced my Ubuntu + Gnome/KDE, and probably will be replaced some day by Mint + Cinnamon. I don't care which directions Gnome 3 and KDE 4 are going.
Also, I suppose the code was written either by a Python novice or a FORTRAN expert:D I'm more of a Ruby guy, but I learned Python a few months ago, and one nice thing about it are list comprehensions (the syntax will probably get messed up by/.):
x_n = [2,8,7,9,-5,0,2] y_n = [1,-3,10,0,8,9,1]
def between(numbers,low,high):
return [x for x in numbers if x>low and xhigh]
def common(list1,list2):
return [x for x in list1 if x in list2]
Slashdot Mirror
Maybe the "good old-fashioned investigative work by the various authorities" came after NSA monitoring.
Maybe the NSA doesn't want you to know that it's been involved in this case.
Holy fucking cow.
Two worlds collide :
In order to plan an energy strategy, you need to look 20-30 years ahead.
In order to avoid financial meltdown, you need to make Wall Street happy before next quarter.
Your description is correct for concentrated systems with fewer suns.
But the cell we're talking about is about 2mm in diameter, and the tracking system needs to work within 0.1 accuracy.
The modules deliver exactly 0Wp as soon as the tracker isn't properly aligned, so it needs to be moved constantly throughout the day.
Actually it's a 4cm*4cm fresnel lens focusing on a 2mm diameter cell. http://www.soitec.com/en/technologies/concentrix/components/
Give credits to this company.
They have fields in Spain, USA & Israel (http://www.soitec.com/en/products-and-services/solar-cpv/our-references/) with about 25% of system efficiency.
This takes into account optical losses, cell efficiency, module efficiency, module mismatch, inverter efficiency, cable losses, etc etc...
It's not 45%, but it's twice as much as any other PV installation.
Nobody will ever achieve 44.7% system efficiency, but Concentrix does a pretty good job at implementing those cells in their system.
The modules aren't that expensive, because Fresnel lenses are cheap, and the cells are so small (about 1mm).
You need places with very high direct radiation levels and very good 2-axis trackers, though.
They use Fresnel lenses, not mirrors : http://www.soitec.com/en/technologies/concentrix/components/
PS: I worked with Concentrix (now Soitec). Cool company.
Also, what prevents you from ignoring it if you don't like it?
One more reason to try LXDE, MATE or Cinnamon.
Also, relatively simple one-liners leave precious vertical space for more important parts of the code.
Maybe you could give an example of a "good programming language"?
Because "concise set of commands" and "concise code" seem to be contradictory.
To each his own, but I really like Ruby programs because they're usually much shorter and to the point, than say, Java, C or PHP equivalent.
I know I'm biased because I work with Ruby on a daily basis, but I think :
1.upto(10).each{|i| print i}
is self documenting.
Who cares if you could write an equivalent with
Range.new(1,10).each{|i| print i}
or
for i in [1,2,3,4,5,6,7,8,9,10] do
print i
end
?
Given the properties you're looking for, I suppose you prefer Python over Ruby. :
The equivalent Python code is
for i in range(1,11):
print i
Is it really self-documenting?
Coming from other programming languages, it is liberating to discover Blocks, method_missing and stuff like that.
Anyway, it's clear that Ruby isn't the solution to every problem, but it definitely is a great tool for many different purposes. For other jobs, Python, C, Prolog or Caml might be better suited.
I'm still a bit sleepy, but I think that :
"I will use anything not made in America" isn't equivalent to "I will not use anything made in America".
Slashdot is a no go for the latter, but it's okay for the former.
Am I not unright, yes?
Yeah right.
What's the probability of an elephant knocking on your door today?
50%...
Google *is* the ad industry.
+1
Well, we're still underestimating the level of risk related to peak oil and global warming.
Those are bigger problems than buildings collapse.
It must confess that it already happened to me : /home partition on an 16GB FAT32 SD-Card. :D
I wanted to backup a 8GB
I was surprised at how good the "compression" was : the tgz file was only 4GB!
Hell yeah.
I don't understand your message.
Great. ...), I bet they have way more information than they needed to have.
With their policy of needing to sign-in in order to download anything (script, picture,
And this information is now compromised....
Linux Mint + MATE has replaced my Ubuntu + Gnome/KDE, and probably will be replaced some day by Mint + Cinnamon.
I don't care which directions Gnome 3 and KDE 4 are going.
I thought so too, but it appears to be wrong :
http://en.wikipedia.org/wiki/List_of_wars_by_death_toll
THE BRAND NEW iPad Mini Mega :D
http://www.youtube.com/watch?v=abtmeXXT7VA
Also, due to limited budget, some police stations have Word installed on some computers and Excel on others.
Want to copy/paste? Too bad.
Also, I suppose the code was written either by a Python novice or a FORTRAN expert :D /.):
I'm more of a Ruby guy, but I learned Python a few months ago, and one nice thing about it are list comprehensions (the syntax will probably get messed up by
x_n = [2,8,7,9,-5,0,2]
y_n = [1,-3,10,0,8,9,1]
def between(numbers,low,high):
return [x for x in numbers if x>low and xhigh]
def common(list1,list2):
return [x for x in list1 if x in list2]
x_btwn = between(x_n,2,10)
y_btwn = between(y_n,-2,9)
print x_btwn
print y_btwn
print common(x_btwn,y_btwn)