This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (format=pdflatex 2012.12.6)  1 JUL 2013 11:28
entering extended mode
 %&-line parsing enabled.
**\input review.tex
(./review.tex (/usr/share/texmf-texlive/tex/latex/base/article.cls
Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
(/usr/share/texmf-texlive/tex/latex/base/size10.clo
File: size10.clo 2007/10/19 v1.4h Standard LaTeX file (size option)
)
\c@part=\count79
\c@section=\count80
\c@subsection=\count81
\c@subsubsection=\count82
\c@paragraph=\count83
\c@subparagraph=\count84
\c@figure=\count85
\c@table=\count86
\abovecaptionskip=\skip41
\belowcaptionskip=\skip42
\bibindent=\dimen102
) (./review.aux)
\openout1 = `review.aux'.

LaTeX Font Info:    Checking defaults for OML/cmm/m/it on input line 4.
LaTeX Font Info:    ... okay on input line 4.
LaTeX Font Info:    Checking defaults for T1/cmr/m/n on input line 4.
LaTeX Font Info:    ... okay on input line 4.
LaTeX Font Info:    Checking defaults for OT1/cmr/m/n on input line 4.
LaTeX Font Info:    ... okay on input line 4.
LaTeX Font Info:    Checking defaults for OMS/cmsy/m/n on input line 4.
LaTeX Font Info:    ... okay on input line 4.
LaTeX Font Info:    Checking defaults for OMX/cmex/m/n on input line 4.
LaTeX Font Info:    ... okay on input line 4.
LaTeX Font Info:    Checking defaults for U/cmr/m/n on input line 4.
LaTeX Font Info:    ... okay on input line 4.
LaTeX Font Info:    External font `cmex10' loaded for size
(Font)              <12> on input line 5.
LaTeX Font Info:    External font `cmex10' loaded for size
(Font)              <8> on input line 5.
LaTeX Font Info:    External font `cmex10' loaded for size
(Font)              <6> on input line 5.


LaTeX Warning: No \author given.

[1

{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}]
Overfull \hbox (6.74693pt too wide) in paragraph at lines 88--88
[] \OT1/cmtt/m/n/10 below.  An *iso*line would normally be expected to delineat
e areas[] 
 []


Overfull \hbox (6.74693pt too wide) in paragraph at lines 88--88
[] \OT1/cmtt/m/n/10 of the *same* intensity, so it's not obvious why a std devn
 should[] 
 []


Overfull \hbox (1.49698pt too wide) in paragraph at lines 88--88
[]\OT1/cmtt/m/n/10 be associated with one.  This doesn't become clear until wel
l into[] 
 []


Overfull \hbox (1.49698pt too wide) in paragraph at lines 88--88
[]\OT1/cmtt/m/n/10 section 6!! The authors need to explain (even if only briefl
y) how[] 
 []


Overfull \hbox (1.49698pt too wide) in paragraph at lines 88--88
[]\OT1/cmtt/m/n/10 associating a pixel with an isoline removes noise *early* in
 their[] 
 []


Overfull \hbox (1.49698pt too wide) in paragraph at lines 88--88
[]\OT1/cmtt/m/n/10 paper.  I would suggest moving figure 4(a,b,c) to the introd
uction[] 
 []


Overfull \hbox (1.49698pt too wide) in paragraph at lines 88--88
[]\OT1/cmtt/m/n/10 and adding the set of isolines that their process adds to th
e that[] 
 []


Overfull \hbox (6.74693pt too wide) in paragraph at lines 88--88
[]\OT1/cmtt/m/n/10 noisy window. Since it's only an 11x11 window, there should 
be only[] 
 []


Overfull \hbox (1.49698pt too wide) in paragraph at lines 88--88
[]\OT1/cmtt/m/n/10 the edge region, then something like the isoline through eve
ry 2nd[] 
 []

[2]
Overfull \hbox (11.99689pt too wide) in paragraph at lines 108--108
[]\OT1/cmtt/m/n/10 There is a key inconsistency in presentation .. there is a s
tatement[] 
 []


Overfull \hbox (1.49698pt too wide) in paragraph at lines 108--108
[]\OT1/cmtt/m/n/10 that 'most common' images are continuous and continuous few 
edges.[] 
 []


Overfull \hbox (27.74675pt too wide) in paragraph at lines 108--108
[]\OT1/cmtt/m/n/10 Such images would contain little information and be of littl
e interest.[] 
 []


Overfull \hbox (11.99689pt too wide) in paragraph at lines 108--108
[]\OT1/cmtt/m/n/10 However, tests have been conducted on 'real' images with no 
shortage[] 
 []


Overfull \hbox (6.74693pt too wide) in paragraph at lines 108--108
[]\OT1/cmtt/m/n/10 of edges - see figure 7b. If the continuity and few edges co
ndition[] 
 []


Overfull \hbox (6.74693pt too wide) in paragraph at lines 108--108
[]\OT1/cmtt/m/n/10 actually important (as results suggest), then these referenc
es need[] 
 []


Overfull \hbox (17.24684pt too wide) in paragraph at lines 115--115
[]\OT1/cmtt/m/n/10 Circular poly-isolines are apparently excluded which would s
eem to be[] 
 []


Overfull \hbox (27.74675pt too wide) in paragraph at lines 125--125
[]\OT1/cmtt/m/n/10 In general, the paper could be a lot better written.  The au
thors might[] 
 []


Overfull \hbox (1.49698pt too wide) in paragraph at lines 125--125
[]\OT1/cmtt/m/n/10 remove the 'noise' (in the sense of unnecessary words and ph
rases)[] 
 []


Overfull \hbox (11.99689pt too wide) in paragraph at lines 134--134
[]\OT1/cmtt/m/n/10 Similarly, figure 9 contains excess noise in the form of mea
ningless[] 
 []


Overfull \hbox (1.49698pt too wide) in paragraph at lines 134--134
[]\OT1/cmtt/m/n/10 digits in numbers presented.  By convention,   if you write 
19.49,[] 
 []

Missing character: There is no  in font cmtt10!
Missing character: There is no ± in font cmtt10!
LaTeX Font Info:    External font `cmex10' loaded for size
(Font)              <7> on input line 136.
LaTeX Font Info:    External font `cmex10' loaded for size
(Font)              <5> on input line 136.

Overfull \hbox (9.13957pt too wide) in paragraph at lines 135--139
\OT1/cmr/m/n/10 That is not ex-act: Let us con-sider a noisy $512 \OMS/cmsy/m/n
/10 ^^B \OT1/cmr/m/n/10 512$ pixel im-age of PSNR=19.50 dB.
 []

[3]
Overfull \hbox (6.74693pt too wide) in paragraph at lines 150--150
[]\OT1/cmtt/m/n/10 This table would be further improved by reporting the *impro
vement*[] 
 []


Overfull \hbox (6.74693pt too wide) in paragraph at lines 215--215
[]\OT1/cmtt/m/n/10 If they just 'propose to address' something, then this paper
 should[] 
 []


Overfull \hbox (1.49698pt too wide) in paragraph at lines 215--215
[]\OT1/cmtt/m/n/10 reference list - just use the author(s)' names as in the sug
gested[] 
 []


Overfull \hbox (1.49698pt too wide) in paragraph at lines 215--215
[]\OT1/cmtt/m/n/10 more precise wording is needed: I don't think anyone is inte
rested[] 
 []


Overfull \hbox (1.49698pt too wide) in paragraph at lines 215--215
[]\OT1/cmtt/m/n/10 The final sentence is almost inviting a reader to skip readi
ng the[] 
 []

[4] [5]
Overfull \hbox (6.74693pt too wide) in paragraph at lines 264--264
[]\OT1/cmtt/m/n/10 Giving the actual rates (in terms, say, of frames per second
) would[] 
 []


Overfull \hbox (1.49698pt too wide) in paragraph at lines 264--264
[] \OT1/cmtt/m/n/10 be even better in putting the author's current work into co
ntext![] 
 []


Overfull \hbox (17.24684pt too wide) in paragraph at lines 276--276
[]\OT1/cmtt/m/n/10 'apparently sub-optimal' implies that they might really be o
ptimal ..[] 
 []


Overfull \hbox (1.49698pt too wide) in paragraph at lines 276--276
[]\OT1/cmtt/m/n/10 it would seem that you're referring to the usual trade-off b
etween[] 
 []


Overfull \hbox (22.4968pt too wide) in paragraph at lines 276--276
[]\OT1/cmtt/m/n/10 lower quality algortithms that run faster .. so say that .. 
in 5 words[] 
 []

[6]
Overfull \hbox (43.49661pt too wide) in paragraph at lines 311--311
[]\OT1/cmtt/m/n/10 .. have been published.  Where?? At least some sample refere
nces required.[] 
 []


Overfull \hbox (6.74693pt too wide) in paragraph at lines 339--339
[]\OT1/cmtt/m/n/10 Nvidia themselves are rather vague about this, but that's no
 excuse[] 
 []


Overfull \hbox (1.49698pt too wide) in paragraph at lines 339--339
[]\OT1/cmtt/m/n/10 vagueness into (hopefully) carefully written and objective p
apers.[] 
 []

[7]
Overfull \hbox (1.49698pt too wide) in paragraph at lines 339--339
[]\OT1/cmtt/m/n/10 perspective with the clock rate.  I shouldn't have to look t
his up[] 
 []


Overfull \hbox (27.74675pt too wide) in paragraph at lines 374--374
[]\OT1/cmtt/m/n/10 The 'A' of CUDA is 'architecture' .. adding 'model' is not n
ecessary ..[] 
 []


Overfull \hbox (11.99689pt too wide) in paragraph at lines 374--374
[]\OT1/cmtt/m/n/10 lie in the same n mod 2^7 address block .. not an arbitrary 
2^7 byte[] 
 []

[8]
Overfull \hbox (27.74675pt too wide) in paragraph at lines 412--412
[]\OT1/cmtt/m/n/10 Small point, but this is a journal paper .. so you should ge
t it right![] 
 []


Overfull \hbox (6.74693pt too wide) in paragraph at lines 427--427
[]\OT1/cmtt/m/n/10 'As introduced above' .. where ?? In the previous para, you'
ve just[] 
 []


Overfull \hbox (11.99689pt too wide) in paragraph at lines 427--427
[]\OT1/cmtt/m/n/10 If you want to persist with this, then you should give some 
examples[] 
 []


Overfull \hbox (1.49698pt too wide) in paragraph at lines 427--427
[]\OT1/cmtt/m/n/10 There are many images used for testing image processing algo
rithms[] 
 []

[9]
Overfull \hbox (22.4968pt too wide) in paragraph at lines 487--487
[]\OT1/cmtt/m/n/10 You're defining a notation here .. don't use words implying 
vagueness![] 
 []


Overfull \hbox (6.74693pt too wide) in paragraph at lines 487--487
[]\OT1/cmtt/m/n/10 You mean that the two segments S^n and S^p must have the sam
e mean?[] 
 []

[10]
Overfull \hbox (1.49698pt too wide) in paragraph at lines 504--504
[]\OT1/cmtt/m/n/10 which appears to have the *same* intensity along its whole l
ength.[] 
 []

[11]
Overfull \hbox (17.24684pt too wide) in paragraph at lines 556--556
[]\OT1/cmtt/m/n/10 how do you have C_x(Z(S^n)) .. having been obtained in the *
previous*[] 
 []

[12]
Overfull \hbox (53.99652pt too wide) in paragraph at lines 620--620
[]\OT1/cmtt/m/n/10 (you use deviation in another sense also .. so you need to b
e specific here)[] 
 []


Overfull \hbox (1.49698pt too wide) in paragraph at lines 636--636
[]\OT1/cmtt/m/n/10 The notation [0;D] for the set [0..D] is also unusual and pr
obably[] 
 []

[13]
Overfull \hbox (6.74693pt too wide) in paragraph at lines 665--665
[]\OT1/cmtt/m/n/10 only for P_l, not for the images themselves, which are much 
larger.[] 
 []


Overfull \hbox (1.49698pt too wide) in paragraph at lines 665--665
[]\OT1/cmtt/m/n/10 effort.  In this case, it would appear that there are a suff
icient[] 
 []


Overfull \hbox (6.74693pt too wide) in paragraph at lines 677--677
[]\OT1/cmtt/m/n/10 Results should ideally separate out time to transfer images 
between[] 
 []


Overfull \hbox (6.74693pt too wide) in paragraph at lines 677--677
[]\OT1/cmtt/m/n/10 and GPU computation times, since for applications (most pres
umably)[] 
 []


Overfull \hbox (6.74693pt too wide) in paragraph at lines 686--686
[]\OT1/cmtt/m/n/10 There is a disappointing lack of data for values of l other 
than 5.[] 
 []

[14] [15] (./review.aux) ) 
Here is how much of TeX's memory you used:
 232 strings out of 495028
 2464 string characters out of 1181229
 52031 words of memory out of 3000000
 3492 multiletter control sequences out of 15000+50000
 7794 words of font info for 28 fonts, out of 3000000 for 9000
 28 hyphenation exceptions out of 8191
 23i,6n,17p,305b,245s stack positions out of 5000i,500n,10000p,200000b,50000s
