Avoiding excessive space under equation

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
3
down vote

favorite












I'm wondering how can I avoid excessive white space under equation.
This happens only a time in the entire document; in the other pages there are not this problem (I wrote the equation and the text in the same way everywhere).



enter image description here



poi saranno applicate quando si collegherà solo il sensore:
beginequation*
H(j omega) = Z_Known(j omega) fracV^ZK_ADC1(j omega)V_IN(j omega)
endequation*
dove $V^ZK_ADC1$ è la tensione letta dall'ADC quando tra il WE1 ed il CE è collegata solo la $Z_Known$ (footnoteNotare che, quando $V^ZC_ADC1(j omega) = V^ZK_ADC1(j omega)$, si ha: beginequation*
Z_S(j omega) = Z_Known(j omega) fracV^ZK_ADC1(j omega)V_IN(j omega) fracV_IN(j omega)V^ZS_ADC1(j omega) = Z_Known(j omega)
endequation*).
L'impedenza $Z_Known$ ha la seguente espressione:



EDIT: I'm using classicthesis template. The documentclass is:



documentclass[oneside,titlepage,numbers=noenddot,%1headlines,
headinclude,footinclude,cleardoublepage=empty,abstract=on,
BCOR=5mm,paper=a4,fontsize=11pt
]scrreprt


https://ctan.org/tex-archive/macros/latex/contrib/classicthesis?lang=en



Thank you so much in advance.










share|improve this question























  • Please tell us which document class you employ, which font-related packages you employ, and whether flushbottom or raggedbottom is in effect. Ideally, you would edit your query to provide not just a code fragment but a compilable example that generates the problem behavior you wish to fix.
    – Mico
    Sep 16 at 8:26










  • Hello @Mico see the edit please.
    – Gennaro Arguzzi
    Sep 16 at 8:34






  • 2




    you have given no indication why the space is there, so hard to tell you what to change. Most likely it is something on the next page preventing a good page break. Your example should be a complete small document that shows the issue so that people can debug
    – David Carlisle
    Sep 16 at 8:45






  • 1




    Thanks for providing information about the document class. Do you employ a package such as classicthesis?
    – Mico
    Sep 16 at 8:46






  • 3




    The issue is simple to describe: footnote 19 is quite long and wouldn't fit in page 23; so it's moved to page 24 together with one line above and below because you end up with a three line (partial) paragraph. Unless you do some editing, the problem will remain. To begin with, I don't think that material with a displayed equation qualifies as “footnote”.
    – egreg
    Sep 16 at 9:05















up vote
3
down vote

favorite












I'm wondering how can I avoid excessive white space under equation.
This happens only a time in the entire document; in the other pages there are not this problem (I wrote the equation and the text in the same way everywhere).



enter image description here



poi saranno applicate quando si collegherà solo il sensore:
beginequation*
H(j omega) = Z_Known(j omega) fracV^ZK_ADC1(j omega)V_IN(j omega)
endequation*
dove $V^ZK_ADC1$ è la tensione letta dall'ADC quando tra il WE1 ed il CE è collegata solo la $Z_Known$ (footnoteNotare che, quando $V^ZC_ADC1(j omega) = V^ZK_ADC1(j omega)$, si ha: beginequation*
Z_S(j omega) = Z_Known(j omega) fracV^ZK_ADC1(j omega)V_IN(j omega) fracV_IN(j omega)V^ZS_ADC1(j omega) = Z_Known(j omega)
endequation*).
L'impedenza $Z_Known$ ha la seguente espressione:



EDIT: I'm using classicthesis template. The documentclass is:



documentclass[oneside,titlepage,numbers=noenddot,%1headlines,
headinclude,footinclude,cleardoublepage=empty,abstract=on,
BCOR=5mm,paper=a4,fontsize=11pt
]scrreprt


https://ctan.org/tex-archive/macros/latex/contrib/classicthesis?lang=en



Thank you so much in advance.










share|improve this question























  • Please tell us which document class you employ, which font-related packages you employ, and whether flushbottom or raggedbottom is in effect. Ideally, you would edit your query to provide not just a code fragment but a compilable example that generates the problem behavior you wish to fix.
    – Mico
    Sep 16 at 8:26










  • Hello @Mico see the edit please.
    – Gennaro Arguzzi
    Sep 16 at 8:34






  • 2




    you have given no indication why the space is there, so hard to tell you what to change. Most likely it is something on the next page preventing a good page break. Your example should be a complete small document that shows the issue so that people can debug
    – David Carlisle
    Sep 16 at 8:45






  • 1




    Thanks for providing information about the document class. Do you employ a package such as classicthesis?
    – Mico
    Sep 16 at 8:46






  • 3




    The issue is simple to describe: footnote 19 is quite long and wouldn't fit in page 23; so it's moved to page 24 together with one line above and below because you end up with a three line (partial) paragraph. Unless you do some editing, the problem will remain. To begin with, I don't think that material with a displayed equation qualifies as “footnote”.
    – egreg
    Sep 16 at 9:05













up vote
3
down vote

favorite









