nmz787

anyone care to pastebin a copy of the text?

I think that's solved now though, at least for a few ICs and toolchains, via things like MyHDL and/or rhea (tldr; Python wrappers) and websites like fpga4fun.com

Why don't these numbers ever list the width AND height AND length... I'd really like to know how many atoms each transistor was composed of.

doesn't the Willamette and Columbia river run along mountain range for a long while?

Is that really smaller than any of these??? https://scholar.google.com/scholar?q=microfluidic%20qpcr

I use BRL-CAD for 3D modelling via Python (https://github.com/nmz787/python-brlcad-tcl)... using it for the base CAD tool for my nano/MEMS fabrication pipeline

I wrote a tool like this for big high-performance test boards at work, the input was a spreadsheet, and I automatically generated (visual) schematics after assigning the netlist using a constraint solver. The analog guys review and debug using the graphical schematics, their design doc, and lab tools. I started the visualization end after thinking about how tumblr packs images onto a webpage pretty well, turns out 2d and 3d shape/box packing is a rich academic field.

Oh, by 'package' I meant heat-seal in plastic bags. 'Packaging' a silicon chip for electrical use should be pretty similar regardless of the production technique, given chemical compatibility, stress/strain of the chip and how packaging would add/affect that. There's wirebonding which is basically soldering wires from the silicon to some larger package-scale traces/larger-wires (often embedded in the package structure). There are a few ways of getting the actual FIBbed gizmo onto something macro-scale. Sometimes the thing you start with is large enough to handle easily, sometimes you bring in a CNC manipulator, use FIB to solder your gizmo to the manipulator, move the manipulator elsewhere and then 'tack weld' down your gizmo there and mill away the connection to the manipulator. Some systems have micro/nano vacuum manipulators. I bet on the high-end piezos are used to move things, but I am sure at some relatively larger scale mechanical movement wouldn't be too hard to use (depending on how cheap you need things to be, and how many times you want to repeat doing such connections).

I do part time work packaging FIBbed gizmos, the 'machinist' has done at best a 50nm diameter aperture in metal film (from what I recall, maybe it was 100nm) using a beam diameter of 10nm. This is on a machine that was new 20 years ago (newer machines are probably 5 to 10X better in terms of hardware these days, maybe 50X in software). Also, ASML is researching multi-beam electron steppers and getting more traction lately: http://semiengineering.com/multi-beam-market-heats-up/ (from 2 months ago)

spectruino's ADC isn't fast enough to capture all the data from a CCD data frame, thus to get an entire spectrum one needs to sample multiple times and shift the ADC sample clock... or deal with not having all the pixels. This method would be fine if your samples aren't changing, but for something like enzyme kinetics this non-simultaneous method will likely yield poor results. For applications that can use a monochromator, this method should be fine (albeit with lower spectral resolution since monochromators usually have quite high spectral resolution)

Very good point, I would think before making a fancy case and adding useless colorful LED rings, you would try to prove the actual detection concept, which hasn't been shown by the maker.

That's exactly what expensive notch filters do.

"What happened to the FDA's mission to protect the consumer? Why aren't rice imports tested for heavy metals?"

'FDA spokesman Noah Bartolucci told BBC News that the "FDA plans to review the new research on lead levels in imported rice released today".'

Seems like they're just laggy... is there requirement in law to test one gram of every Xth ton of imported food?

I suffered through childhood lead poisoning and I'm still here on HN!

Seems like the smart thing would be pushing rendering to the client. This is already done in real-time for coarse and simple models like PDB.

Thanks for the kind words!

The $800 price tag was just a kickstarter only price, since we were still largely in the development phase we weren't sure of final pricing. Now it looks like a UV capable scientific instrument with a chinese grating would cost around $400, if you want the same optics but U.S. made it would be around $900.

I think daniel_reetz put it right with "good enough". This isn't a lab or scientific instrument. But its cheap enough to use as a teaching tool, to get people interested and in-the-know about light and its connection to common life.

using a 2D sensor, you could actually just block one half of the slit at a time with your sample, and let the other half of the slit pass through unchanged... that way you could get a calibration shot for every sample, assuming the dynamic range of the sensor was high enough that the calibration lines didn't bleed (or conversely that your sample didn't get buried in noise because exposure wasn't high enough)

You want a "peaky" light source to build the spectral response model, xenon or deuterium flashbulbs are cheap on amazon... I would lean towards using deuterium because I think the relative power of the peak to the blackbody floor (the rest of the light freqs) is less than the xenon, so you'd have less chance of the peaks dominating your sample with a less sensitive webcam type sensor

The link at: http://www.iontorrent.com/career/

just re-directs me to the homepage.

As to your last comment, JCVI already did that, synthesis is lacking for speed and cost as compared to sequencing today.

current behemoth machines have errors too, often the best way to get a really polished sequence is to sequence on machines which have different type of errors, and interlace the data appropriately.

Different here. Bug found when I switch resolution... other cams keep playing rather than pausing... thus synchronicity is lost.

I'd also like to know the answer to this question. Also isn't openFrameworks supposeds to be more frame-worky than just a library (someone mentioned earlier simplecv aims to be more of a framework rather than just a library) Did the developers not realize there are similar solutions already in existence? Why not develop those further?

That doesn't really make any comparison between open and simple CV. The example towards the end thqt compares two code snippets isn't even comparing the same operation, in the C code it creates a new image and places text on it, while the python code merely opens a file... Opening a file and displaying it in C is about one or two lines more of code