</usr/share/texmf-texlive/fonts/type1/public/amsfonts
/cm/cmbx12.pfb></usr/share/texmf-texlive/fonts/type1/public/amsfonts/cm/cmex10.
pfb></usr/share/texmf-texlive/fonts/type1/public/amsfonts/cm/cmmi10.pfb></usr/s
hare/texmf-texlive/fonts/type1/public/amsfonts/cm/cmmi7.pfb></usr/share/texmf-t
exlive/fonts/type1/public/amsfonts/cm/cmr10.pfb></usr/share/texmf-texlive/fonts
/type1/public/amsfonts/cm/cmr12.pfb></usr/share/texmf-texlive/fonts/type1/publi
c/amsfonts/cm/cmr17.pfb></usr/share/texmf-texlive/fonts/type1/public/amsfonts/c
m/cmr7.pfb></usr/share/texmf-texlive/fonts/type1/public/amsfonts/cm/cmsy10.pfb>
</usr/share/texmf-texlive/fonts/type1/public/amsfonts/cm/cmti10.pfb></usr/share
/texmf-texlive/fonts/type1/public/amsfonts/cm/cmtt10.pfb>
Output written on review.pdf (15 pages, 157774 bytes).
PDF statistics:
 95 PDF objects out of 1000 (max. 8388607)
 0 named destinations out of 1000 (max. 500000)
 1 words of extra memory for PDF output out of 10000 (max. 10000000)