Topic for #homecmos is now Homebrew CMOS and MEMS foundry design | http://code.google.com/p/homecmos/ | Logs: http://en.qi-hardware.com/homecmos-logs/
lekernel [lekernel!~lekernel@g225039244.adsl.alicedsl.de] has joined #homecmos
wolfspraul [wolfspraul!~wolfsprau@221.217.224.207] has joined #homecmos
soul-d [soul-d!~main@88.159.111.237] has joined #homecmos
c1de0x [c1de0x!~c1de0x@208.111.44.254] has joined #homecmos
wolfspraul [wolfspraul!~wolfsprau@123.125.157.59] has joined #homecmos
wolfspraul [wolfspraul!~wolfsprau@222.130.118.13] has joined #homecmos
azonenberg [azonenberg!~azonenber@cpe-67-246-33-188.nycap.res.rr.com] has joined #homecmos
someguy [someguy!601846b4@gateway/web/freenode/ip.96.24.70.180] has joined #homecmos
<someguy> if you write a follow up paper that describes why some experimental result happens with additional new data using new characterization methods, what would you call it? for example, review papers give a broad view of the state of the art of one field
<soul-d> <first paper's name> The sequel
<humble_hoser> are you following up on your own paper, or someone else's?
<someguy> someone else's
<someguy> humble_hoser: it's not my paper
<someguy> i mean the original was not my paper
<Sync> A follow up on: foobar
<someguy> is that common?
<Sync> there are some papers like that
<someguy> ok cool