up vote
3
down vote

favorite











I'm wondering how can I avoid excessive white space under equation.
This happens only a time in the entire document; in the other pages there are not this problem (I wrote the equation and the text in the same way everywhere).



enter image description here



poi saranno applicate quando si collegherà solo il sensore:
beginequation*
H(j omega) = Z_Known(j omega) fracV^ZK_ADC1(j omega)V_IN(j omega)
endequation*
dove $V^ZK_ADC1$ è la tensione letta dall'ADC quando tra il WE1 ed il CE è collegata solo la $Z_Known$ (footnoteNotare che, quando $V^ZC_ADC1(j omega) = V^ZK_ADC1(j omega)$, si ha: beginequation*
Z_S(j omega) = Z_Known(j omega) fracV^ZK_ADC1(j omega)V_IN(j omega) fracV_IN(j omega)V^ZS_ADC1(j omega) = Z_Known(j omega)
endequation*).
L'impedenza $Z_Known$ ha la seguente espressione:



EDIT: I'm using classicthesis template. The documentclass is:



documentclass[oneside,titlepage,numbers=noenddot,%1headlines,
headinclude,footinclude,cleardoublepage=empty,abstract=on,
BCOR=5mm,paper=a4,fontsize=11pt
]scrreprt


https://ctan.org/tex-archive/macros/latex/contrib/classicthesis?lang=en



Thank you so much in advance.










share|improve this question















I'm wondering how can I avoid excessive white space under equation.
This happens only a time in the entire document; in the other pages there are not this problem (I wrote the equation and the text in the same way everywhere).



enter image description here



poi saranno applicate quando si collegherà solo il sensore:
beginequation*
H(j omega) = Z_Known(j omega) fracV^ZK_ADC1(j omega)V_IN(j omega)
endequation*
dove $V^ZK_ADC1$ è la tensione letta dall'ADC quando tra il WE1 ed il CE è collegata solo la $Z_Known$ (footnoteNotare che, quando $V^ZC_ADC1(j omega) = V^ZK_ADC1(j omega)$, si ha: beginequation*
Z_S(j omega) = Z_Known(j omega) fracV^ZK_ADC1(j omega)V_IN(j omega) fracV_IN(j omega)V^ZS_ADC1(j omega) = Z_Known(j omega)
endequation*).
L'impedenza $Z_Known$ ha la seguente espressione:



EDIT: I'm using classicthesis template. The documentclass is:



documentclass[oneside,titlepage,numbers=noenddot,%1headlines,
headinclude,footinclude,cleardoublepage=empty,abstract=on,
BCOR=5mm,paper=a4,fontsize=11pt
]scrreprt


https://ctan.org/tex-archive/macros/latex/contrib/classicthesis?lang=en



Thank you so much in advance.







spacing templates classicthesis white-space






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Sep 16 at 8:34

























asked Sep 16 at 8:15









Gennaro Arguzzi

467310




467310











  • Please tell us which document class you employ, which font-related packages you employ, and whether flushbottom or raggedbottom is in effect. Ideally, you would edit your query to provide not just a code fragment but a compilable example that generates the problem behavior you wish to fix.
    – Mico
    Sep 16 at 8:26










  • Hello @Mico see the edit please.
    – Gennaro Arguzzi
    Sep 16 at 8:34






  • 2




    you have given no indication why the space is there, so hard to tell you what to change. Most likely it is something on the next page preventing a good page break. Your example should be a complete small document that shows the issue so that people can debug
    – David Carlisle
    Sep 16 at 8:45






  • 1




    Thanks for providing information about the document class. Do you employ a package such as classicthesis?
    – Mico
    Sep 16 at 8:46






  • 3




    The issue is simple to describe: footnote 19 is quite long and wouldn't fit in page 23; so it's moved to page 24 together with one line above and below because you end up with a three line (partial) paragraph. Unless you do some editing, the problem will remain. To begin with, I don't think that material with a displayed equation qualifies as “footnote”.
    – egreg
    Sep 16 at 9:05

















  • Please tell us which document class you employ, which font-related packages you employ, and whether flushbottom or raggedbottom is in effect. Ideally, you would edit your query to provide not just a code fragment but a compilable example that generates the problem behavior you wish to fix.
    – Mico
    Sep 16 at 8:26










  • Hello @Mico see the edit please.
    – Gennaro Arguzzi
    Sep 16 at 8:34






  • 2




    you have given no indication why the space is there, so hard to tell you what to change. Most likely it is something on the next page preventing a good page break. Your example should be a complete small document that shows the issue so that people can debug
    – David Carlisle
    Sep 16 at 8:45






  • 1




    Thanks for providing information about the document class. Do you employ a package such as classicthesis?
    – Mico
    Sep 16 at 8:46






  • 3




    The issue is simple to describe: footnote 19 is quite long and wouldn't fit in page 23; so it's moved to page 24 together with one line above and below because you end up with a three line (partial) paragraph. Unless you do some editing, the problem will remain. To begin with, I don't think that material with a displayed equation qualifies as “footnote”.
    – egreg
    Sep 16 at 9:05
















