search for: 1e14

...simply scaling the data change the BIC and log likelihood values? (3) Perhaps most important, why should scaling the data change the optimum model and the number of clusters? To explore the effects of scaling the data I further scaled it by multiplying the normalized caluesby 10, by 1E4 and by 1E14. The larger the values the more negative were the BIC and log likelihood values, and the optimum model and number of clusters changed with each change to the scale of the data (though in no obvious pattern). >From my perspective the normalized values would be preferable because when there are...

Hi Bob, Thanks for sending around the link to that. It looks mostly right and looks like a useful onramp. There are a few things to watch out for though (I've cc'ed Romain so he's aware of these comments). @romain I hope you taake the following comments as they are intended, as help rather than attacks. The largest issue I see is that the contract for Get_region is that it *populates

...] pci 0000:00:1c.0: [8086:1e10] type 01 class 0x060400 [ 0.358142] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold [ 0.358225] pci 0000:00:1c.1: [8086:1e12] type 01 class 0x060400 [ 0.358362] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold [ 0.358450] pci 0000:00:1c.2: [8086:1e14] type 01 class 0x060400 [ 0.358591] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold [ 0.358632] pci 0000:00:1c.2: System wakeup disabled by ACPI [ 0.358683] pci 0000:00:1d.0: [8086:1e26] type 00 class 0x0c0320 [ 0.358706] pci 0000:00:1d.0: reg 0x10: [mem 0xf3a39000-0xf3a393ff] [...

...] pci 0000:00:1c.0: [8086:1e10] type 01 class 0x060400 [ 0.324788] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold [ 0.324840] pci 0000:00:1c.1: [8086:1e12] type 01 class 0x060400 [ 0.324992] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold [ 0.325040] pci 0000:00:1c.2: [8086:1e14] type 01 class 0x060400 [ 0.325199] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold [ 0.325266] pci 0000:00:1d.0: [8086:1e26] type 00 class 0x0c0320 [ 0.325306] pci 0000:00:1d.0: reg 10: [mem 0xf2539000-0xf25393ff] [ 0.325473] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold...

...] pci 0000:00:1c.0: [8086:1e10] type 01 class 0x060400 [ 0.314535] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold [ 0.314674] pci 0000:00:1c.1: [8086:1e12] type 01 class 0x060400 [ 0.314799] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold [ 0.314933] pci 0000:00:1c.2: [8086:1e14] type 01 class 0x060400 [ 0.315069] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold [ 0.315141] pci 0000:00:1c.2: System wakeup disabled by ACPI [ 0.315221] pci 0000:00:1d.0: [8086:1e26] type 00 class 0x0c0320 [ 0.315271] pci 0000:00:1d.0: reg 0x10: [mem 0xed939000-0xed9393ff] [...

Hello, following up on myself, it was suggested on IRC that I better attach a dmesg output. Here's the output of a clean boot & echo 0f > /sys/.../pstate cycle. I can't spot a message that relates to the reclock action, and there's only one weird "nouveau 0000:04:00.0: clk: base: 7 MHz, boost: 7 MHz" message. On the other hand: # cat

Which consumer-priced 1.5TB drives do people currently recommend? I had zero read/write/checksum errors so far in 2 years with my trusty old Western Digital WD7500AAKS drives, but now I want to upgrade to a new set of drives that are big, reliable and cheap. As of Jan 2010 it seems the price sweet spot is the 1.5TB drives. As I had a lot of success with Western Digital drives I thought I would