Isn't it time/. got a "-1 Reply Abuse" mod? The parent reply has nothing to do with the GP. It's on topic, and maybe it deserves the "Insightful" mod -- but it's replying to the top post just to appear at the top of the page.
STOP THE MADNESS!
Nobody really writes applications for X anymore [...]
I must be a "nobody", because I just spent the last few hours adding a "plasma-saver" bar (a black veritical bar marching across the transparent lock) to alock. Of course, starting with someone else's code is way different than writing from scratch.
It's easy -- you ask people you've never asked before: "Hey, do you have any data centers?". In other words, no one was keeping track before. Missions/projects setup data centers as-needed, but were not required to report them as a new "data center" to anyone.
I don't think it's surprising to find that the estimate was wrong. I know that where I work, funding plays a huge part in the creation of "islands" of IT resources. Every project pays for their own resources, and no one wants to share. Until this data center consolidation effort, there was no real impetus for creating pooled data centers.
Server-based and gatekeeper solutions are useless when the compromise comes from other systems on the same network. Especially when the guy next to you clicks on a genuine-looking link in a forged email:-P
The full article notes that simple contamination wouldn't have generated enough tetracycline to match what they detected.
The extent of the [osteon] labeling suggests that the population received tetracycline during osteon mineralization, which occurs during periods of ~80 days. This finding contradicts the notion that the osteons were labeled by a one time event of bacterial
contamination of grains or foodstuffs. [...]In contrast, surface inoculation
of cracked and water-treated grains would produce tetracycline, but in low yields compared with liquid fermentation
So, the population must have cultured this brew to generate enough tetracycline. Whether it was deliberate (because they knew it had health benefits) or just a happy accident that they kept using the right culture is unanswered.
I did not know that, thank you. I didn't bother testing only applying 9.3.2 -- I just tacked the extra patch onto the end and it worked, so I left it at that.
That "Wizard" is practically useless -- the updates for it lag so far behind the Reader releases that half of the functions (like removing the icon from the desktop) stop working. For example, the function to prevent the creation of the desktop icon no longer works.
I've found it more reliable to script the installation, removing the desktop icon using the script (%ALLUSERSPROFILE%\Desktop\Adobe Reader 9.lnk or %PUBLIC%\Desktop\Adobe Reader 9.lnk)
I had a horrible experience with a AutoIT GUI program because their API changed quite a bit between releases. I don't recommend it to anyone anymore because of that.
AutoIt is nice -- the first time. That's how they hook you.
Then, a year later, you decide to update your program. And hey, why not update to the latest version of AutoIt while you're at it? There was this one bug that always annoyed you, and you hope the devs fixed it.
Well, guess what? While you had your back turned, all the APIs for the GUI changed. All those calls you made to AwesomeFunction() now require 4 arguments instead of 3. Oh, and one of them is now an object instead of string.
That was my personal experience, anyway. After wroting a GUI program with perhaps 3000 lines of code, I updated to the new version of AutoIt. It seemed I had to practically rewrite the entire thing. Since then, I haven't recommended AutoIt to anyone that I like.
That's why I downloaded everything at home, and am seeding from there. Of course it's only a measly FIOS connection. Downloading from the NASA and LMSAL sites is probably going to be faster in any case.
Depends on the flight path. Flights that go to high latitudes (great cirle routes over the north pole) sometimes lose communications due to (currently unpredicted) solar events. They are not allowed to fly without communications, so they have to divert to more southerly routes to restore comm. Of course this takes more time and fuel -- perhaps even forcing a landing at a closer airport.
Accurate predictions of solar events would allow the airline industry to plan better.
Flight operations for the spacecraft is at GSFC, while instrument operations can be done at both GSFC and at the science operations centers.
Science data is stored temporarily ( up to 30 days) at the dedicated ground stations at White Sands. The data is transferred in close to real-time (OC-3 lines for HMI/AIA, DS-3 for EVE) from there to each of the science instrument data centers (LASP for EVE, and JSOC at Stanford for HMI and AIA).
So, in this case it is the science teams (not NASA) that must store and process massive amounts of data. Perhaps obviously, none of the science data processing is done at GSFC (only engineering data).
Actually, you can find some documents online for HMI/AIA by searching Google for "jsoc sdp".
Recently, we allowed our teenager to get a Facebook account, with the proviso that we remain her friends and that we have access to the account. I reply to every post she makes abusively correcting her piss-poor grammar.
She probably just hides your responses (she never sees them)!:)
You can use the Adobe Javascript Blacklist Framework to block the vulnerable function completely, so that no matter what the (non-admin) user does, they cannot execute the Javascript. They still get prompted about the Javascript, but it won't execute.
More information about mitigating the vulnerability using this method is here:
Also I'm sure you already know this, but for the rest of the/. crowd: SpaceWire is an existing standard bus (like a router), but it doesn't currently have any PnP features.
In the August AIAA paper (2009-4877), the diameter of the test chamber greatly influenced the Isp and exhaust velocity. They tested three diameters -- 0.75 in, 1.5 in, and 3 in.
Values below are averages (except the peak row)
motor size 0.5" 1.5" 3.0" exhaust velocity (m/s) 528 784 848 Isp (s) 56 83 133 Isp (peak) (s) 97 124 203
The paper notes that the motors were not optimized. Higher pressures in the combustion chamber would result in higher efficiency. Also, they speculate that increasing the equivalence ratio (fuel-to-oxidizer ratio) would increase combustion efficiency.
Slashdot Mirror
Isn't it time /. got a "-1 Reply Abuse" mod? The parent reply has nothing to do with the GP. It's on topic, and maybe it deserves the "Insightful" mod -- but it's replying to the top post just to appear at the top of the page.
STOP THE MADNESS!
Can you please elaborate on why you have 15 speakers? Are they all in one normal-sized room, or is it theater-sized? Scattered through a house?
I must be a "nobody", because I just spent the last few hours adding a "plasma-saver" bar (a black veritical bar marching across the transparent lock) to alock. Of course, starting with someone else's code is way different than writing from scratch.
It's easy -- you ask people you've never asked before: "Hey, do you have any data centers?". In other words, no one was keeping track before. Missions/projects setup data centers as-needed, but were not required to report them as a new "data center" to anyone.
I don't think it's surprising to find that the estimate was wrong. I know that where I work, funding plays a huge part in the creation of "islands" of IT resources. Every project pays for their own resources, and no one wants to share. Until this data center consolidation effort, there was no real impetus for creating pooled data centers.
Server-based and gatekeeper solutions are useless when the compromise comes from other systems on the same network. Especially when the guy next to you clicks on a genuine-looking link in a forged email :-P
The extent of the [osteon] labeling suggests that the population received tetracycline during osteon mineralization, which occurs during periods of ~80 days. This finding contradicts the notion that the osteons were labeled by a one time event of bacterial contamination of grains or foodstuffs. [...]In contrast, surface inoculation of cracked and water-treated grains would produce tetracycline, but in low yields compared with liquid fermentation
So, the population must have cultured this brew to generate enough tetracycline. Whether it was deliberate (because they knew it had health benefits) or just a happy accident that they kept using the right culture is unanswered.
I guess you think "2ndcoming" is nothing like "W8"
I did not know that, thank you. I didn't bother testing only applying 9.3.2 -- I just tacked the extra patch onto the end and it worked, so I left it at that.
I agree, but you can work around this using the command line. (I know, it sucks to have to do this!)
/passive /i AdbeRdr930_en_US.msi PATCH=AdbeRdrUpd931_all_incr.msp;AdbeRdrUpd932_all_incr.msp
Download the full MSI installer for 9.3.0, plus the patches for 9.3.1 and 9.3.2 (etc) from ftp://ftp.adobe.com/pub/adobe/reader/win/9.x/
Then, install with:
msiexec
That "Wizard" is practically useless -- the updates for it lag so far behind the Reader releases that half of the functions (like removing the icon from the desktop) stop working. For example, the function to prevent the creation of the desktop icon no longer works.
I've found it more reliable to script the installation, removing the desktop icon using the script (%ALLUSERSPROFILE%\Desktop\Adobe Reader 9.lnk or %PUBLIC%\Desktop\Adobe Reader 9.lnk)
I had a horrible experience with a AutoIT GUI program because their API changed quite a bit between releases. I don't recommend it to anyone anymore because of that.
See my comment above:
http://ask.slashdot.org/comments.pl?sid=1666054&cid=32360238
AutoIt is nice -- the first time. That's how they hook you.
Then, a year later, you decide to update your program. And hey, why not update to the latest version of AutoIt while you're at it? There was this one bug that always annoyed you, and you hope the devs fixed it.
Well, guess what? While you had your back turned, all the APIs for the GUI changed. All those calls you made to AwesomeFunction() now require 4 arguments instead of 3. Oh, and one of them is now an object instead of string.
That was my personal experience, anyway. After wroting a GUI program with perhaps 3000 lines of code, I updated to the new version of AutoIt. It seemed I had to practically rewrite the entire thing. Since then, I haven't recommended AutoIt to anyone that I like.
Seriously.. what kind of web security lab forces users to enable javascript to view content?
IMO, this site gives Stanford security researchers a bad image.
That's why I downloaded everything at home, and am seeding from there. Of course it's only a measly FIOS connection. Downloading from the NASA and LMSAL sites is probably going to be faster in any case.
http://aia.lmsal.com/public/firstlight.html
In the "Movies" section.
I am seeding! I imagine until we get a lot of peers direct download from the websites will be better
So, if you download from the web, please seed them :)
http://sdo.gsfc.nasa.gov/firstlight/
http://aia.lmsal.com/public/firstlight.html
Depends on the flight path. Flights that go to high latitudes (great cirle routes over the north pole) sometimes lose communications due to (currently unpredicted) solar events. They are not allowed to fly without communications, so they have to divert to more southerly routes to restore comm. Of course this takes more time and fuel -- perhaps even forcing a landing at a closer airport.
Accurate predictions of solar events would allow the airline industry to plan better.
Well, this is my first attempt at a torrent; hope this works
http://www.seedpeer.com/details/3024437/SDO.html
Sorry, you can't see the design documents! :-P
Flight operations for the spacecraft is at GSFC, while instrument operations can be done at both GSFC and at the science operations centers.
Science data is stored temporarily ( up to 30 days) at the dedicated ground stations at White Sands. The data is transferred in close to real-time (OC-3 lines for HMI/AIA, DS-3 for EVE) from there to each of the science instrument data centers (LASP for EVE, and JSOC at Stanford for HMI and AIA).
So, in this case it is the science teams (not NASA) that must store and process massive amounts of data. Perhaps obviously, none of the science data processing is done at GSFC (only engineering data).
Actually, you can find some documents online for HMI/AIA by searching Google for "jsoc sdp".
Recently, we allowed our teenager to get a Facebook account, with the proviso that we remain her friends and that we have access to the account. I reply to every post she makes abusively correcting her piss-poor grammar.
She probably just hides your responses (she never sees them)! :)
You can use the Adobe Javascript Blacklist Framework to block the vulnerable function completely, so that no matter what the (non-admin) user does, they cannot execute the Javascript. They still get prompted about the Javascript, but it won't execute.
More information about mitigating the vulnerability using this method is
here:
http://kb2.adobe.com/cps/532/cpsid_53237.html
More general information about the framework is here:
http://kb2.adobe.com/cps/504/cpsid_50431.html
I lost a lot of respect for Phil Plait when he released a book called "DEATH FROM THE SKIES!!!!!" Is that really who we want to represent NASA?
Excuse me, did you just say that learning about baseball is education? Or am I misunderstanding you?
You mentioned the existing PnP spec, but didn't provide any details! The effort is called Space Plug and Play Avionics (SPA).
Also I'm sure you already know this, but for the rest of the /. crowd: SpaceWire is an existing standard bus (like a router), but it doesn't currently have any PnP features.
In the August AIAA paper (2009-4877), the diameter of the test chamber greatly influenced the Isp and exhaust velocity. They tested three diameters -- 0.75 in, 1.5 in, and 3 in.
Values below are averages (except the peak row)
motor size
0.5" 1.5" 3.0"
exhaust velocity (m/s) 528 784 848
Isp (s) 56 83 133
Isp (peak) (s) 97 124 203
The paper notes that the motors were not optimized. Higher pressures in the combustion chamber would result in higher efficiency. Also, they speculate that increasing the equivalence ratio (fuel-to-oxidizer ratio) would increase combustion efficiency.