Please tell us which document class you employ, which font-related packages you employ, and whether flushbottom or raggedbottom is in effect. Ideally, you would edit your query to provide not just a code fragment but a compilable example that generates the problem behavior you wish to fix.
– Mico
Sep 16 at 8:26




Please tell us which document class you employ, which font-related packages you employ, and whether flushbottom or raggedbottom is in effect. Ideally, you would edit your query to provide not just a code fragment but a compilable example that generates the problem behavior you wish to fix.
– Mico
Sep 16 at 8:26












Hello @Mico see the edit please.
– Gennaro Arguzzi
Sep 16 at 8:34




Hello @Mico see the edit please.
– Gennaro Arguzzi
Sep 16 at 8:34




2




2




you have given no indication why the space is there, so hard to tell you what to change. Most likely it is something on the next page preventing a good page break. Your example should be a complete small document that shows the issue so that people can debug
– David Carlisle
Sep 16 at 8:45




you have given no indication why the space is there, so hard to tell you what to change. Most likely it is something on the next page preventing a good page break. Your example should be a complete small document that shows the issue so that people can debug
– David Carlisle
Sep 16 at 8:45




1




1




Thanks for providing information about the document class. Do you employ a package such as classicthesis?
– Mico
Sep 16 at 8:46




Thanks for providing information about the document class. Do you employ a package such as classicthesis?
– Mico
Sep 16 at 8:46




3




3




The issue is simple to describe: footnote 19 is quite long and wouldn't fit in page 23; so it's moved to page 24 together with one line above and below because you end up with a three line (partial) paragraph. Unless you do some editing, the problem will remain. To begin with, I don't think that material with a displayed equation qualifies as “footnote”.
– egreg
Sep 16 at 9:05





The issue is simple to describe: footnote 19 is quite long and wouldn't fit in page 23; so it's moved to page 24 together with one line above and below because you end up with a three line (partial) paragraph. Unless you do some editing, the problem will remain. To begin with, I don't think that material with a displayed equation qualifies as “footnote”.
– egreg
Sep 16 at 9:05











1 Answer
1






active

oldest

votes

















up vote
6
down vote



accepted










As @egreg has already pointed out in a comment, the big gap at the bottom of page 23 is caused by the fact that the material that follows the first displayed equation contains a lengthy footnote. This material -- including footnote 19 -- just won't fit at the bottom of page 23 and hence gets pushed to the top of page 24.



The following screenshot shows how this can happen (the code is given at the end of this answer):



enter image description here



There are several possible remedies:



  • Make footnote 19 take up less space. E.g., is it essential to include a displayed equation in that footnote? Alternatively, if the footnote material truly is sufficiently important to warrant a displayed equation, it may be sufficiently important to be include in the main text, rather than being relegated to a footnote.


  • Shorten the material earlier on page 23 (or page 22, or ...).


  • Insert an instruction such as enlargethispage0.75baselineskip (or whatever vertical skip may be necessary...) just before the paragraph that contains the displayed equation.


Any visual fine-tuning should be performed only at the very end of the editing process, i.e., once the paper is truly done from a content perspective.



For the sake of completeness, here's the code that gave rise to the screenshot shown above; note that I would use upright Roman lettering for acronyms and full words, such as 'Known' and 'ADC', that occur in a math context.



documentclass[oneside,titlepage,numbers=noenddot,
headinclude,footinclude,cleardoublepage=empty,abstract=on,
BCOR=5mm,paper=a4,fontsize=11pt]scrreprt
usepackageamsmath
usepackage[dottedtoc]classicthesis
usepackagelipsum
newcommandvn[1]mathrm#1
newcommandmyfootnote[1]%
textsuperscript(%
footnote#1%
textsuperscript)
begindocument
setcounterpage23
setcounterfootnote17
setcounterchapter2
setcountersection3
sectionConfronto tra il biosensore ed un bipotenziostato da banco

lipsum[1-2] % filler text
myfootnoteCalibrare significa sollecitare con ingressi noti e misurare
le correspondenti uscite. In questo caso gli ingressi noti dots
lipsum[2] % more filler text

% Check out what happens if the following line is uncommented.
%enlargethispage0.75baselineskip
bigskip
noindent
poi saranno applicate quando si collegherà solo il sensore:
beginequation*
H(jomega) = Z_vnKnown(jomega) fracV^vnZK_vnADC1(jomega)V_vnIN(jomega)
endequation*
dove $V^vnZK_vnADC1$ è la tensione letta dall'ADC quando tra il WE1 ed il~CE è collegata solo la $Z_vnKnown$.%
myfootnoteNotare che, quando $V^vnZC_vnADC1(jomega) = V^vnZK_vnADC1(jomega)$, si ha:
[
Z_S(jomega) = Z_vnKnown(jomega)
fracV^vnZK_vnADC1(jomega)V_vnIN(jomega)
fracV_vnIN(jomega)V^vnZS_vnADC1(jomega)
= Z_vnKnown(jomega),.
]
L'impedenza $Z_vnKnown$ ha la seguente espressione: dots

bigskip
lipsum[4-7] % still more filler texxt
enddocument





share|improve this answer


















  • 1




    i took a liberty and correct definition of newcommandvn[2]mathrm#1 to newcommandvn[1]mathrm#1 (after that your mwe works). compiling your mwe, i obtain quite different result as shown in your answer. i use recent miktex.
    – Zarko
    Sep 16 at 9:31











  • problem seems to be with myfootnote. if lipsum[2] is immediately after it, this paragraph not appear, but is printout only [2], i .e. option which paragraph from lipsum should be used. inserting blank lines before repair this malfunction.
    – Zarko
    Sep 16 at 9:40










  • @Zarko - Many thanks for applying the fix to the definition of vn. Something very weird seems to have happened during the copy-and-paste operation: In the tex file on my system, both vn and myfootnote are defined to take a single argument. However, upon pasting (and indenting), the two instances of [1] ended up as [2]. I have no idea how this came about. I suspect it's a site bug. Fortunately, both commands now show that they take a single argument.
    – Mico
    Sep 16 at 10:08







  • 1




    @Mico Unrelated, but I've been meaning to compliment you on your TUG talk. It was very interesting and you did a perfect job of explaining the linguistics! (I put this comment elsewhere, but I thought it would be better on one of your answers instead of a new user's question.)
    – Alan Munn
    Sep 16 at 18:36






  • 1




    @AlanMunn - Wow, thanks so much for this compliment!! I deeply appreciate it. You can probably tell that I'm not a linguist by training (in fact, I'm an economist...), but I did get a thorough introduction to morphemes and morphology from Felix Lehmann, who is a budding linguist, at a crucial early stage of the development of the selnolig package. Felix and his colleague Steffen Hildebrand provided a large number of crucial inputs and validations to the package -- including teaching me the basics of morphology! I very much appreciated getting this type of education. :-)
    – Mico
    Sep 16 at 18:45










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "85"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f451090%2favoiding-excessive-space-under-equation%23new-answer', 'question_page');

);

Post as a guest






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
6
down vote



accepted










As @egreg has already pointed out in a comment, the big gap at the bottom of page 23 is caused by the fact that the material that follows the first displayed equation contains a lengthy footnote. This material -- including footnote 19 -- just won't fit at the bottom of page 23 and hence gets pushed to the top of page 24.



The following screenshot shows how this can happen (the code is given at the end of this answer):



enter image description here



There are several possible remedies:



  • Make footnote 19 take up less space. E.g., is it essential to include a displayed equation in that footnote? Alternatively, if the footnote material truly is sufficiently important to warrant a displayed equation, it may be sufficiently important to be include in the main text, rather than being relegated to a footnote.


  • Shorten the material earlier on page 23 (or page 22, or ...).


  • Insert an instruction such as enlargethispage0.75baselineskip (or whatever vertical skip may be necessary...) just before the paragraph that contains the displayed equation.


Any visual fine-tuning should be performed only at the very end of the editing process, i.e., once the paper is truly done from a content perspective.



For the sake of completeness, here's the code that gave rise to the screenshot shown above; note that I would use upright Roman lettering for acronyms and full words, such as 'Known' and 'ADC', that occur in a math context.



documentclass[oneside,titlepage,numbers=noenddot,
headinclude,footinclude,cleardoublepage=empty,abstract=on,
BCOR=5mm,paper=a4,fontsize=11pt]scrreprt
usepackageamsmath
usepackage[dottedtoc]classicthesis
usepackagelipsum
newcommandvn[1]mathrm#1
newcommandmyfootnote[1]%
textsuperscript(%
footnote#1%
textsuperscript)
begindocument
setcounterpage23
setcounterfootnote17
setcounterchapter2
setcountersection3
sectionConfronto tra il biosensore ed un bipotenziostato da banco

lipsum[1-2] % filler text
myfootnoteCalibrare significa sollecitare con ingressi noti e misurare
le correspondenti uscite. In questo caso gli ingressi noti dots
lipsum[2] % more filler text

% Check out what happens if the following line is uncommented.
%enlargethispage0.75baselineskip
bigskip
noindent
poi saranno applicate quando si collegherà solo il sensore:
beginequation*
H(jomega) = Z_vnKnown(jomega) fracV^vnZK_vnADC1(jomega)V_vnIN(jomega)
endequation*
dove $V^vnZK_vnADC1$ è la tensione letta dall'ADC quando tra il WE1 ed il~CE è collegata solo la $Z_vnKnown$.%
myfootnoteNotare che, quando $V^vnZC_vnADC1(jomega) = V^vnZK_vnADC1(jomega)$, si ha:
[
Z_S(jomega) = Z_vnKnown(jomega)
fracV^vnZK_vnADC1(jomega)V_vnIN(jomega)
fracV_vnIN(jomega)V^vnZS_vnADC1(jomega)
= Z_vnKnown(jomega),.
]
L'impedenza $Z_vnKnown$ ha la seguente espressione: dots

bigskip
lipsum[4-7] % still more filler texxt
enddocument





share|improve this answer


















  • 1




    i took a liberty and correct definition of newcommandvn[2]mathrm#1 to newcommandvn[1]mathrm#1 (after that your mwe works). compiling your mwe, i obtain quite different result as shown in your answer. i use recent miktex.
    – Zarko
    Sep 16 at 9:31











  • problem seems to be with myfootnote. if lipsum[2] is immediately after it, this paragraph not appear, but is printout only [2], i .e. option which paragraph from lipsum should be used. inserting blank lines before repair this malfunction.
    – Zarko
    Sep 16 at 9:40










  • @Zarko - Many thanks for applying the fix to the definition of vn. Something very weird seems to have happened during the copy-and-paste operation: In the tex file on my system, both vn and myfootnote are defined to take a single argument. However, upon pasting (and indenting), the two instances of [1] ended up as [2]. I have no idea how this came about. I suspect it's a site bug. Fortunately, both commands now show that they take a single argument.
    – Mico
    Sep 16 at 10:08







  • 1




    @Mico Unrelated, but I've been meaning to compliment you on your TUG talk. It was very interesting and you did a perfect job of explaining the linguistics! (I put this comment elsewhere, but I thought it would be better on one of your answers instead of a new user's question.)
    – Alan Munn
    Sep 16 at 18:36






  • 1




    @AlanMunn - Wow, thanks so much for this compliment!! I deeply appreciate it. You can probably tell that I'm not a linguist by training (in fact, I'm an economist...), but I did get a thorough introduction to morphemes and morphology from Felix Lehmann, who is a budding linguist, at a crucial early stage of the development of the selnolig package. Felix and his colleague Steffen Hildebrand provided a large number of crucial inputs and validations to the package -- including teaching me the basics of morphology! I very much appreciated getting this type of education. :-)
    – Mico
    Sep 16 at 18:45














up vote
6
down vote



accepted










As @egreg has already pointed out in a comment, the big gap at the bottom of page 23 is caused by the fact that the material that follows the first displayed equation contains a lengthy footnote. This material -- including footnote 19 -- just won't fit at the bottom of page 23 and hence gets pushed to the top of page 24.



The following screenshot shows how this can happen (the code is given at the end of this answer):



enter image description here



There are several possible remedies:



  • Make footnote 19 take up less space. E.g., is it essential to include a displayed equation in that footnote? Alternatively, if the footnote material truly is sufficiently important to warrant a displayed equation, it may be sufficiently important to be include in the main text, rather than being relegated to a footnote.


  • Shorten the material earlier on page 23 (or page 22, or ...).


  • Insert an instruction such as enlargethispage0.75baselineskip (or whatever vertical skip may be necessary...) just before the paragraph that contains the displayed equation.


Any visual fine-tuning should be performed only at the very end of the editing process, i.e., once the paper is truly done from a content perspective.



For the sake of completeness, here's the code that gave rise to the screenshot shown above; note that I would use upright Roman lettering for acronyms and full words, such as 'Known' and 'ADC', that occur in a math context.



documentclass[oneside,titlepage,numbers=noenddot,
headinclude,footinclude,cleardoublepage=empty,abstract=on,
BCOR=5mm,paper=a4,fontsize=11pt]scrreprt
usepackageamsmath
usepackage[dottedtoc]classicthesis
usepackagelipsum
newcommandvn[1]mathrm#1
newcommandmyfootnote[1]%
textsuperscript(%
footnote#1%
textsuperscript)
begindocument
setcounterpage23
setcounterfootnote17
setcounterchapter2
setcountersection3
sectionConfronto tra il biosensore ed un bipotenziostato da banco

lipsum[1-2] % filler text
myfootnoteCalibrare significa sollecitare con ingressi noti e misurare
le correspondenti uscite. In questo caso gli ingressi noti dots
lipsum[2] % more filler text

% Check out what happens if the following line is uncommented.
%enlargethispage0.75baselineskip
bigskip
noindent
poi saranno applicate quando si collegherà solo il sensore:
beginequation*
H(jomega) = Z_vnKnown(jomega) fracV^vnZK_vnADC1(jomega)V_vnIN(jomega)
endequation*
dove $V^vnZK_vnADC1$ è la tensione letta dall'ADC quando tra il WE1 ed il~CE è collegata solo la $Z_vnKnown$.%
myfootnoteNotare che, quando $V^vnZC_vnADC1(jomega) = V^vnZK_vnADC1(jomega)$, si ha:
[
Z_S(jomega) = Z_vnKnown(jomega)
fracV^vnZK_vnADC1(jomega)V_vnIN(jomega)
fracV_vnIN(jomega)V^vnZS_vnADC1(jomega)
= Z_vnKnown(jomega),.
]
L'impedenza $Z_vnKnown$ ha la seguente espressione: dots

bigskip
lipsum[4-7] % still more filler texxt
enddocument





share|improve this answer


















  • 1




    i took a liberty and correct definition of newcommandvn[2]mathrm#1 to newcommandvn[1]mathrm#1 (after that your mwe works). compiling your mwe, i obtain quite different result as shown in your answer. i use recent miktex.
    – Zarko
    Sep 16 at 9:31











  • problem seems to be with myfootnote. if lipsum[2] is immediately after it, this paragraph not appear, but is printout only [2], i .e. option which paragraph from lipsum should be used. inserting blank lines before repair this malfunction.
    – Zarko
    Sep 16 at 9:40










  • @Zarko - Many thanks for applying the fix to the definition of vn. Something very weird seems to have happened during the copy-and-paste operation: In the tex file on my system, both vn and myfootnote are defined to take a single argument. However, upon pasting (and indenting), the two instances of [1] ended up as [2]. I have no idea how this came about. I suspect it's a site bug. Fortunately, both commands now show that they take a single argument.
    – Mico
    Sep 16 at 10:08







  • 1




    @Mico Unrelated, but I've been meaning to compliment you on your TUG talk. It was very interesting and you did a perfect job of explaining the linguistics! (I put this comment elsewhere, but I thought it would be better on one of your answers instead of a new user's question.)
    – Alan Munn
    Sep 16 at 18:36






  • 1




    @AlanMunn - Wow, thanks so much for this compliment!! I deeply appreciate it. You can probably tell that I'm not a linguist by training (in fact, I'm an economist...), but I did get a thorough introduction to morphemes and morphology from Felix Lehmann, who is a budding linguist, at a crucial early stage of the development of the selnolig package. Felix and his colleague Steffen Hildebrand provided a large number of crucial inputs and validations to the package -- including teaching me the basics of morphology! I very much appreciated getting this type of education. :-)
    – Mico
    Sep 16 at 18:45












up vote
6
down vote



accepted







up vote
6
down vote



accepted






As @egreg has already pointed out in a comment, the big gap at the bottom of page 23 is caused by the fact that the material that follows the first displayed equation contains a lengthy footnote. This material -- including footnote 19 -- just won't fit at the bottom of page 23 and hence gets pushed to the top of page 24.



The following screenshot shows how this can happen (the code is given at the end of this answer):



enter image description here



There are several possible remedies:



  • Make footnote 19 take up less space. E.g., is it essential to include a displayed equation in that footnote? Alternatively, if the footnote material truly is sufficiently important to warrant a displayed equation, it may be sufficiently important to be include in the main text, rather than being relegated to a footnote.


  • Shorten the material earlier on page 23 (or page 22, or ...).


  • Insert an instruction such as enlargethispage0.75baselineskip (or whatever vertical skip may be necessary...) just before the paragraph that contains the displayed equation.


Any visual fine-tuning should be performed only at the very end of the editing process, i.e., once the paper is truly done from a content perspective.



For the sake of completeness, here's the code that gave rise to the screenshot shown above; note that I would use upright Roman lettering for acronyms and full words, such as 'Known' and 'ADC', that occur in a math context.



documentclass[oneside,titlepage,numbers=noenddot,
headinclude,footinclude,cleardoublepage=empty,abstract=on,
BCOR=5mm,paper=a4,fontsize=11pt]scrreprt
usepackageamsmath
usepackage[dottedtoc]classicthesis
usepackagelipsum
newcommandvn[1]mathrm#1
newcommandmyfootnote[1]%
textsuperscript(%
footnote#1%
textsuperscript)
begindocument
setcounterpage23
setcounterfootnote17
setcounterchapter2
setcountersection3
sectionConfronto tra il biosensore ed un bipotenziostato da banco

lipsum[1-2] % filler text
myfootnoteCalibrare significa sollecitare con ingressi noti e misurare
le correspondenti uscite. In questo caso gli ingressi noti dots
lipsum[2] % more filler text

% Check out what happens if the following line is uncommented.
%enlargethispage0.75baselineskip
bigskip
noindent
poi saranno applicate quando si collegherà solo il sensore:
beginequation*
H(jomega) = Z_vnKnown(jomega) fracV^vnZK_vnADC1(jomega)V_vnIN(jomega)
endequation*
dove $V^vnZK_vnADC1$ è la tensione letta dall'ADC quando tra il WE1 ed il~CE è collegata solo la $Z_vnKnown$.%
myfootnoteNotare che, quando $V^vnZC_vnADC1(jomega) = V^vnZK_vnADC1(jomega)$, si ha:
[
Z_S(jomega) = Z_vnKnown(jomega)
fracV^vnZK_vnADC1(jomega)V_vnIN(jomega)
fracV_vnIN(jomega)V^vnZS_vnADC1(jomega)
= Z_vnKnown(jomega),.
]
L'impedenza $Z_vnKnown$ ha la seguente espressione: dots

bigskip
lipsum[4-7] % still more filler texxt
enddocument





share|improve this answer














As @egreg has already pointed out in a comment, the big gap at the bottom of page 23 is caused by the fact that the material that follows the first displayed equation contains a lengthy footnote. This material -- including footnote 19 -- just won't fit at the bottom of page 23 and hence gets pushed to the top of page 24.



The following screenshot shows how this can happen (the code is given at the end of this answer):



enter image description here



There are several possible remedies:



  • Make footnote 19 take up less space. E.g., is it essential to include a displayed equation in that footnote? Alternatively, if the footnote material truly is sufficiently important to warrant a displayed equation, it may be sufficiently important to be include in the main text, rather than being relegated to a footnote.


  • Shorten the material earlier on page 23 (or page 22, or ...).


  • Insert an instruction such as enlargethispage0.75baselineskip (or whatever vertical skip may be necessary...) just before the paragraph that contains the displayed equation.


Any visual fine-tuning should be performed only at the very end of the editing process, i.e., once the paper is truly done from a content perspective.



For the sake of completeness, here's the code that gave rise to the screenshot shown above; note that I would use upright Roman lettering for acronyms and full words, such as 'Known' and 'ADC', that occur in a math context.



documentclass[oneside,titlepage,numbers=noenddot,
headinclude,footinclude,cleardoublepage=empty,abstract=on,
BCOR=5mm,paper=a4,fontsize=11pt]scrreprt
usepackageamsmath
usepackage[dottedtoc]classicthesis
usepackagelipsum
newcommandvn[1]mathrm#1
newcommandmyfootnote[1]%
textsuperscript(%
footnote#1%
textsuperscript)
begindocument
setcounterpage23
setcounterfootnote17
setcounterchapter2
setcountersection3
sectionConfronto tra il biosensore ed un bipotenziostato da banco

lipsum[1-2] % filler text
myfootnoteCalibrare significa sollecitare con ingressi noti e misurare
le correspondenti uscite. In questo caso gli ingressi noti dots
lipsum[2] % more filler text

% Check out what happens if the following line is uncommented.
%enlargethispage0.75baselineskip
bigskip
noindent
poi saranno applicate quando si collegherà solo il sensore:
beginequation*
H(jomega) = Z_vnKnown(jomega) fracV^vnZK_vnADC1(jomega)V_vnIN(jomega)
endequation*
dove $V^vnZK_vnADC1$ è la tensione letta dall'ADC quando tra il WE1 ed il~CE è collegata solo la $Z_vnKnown$.%
myfootnoteNotare che, quando $V^vnZC_vnADC1(jomega) = V^vnZK_vnADC1(jomega)$, si ha:
[
Z_S(jomega) = Z_vnKnown(jomega)
fracV^vnZK_vnADC1(jomega)V_vnIN(jomega)
fracV_vnIN(jomega)V^vnZS_vnADC1(jomega)
= Z_vnKnown(jomega),.
]
L'impedenza $Z_vnKnown$ ha la seguente espressione: dots

bigskip
lipsum[4-7] % still more filler texxt
enddocument






share|improve this answer














share|improve this answer



share|improve this answer








edited Sep 16 at 10:06

























answered Sep 16 at 9:20









Mico

265k30355734




265k30355734







  • 1




    i took a liberty and correct definition of newcommandvn[2]mathrm#1 to newcommandvn[1]mathrm#1 (after that your mwe works). compiling your mwe, i obtain quite different result as shown in your answer. i use recent miktex.
    – Zarko
    Sep 16 at 9:31











  • problem seems to be with myfootnote. if lipsum[2] is immediately after it, this paragraph not appear, but is printout only [2], i .e. option which paragraph from lipsum should be used. inserting blank lines before repair this malfunction.
    – Zarko
    Sep 16 at 9:40










  • @Zarko - Many thanks for applying the fix to the definition of vn. Something very weird seems to have happened during the copy-and-paste operation: In the tex file on my system, both vn and myfootnote are defined to take a single argument. However, upon pasting (and indenting), the two instances of [1] ended up as [2]. I have no idea how this came about. I suspect it's a site bug. Fortunately, both commands now show that they take a single argument.
    – Mico
    Sep 16 at 10:08







  • 1




    @Mico Unrelated, but I've been meaning to compliment you on your TUG talk. It was very interesting and you did a perfect job of explaining the linguistics! (I put this comment elsewhere, but I thought it would be better on one of your answers instead of a new user's question.)
    – Alan Munn
    Sep 16 at 18:36






  • 1




    @AlanMunn - Wow, thanks so much for this compliment!! I deeply appreciate it. You can probably tell that I'm not a linguist by training (in fact, I'm an economist...), but I did get a thorough introduction to morphemes and morphology from Felix Lehmann, who is a budding linguist, at a crucial early stage of the development of the selnolig package. Felix and his colleague Steffen Hildebrand provided a large number of crucial inputs and validations to the package -- including teaching me the basics of morphology! I very much appreciated getting this type of education. :-)
    – Mico
    Sep 16 at 18:45












  • 1




    i took a liberty and correct definition of newcommandvn[2]mathrm#1 to newcommandvn[1]mathrm#1 (after that your mwe works). compiling your mwe, i obtain quite different result as shown in your answer. i use recent miktex.
    – Zarko
    Sep 16 at 9:31











  • problem seems to be with myfootnote. if lipsum[2] is immediately after it, this paragraph not appear, but is printout only [2], i .e. option which paragraph from lipsum should be used. inserting blank lines before repair this malfunction.
    – Zarko
    Sep 16 at 9:40










  • @Zarko - Many thanks for applying the fix to the definition of vn. Something very weird seems to have happened during the copy-and-paste operation: In the tex file on my system, both vn and myfootnote are defined to take a single argument. However, upon pasting (and indenting), the two instances of [1] ended up as [2]. I have no idea how this came about. I suspect it's a site bug. Fortunately, both commands now show that they take a single argument.
    – Mico
    Sep 16 at 10:08







  • 1




    @Mico Unrelated, but I've been meaning to compliment you on your TUG talk. It was very interesting and you did a perfect job of explaining the linguistics! (I put this comment elsewhere, but I thought it would be better on one of your answers instead of a new user's question.)
    – Alan Munn
    Sep 16 at 18:36






  • 1




    @AlanMunn - Wow, thanks so much for this compliment!! I deeply appreciate it. You can probably tell that I'm not a linguist by training (in fact, I'm an economist...), but I did get a thorough introduction to morphemes and morphology from Felix Lehmann, who is a budding linguist, at a crucial early stage of the development of the selnolig package. Felix and his colleague Steffen Hildebrand provided a large number of crucial inputs and validations to the package -- including teaching me the basics of morphology! I very much appreciated getting this type of education. :-)
    – Mico
    Sep 16 at 18:45







1




1




i took a liberty and correct definition of newcommandvn[2]mathrm#1 to newcommandvn[1]mathrm#1 (after that your mwe works). compiling your mwe, i obtain quite different result as shown in your answer. i use recent miktex.
– Zarko
Sep 16 at 9:31





i took a liberty and correct definition of newcommandvn[2]mathrm#1 to newcommandvn[1]mathrm#1 (after that your mwe works). compiling your mwe, i obtain quite different result as shown in your answer. i use recent miktex.
– Zarko
Sep 16 at 9:31













problem seems to be with myfootnote. if lipsum[2] is immediately after it, this paragraph not appear, but is printout only [2], i .e. option which paragraph from lipsum should be used. inserting blank lines before repair this malfunction.
– Zarko
Sep 16 at 9:40




problem seems to be with myfootnote. if lipsum[2] is immediately after it, this paragraph not appear, but is printout only [2], i .e. option which paragraph from lipsum should be used. inserting blank lines before repair this malfunction.
– Zarko
Sep 16 at 9:40












@Zarko - Many thanks for applying the fix to the definition of vn. Something very weird seems to have happened during the copy-and-paste operation: In the tex file on my system, both vn and myfootnote are defined to take a single argument. However, upon pasting (and indenting), the two instances of [1] ended up as [2]. I have no idea how this came about. I suspect it's a site bug. Fortunately, both commands now show that they take a single argument.
– Mico
Sep 16 at 10:08





@Zarko - Many thanks for applying the fix to the definition of vn. Something very weird seems to have happened during the copy-and-paste operation: In the tex file on my system, both vn and myfootnote are defined to take a single argument. However, upon pasting (and indenting), the two instances of [1] ended up as [2]. I have no idea how this came about. I suspect it's a site bug. Fortunately, both commands now show that they take a single argument.
– Mico
Sep 16 at 10:08





1




1




@Mico Unrelated, but I've been meaning to compliment you on your TUG talk. It was very interesting and you did a perfect job of explaining the linguistics! (I put this comment elsewhere, but I thought it would be better on one of your answers instead of a new user's question.)
– Alan Munn
Sep 16 at 18:36




@Mico Unrelated, but I've been meaning to compliment you on your TUG talk. It was very interesting and you did a perfect job of explaining the linguistics! (I put this comment elsewhere, but I thought it would be better on one of your answers instead of a new user's question.)
– Alan Munn
Sep 16 at 18:36




1




1




@AlanMunn - Wow, thanks so much for this compliment!! I deeply appreciate it. You can probably tell that I'm not a linguist by training (in fact, I'm an economist...), but I did get a thorough introduction to morphemes and morphology from Felix Lehmann, who is a budding linguist, at a crucial early stage of the development of the selnolig package. Felix and his colleague Steffen Hildebrand provided a large number of crucial inputs and validations to the package -- including teaching me the basics of morphology! I very much appreciated getting this type of education. :-)
– Mico
Sep 16 at 18:45




@AlanMunn - Wow, thanks so much for this compliment!! I deeply appreciate it. You can probably tell that I'm not a linguist by training (in fact, I'm an economist...), but I did get a thorough introduction to morphemes and morphology from Felix Lehmann, who is a budding linguist, at a crucial early stage of the development of the selnolig package. Felix and his colleague Steffen Hildebrand provided a large number of crucial inputs and validations to the package -- including teaching me the basics of morphology! I very much appreciated getting this type of education. :-)
– Mico
Sep 16 at 18:45

















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f451090%2favoiding-excessive-space-under-equation%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

Peggy Mitchell

Palaiologos

The Forum (Inglewood, California)