Interactions between intersections, fillbetween and axis equal












4














Please be patient, this is a bit complex. I encountered some weird things when trying to answer this nice question. Start with the MWE



documentclass[tikz,border=3.14mm]{standalone}
%usetikzlibrary{intersections}
usepackage{pgfplots}
pgfplotsset{compat=1.16}
usepgfplotslibrary{fillbetween}

begin{document}
begin{tikzpicture}
begin{axis}[axis equal]
addplot[thick,samples=80,name path global=duck] {(-3)*x/abs(x)^(2/3)}; % From https://tex.stackexchange.com/a/144463/152550
addplot[thick,samples=80,name path global=koala] ({sqrt(16/3)*cos((x) r)}, {sqrt(16)*sin((x) r)});
path (0,0) coordinate (O) (1,0) coordinate(X);
fill[red,name intersections={of=duck and koala,by={i1,i2}}]
(i1) circle (2pt) (i2) circle (2pt);
end{axis}
end{tikzpicture}
end{document}


enter image description here



So far so good. However, if one activates usetikzlibrary{intersections} and deactivates usepgfplotslibrary{fillbetween} by just moving the % down, one receives the error



 ! Package pgf Error: No shape named intersection-2 is known.


that tells us that the second intersection cannot be found. If we stick with this, but comment out [axis equal], the error disappears, i.e. the second interaction is found. What's going on here?



Even more, if one moves the determination of the intersections out of the axis environment,



documentclass[tikz,border=3.14mm]{standalone}
%usetikzlibrary{intersections}
usepackage{pgfplots}
pgfplotsset{compat=1.16}
usepgfplotslibrary{fillbetween}

begin{document}
begin{tikzpicture}
begin{axis}[axis equal]
addplot[thick,samples=80,name path global=duck] {(-3)*x/abs(x)^(2/3)}; % From https://tex.stackexchange.com/a/144463/152550
addplot[thick,samples=80,name path global=koala] ({sqrt(16/3)*cos((x) r)}, {sqrt(16)*sin((x) r)});
path (0,0) coordinate (O) (1,0) coordinate(X);
end{axis}
fill[red,name intersections={of=duck and koala,by={i1,i2}}]
(i1) circle (2pt) (i2) circle (2pt);
end{tikzpicture}
end{document}


one gets



enter image description here



meaning that the intersections are not correct. On the other hand, it has been a common practice to compute the intersections outside the axis, see e.g. this nice answer. Notice that even if one drops axis equal in the last example the intersections are still incorrect.










share|improve this question



























    4














    Please be patient, this is a bit complex. I encountered some weird things when trying to answer this nice question. Start with the MWE



    documentclass[tikz,border=3.14mm]{standalone}
    %usetikzlibrary{intersections}
    usepackage{pgfplots}
    pgfplotsset{compat=1.16}
    usepgfplotslibrary{fillbetween}

    begin{document}
    begin{tikzpicture}
    begin{axis}[axis equal]
    addplot[thick,samples=80,name path global=duck] {(-3)*x/abs(x)^(2/3)}; % From https://tex.stackexchange.com/a/144463/152550
    addplot[thick,samples=80,name path global=koala] ({sqrt(16/3)*cos((x) r)}, {sqrt(16)*sin((x) r)});
    path (0,0) coordinate (O) (1,0) coordinate(X);
    fill[red,name intersections={of=duck and koala,by={i1,i2}}]
    (i1) circle (2pt) (i2) circle (2pt);
    end{axis}
    end{tikzpicture}
    end{document}


    enter image description here



    So far so good. However, if one activates usetikzlibrary{intersections} and deactivates usepgfplotslibrary{fillbetween} by just moving the % down, one receives the error



     ! Package pgf Error: No shape named intersection-2 is known.


    that tells us that the second intersection cannot be found. If we stick with this, but comment out [axis equal], the error disappears, i.e. the second interaction is found. What's going on here?



    Even more, if one moves the determination of the intersections out of the axis environment,



    documentclass[tikz,border=3.14mm]{standalone}
    %usetikzlibrary{intersections}
    usepackage{pgfplots}
    pgfplotsset{compat=1.16}
    usepgfplotslibrary{fillbetween}

    begin{document}
    begin{tikzpicture}
    begin{axis}[axis equal]
    addplot[thick,samples=80,name path global=duck] {(-3)*x/abs(x)^(2/3)}; % From https://tex.stackexchange.com/a/144463/152550
    addplot[thick,samples=80,name path global=koala] ({sqrt(16/3)*cos((x) r)}, {sqrt(16)*sin((x) r)});
    path (0,0) coordinate (O) (1,0) coordinate(X);
    end{axis}
    fill[red,name intersections={of=duck and koala,by={i1,i2}}]
    (i1) circle (2pt) (i2) circle (2pt);
    end{tikzpicture}
    end{document}


    one gets



    enter image description here



    meaning that the intersections are not correct. On the other hand, it has been a common practice to compute the intersections outside the axis, see e.g. this nice answer. Notice that even if one drops axis equal in the last example the intersections are still incorrect.










    share|improve this question

























      4












      4








      4


      1





      Please be patient, this is a bit complex. I encountered some weird things when trying to answer this nice question. Start with the MWE



      documentclass[tikz,border=3.14mm]{standalone}
      %usetikzlibrary{intersections}
      usepackage{pgfplots}
      pgfplotsset{compat=1.16}
      usepgfplotslibrary{fillbetween}

      begin{document}
      begin{tikzpicture}
      begin{axis}[axis equal]
      addplot[thick,samples=80,name path global=duck] {(-3)*x/abs(x)^(2/3)}; % From https://tex.stackexchange.com/a/144463/152550
      addplot[thick,samples=80,name path global=koala] ({sqrt(16/3)*cos((x) r)}, {sqrt(16)*sin((x) r)});
      path (0,0) coordinate (O) (1,0) coordinate(X);
      fill[red,name intersections={of=duck and koala,by={i1,i2}}]
      (i1) circle (2pt) (i2) circle (2pt);
      end{axis}
      end{tikzpicture}
      end{document}


      enter image description here



      So far so good. However, if one activates usetikzlibrary{intersections} and deactivates usepgfplotslibrary{fillbetween} by just moving the % down, one receives the error



       ! Package pgf Error: No shape named intersection-2 is known.


      that tells us that the second intersection cannot be found. If we stick with this, but comment out [axis equal], the error disappears, i.e. the second interaction is found. What's going on here?



      Even more, if one moves the determination of the intersections out of the axis environment,



      documentclass[tikz,border=3.14mm]{standalone}
      %usetikzlibrary{intersections}
      usepackage{pgfplots}
      pgfplotsset{compat=1.16}
      usepgfplotslibrary{fillbetween}

      begin{document}
      begin{tikzpicture}
      begin{axis}[axis equal]
      addplot[thick,samples=80,name path global=duck] {(-3)*x/abs(x)^(2/3)}; % From https://tex.stackexchange.com/a/144463/152550
      addplot[thick,samples=80,name path global=koala] ({sqrt(16/3)*cos((x) r)}, {sqrt(16)*sin((x) r)});
      path (0,0) coordinate (O) (1,0) coordinate(X);
      end{axis}
      fill[red,name intersections={of=duck and koala,by={i1,i2}}]
      (i1) circle (2pt) (i2) circle (2pt);
      end{tikzpicture}
      end{document}


      one gets



      enter image description here



      meaning that the intersections are not correct. On the other hand, it has been a common practice to compute the intersections outside the axis, see e.g. this nice answer. Notice that even if one drops axis equal in the last example the intersections are still incorrect.










      share|improve this question













      Please be patient, this is a bit complex. I encountered some weird things when trying to answer this nice question. Start with the MWE



      documentclass[tikz,border=3.14mm]{standalone}
      %usetikzlibrary{intersections}
      usepackage{pgfplots}
      pgfplotsset{compat=1.16}
      usepgfplotslibrary{fillbetween}

      begin{document}
      begin{tikzpicture}
      begin{axis}[axis equal]
      addplot[thick,samples=80,name path global=duck] {(-3)*x/abs(x)^(2/3)}; % From https://tex.stackexchange.com/a/144463/152550
      addplot[thick,samples=80,name path global=koala] ({sqrt(16/3)*cos((x) r)}, {sqrt(16)*sin((x) r)});
      path (0,0) coordinate (O) (1,0) coordinate(X);
      fill[red,name intersections={of=duck and koala,by={i1,i2}}]
      (i1) circle (2pt) (i2) circle (2pt);
      end{axis}
      end{tikzpicture}
      end{document}


      enter image description here



      So far so good. However, if one activates usetikzlibrary{intersections} and deactivates usepgfplotslibrary{fillbetween} by just moving the % down, one receives the error



       ! Package pgf Error: No shape named intersection-2 is known.


      that tells us that the second intersection cannot be found. If we stick with this, but comment out [axis equal], the error disappears, i.e. the second interaction is found. What's going on here?



      Even more, if one moves the determination of the intersections out of the axis environment,



      documentclass[tikz,border=3.14mm]{standalone}
      %usetikzlibrary{intersections}
      usepackage{pgfplots}
      pgfplotsset{compat=1.16}
      usepgfplotslibrary{fillbetween}

      begin{document}
      begin{tikzpicture}
      begin{axis}[axis equal]
      addplot[thick,samples=80,name path global=duck] {(-3)*x/abs(x)^(2/3)}; % From https://tex.stackexchange.com/a/144463/152550
      addplot[thick,samples=80,name path global=koala] ({sqrt(16/3)*cos((x) r)}, {sqrt(16)*sin((x) r)});
      path (0,0) coordinate (O) (1,0) coordinate(X);
      end{axis}
      fill[red,name intersections={of=duck and koala,by={i1,i2}}]
      (i1) circle (2pt) (i2) circle (2pt);
      end{tikzpicture}
      end{document}


      one gets



      enter image description here



      meaning that the intersections are not correct. On the other hand, it has been a common practice to compute the intersections outside the axis, see e.g. this nice answer. Notice that even if one drops axis equal in the last example the intersections are still incorrect.







      pgfplots intersections






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Oct 27 at 4:17









      marmot

      86.4k499184




      86.4k499184






















          2 Answers
          2






          active

          oldest

          votes


















          1














          The reason that coordinates for the computed coordinates do not match up is a bug in pgfplots.



          The underlying reason is explained in the pgfplots manual section "4.26 TikZ Interoperability": pgfplots rescales and translates the coordinate system. Pgfplots does its best to hide this rescaling from the end user. For example, named coordinates within an axis are automatically rescaled after leaving the axis such that you can refer to them after end{axis}. This feature does not exist for the coordinates of named paths.



          A workaround is to ensure that the coordinate systems match up, i.e. to disable the rescaling features of pgfplots.



          This is explained in the aforementioned section of the manual. Applied to your example, this might look like



          documentclass[tikz,border=3.14mm]{standalone}
          %usetikzlibrary{intersections}
          usepackage{pgfplots}
          pgfplotsset{compat=1.16}
          usepgfplotslibrary{fillbetween}

          begin{document}
          begin{tikzpicture}
          begin{axis}[axis equal,
          disabledatascaling,
          anchor=origin,
          x=1cm,y=1cm,
          ]
          addplot[thick,samples=80,name path=duck] {(-3)*x/abs(x)^(2/3)};
          addplot[thick,samples=80,name path=koala] ({sqrt(16/3)*cos((x) r)}, {sqrt(16)*sin((x) r)});
          path (0,0) coordinate (O) (1,0) coordinate(X);
          end{axis}
          fill[red,name intersections={of=duck and koala,by={i1,i2}}]
          (i1) circle (2pt) (i2) circle (2pt);
          end{tikzpicture}
          end{document}


          enter image description here



          This might affect rescaling capabilities like axis equal, though.



          But again: the reason that this does not work out of the box is actually a bug: pgfplots does not translate the coordinates of named paths when it leaves end{axis}.






          share|improve this answer





















          • Thank you so much!!!!
            – marmot
            Dec 8 at 12:44



















          2














          This is most likely because PGFPlots uses a "newer" version of the intersections library than PGF does and thus this is similar to the external library (compare https://tex.stackexchange.com/a/341662/95441). To support this you can do a diff on the both files



          pgflibraryintersections.code.tex
          pgfplotsoldpgfsupp_pgflibraryintersections.code.tex





          share|improve this answer

















          • 1




            Thanks! But this only addresses the more minor problem. The main issue is why the intersections are off if one computes them outside of the axis environment.
            – marmot
            Oct 28 at 18:34






          • 1




            There I cannot help you. But I would compute the intersections inside the axis environment (and label them) and then you can do a foreach loop outside if you want. I'll contact Christian and ask him to have a look at this issue.
            – Stefan Pinnow
            Oct 28 at 18:53











          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',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          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%2f457012%2finteractions-between-intersections-fillbetween-and-axis-equal%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          The reason that coordinates for the computed coordinates do not match up is a bug in pgfplots.



          The underlying reason is explained in the pgfplots manual section "4.26 TikZ Interoperability": pgfplots rescales and translates the coordinate system. Pgfplots does its best to hide this rescaling from the end user. For example, named coordinates within an axis are automatically rescaled after leaving the axis such that you can refer to them after end{axis}. This feature does not exist for the coordinates of named paths.



          A workaround is to ensure that the coordinate systems match up, i.e. to disable the rescaling features of pgfplots.



          This is explained in the aforementioned section of the manual. Applied to your example, this might look like



          documentclass[tikz,border=3.14mm]{standalone}
          %usetikzlibrary{intersections}
          usepackage{pgfplots}
          pgfplotsset{compat=1.16}
          usepgfplotslibrary{fillbetween}

          begin{document}
          begin{tikzpicture}
          begin{axis}[axis equal,
          disabledatascaling,
          anchor=origin,
          x=1cm,y=1cm,
          ]
          addplot[thick,samples=80,name path=duck] {(-3)*x/abs(x)^(2/3)};
          addplot[thick,samples=80,name path=koala] ({sqrt(16/3)*cos((x) r)}, {sqrt(16)*sin((x) r)});
          path (0,0) coordinate (O) (1,0) coordinate(X);
          end{axis}
          fill[red,name intersections={of=duck and koala,by={i1,i2}}]
          (i1) circle (2pt) (i2) circle (2pt);
          end{tikzpicture}
          end{document}


          enter image description here



          This might affect rescaling capabilities like axis equal, though.



          But again: the reason that this does not work out of the box is actually a bug: pgfplots does not translate the coordinates of named paths when it leaves end{axis}.






          share|improve this answer





















          • Thank you so much!!!!
            – marmot
            Dec 8 at 12:44
















          1














          The reason that coordinates for the computed coordinates do not match up is a bug in pgfplots.



          The underlying reason is explained in the pgfplots manual section "4.26 TikZ Interoperability": pgfplots rescales and translates the coordinate system. Pgfplots does its best to hide this rescaling from the end user. For example, named coordinates within an axis are automatically rescaled after leaving the axis such that you can refer to them after end{axis}. This feature does not exist for the coordinates of named paths.



          A workaround is to ensure that the coordinate systems match up, i.e. to disable the rescaling features of pgfplots.



          This is explained in the aforementioned section of the manual. Applied to your example, this might look like



          documentclass[tikz,border=3.14mm]{standalone}
          %usetikzlibrary{intersections}
          usepackage{pgfplots}
          pgfplotsset{compat=1.16}
          usepgfplotslibrary{fillbetween}

          begin{document}
          begin{tikzpicture}
          begin{axis}[axis equal,
          disabledatascaling,
          anchor=origin,
          x=1cm,y=1cm,
          ]
          addplot[thick,samples=80,name path=duck] {(-3)*x/abs(x)^(2/3)};
          addplot[thick,samples=80,name path=koala] ({sqrt(16/3)*cos((x) r)}, {sqrt(16)*sin((x) r)});
          path (0,0) coordinate (O) (1,0) coordinate(X);
          end{axis}
          fill[red,name intersections={of=duck and koala,by={i1,i2}}]
          (i1) circle (2pt) (i2) circle (2pt);
          end{tikzpicture}
          end{document}


          enter image description here



          This might affect rescaling capabilities like axis equal, though.



          But again: the reason that this does not work out of the box is actually a bug: pgfplots does not translate the coordinates of named paths when it leaves end{axis}.






          share|improve this answer





















          • Thank you so much!!!!
            – marmot
            Dec 8 at 12:44














          1












          1








          1






          The reason that coordinates for the computed coordinates do not match up is a bug in pgfplots.



          The underlying reason is explained in the pgfplots manual section "4.26 TikZ Interoperability": pgfplots rescales and translates the coordinate system. Pgfplots does its best to hide this rescaling from the end user. For example, named coordinates within an axis are automatically rescaled after leaving the axis such that you can refer to them after end{axis}. This feature does not exist for the coordinates of named paths.



          A workaround is to ensure that the coordinate systems match up, i.e. to disable the rescaling features of pgfplots.



          This is explained in the aforementioned section of the manual. Applied to your example, this might look like



          documentclass[tikz,border=3.14mm]{standalone}
          %usetikzlibrary{intersections}
          usepackage{pgfplots}
          pgfplotsset{compat=1.16}
          usepgfplotslibrary{fillbetween}

          begin{document}
          begin{tikzpicture}
          begin{axis}[axis equal,
          disabledatascaling,
          anchor=origin,
          x=1cm,y=1cm,
          ]
          addplot[thick,samples=80,name path=duck] {(-3)*x/abs(x)^(2/3)};
          addplot[thick,samples=80,name path=koala] ({sqrt(16/3)*cos((x) r)}, {sqrt(16)*sin((x) r)});
          path (0,0) coordinate (O) (1,0) coordinate(X);
          end{axis}
          fill[red,name intersections={of=duck and koala,by={i1,i2}}]
          (i1) circle (2pt) (i2) circle (2pt);
          end{tikzpicture}
          end{document}


          enter image description here



          This might affect rescaling capabilities like axis equal, though.



          But again: the reason that this does not work out of the box is actually a bug: pgfplots does not translate the coordinates of named paths when it leaves end{axis}.






          share|improve this answer












          The reason that coordinates for the computed coordinates do not match up is a bug in pgfplots.



          The underlying reason is explained in the pgfplots manual section "4.26 TikZ Interoperability": pgfplots rescales and translates the coordinate system. Pgfplots does its best to hide this rescaling from the end user. For example, named coordinates within an axis are automatically rescaled after leaving the axis such that you can refer to them after end{axis}. This feature does not exist for the coordinates of named paths.



          A workaround is to ensure that the coordinate systems match up, i.e. to disable the rescaling features of pgfplots.



          This is explained in the aforementioned section of the manual. Applied to your example, this might look like



          documentclass[tikz,border=3.14mm]{standalone}
          %usetikzlibrary{intersections}
          usepackage{pgfplots}
          pgfplotsset{compat=1.16}
          usepgfplotslibrary{fillbetween}

          begin{document}
          begin{tikzpicture}
          begin{axis}[axis equal,
          disabledatascaling,
          anchor=origin,
          x=1cm,y=1cm,
          ]
          addplot[thick,samples=80,name path=duck] {(-3)*x/abs(x)^(2/3)};
          addplot[thick,samples=80,name path=koala] ({sqrt(16/3)*cos((x) r)}, {sqrt(16)*sin((x) r)});
          path (0,0) coordinate (O) (1,0) coordinate(X);
          end{axis}
          fill[red,name intersections={of=duck and koala,by={i1,i2}}]
          (i1) circle (2pt) (i2) circle (2pt);
          end{tikzpicture}
          end{document}


          enter image description here



          This might affect rescaling capabilities like axis equal, though.



          But again: the reason that this does not work out of the box is actually a bug: pgfplots does not translate the coordinates of named paths when it leaves end{axis}.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Dec 8 at 10:40









          Christian Feuersänger

          48.7k4114171




          48.7k4114171












          • Thank you so much!!!!
            – marmot
            Dec 8 at 12:44


















          • Thank you so much!!!!
            – marmot
            Dec 8 at 12:44
















          Thank you so much!!!!
          – marmot
          Dec 8 at 12:44




          Thank you so much!!!!
          – marmot
          Dec 8 at 12:44











          2














          This is most likely because PGFPlots uses a "newer" version of the intersections library than PGF does and thus this is similar to the external library (compare https://tex.stackexchange.com/a/341662/95441). To support this you can do a diff on the both files



          pgflibraryintersections.code.tex
          pgfplotsoldpgfsupp_pgflibraryintersections.code.tex





          share|improve this answer

















          • 1




            Thanks! But this only addresses the more minor problem. The main issue is why the intersections are off if one computes them outside of the axis environment.
            – marmot
            Oct 28 at 18:34






          • 1




            There I cannot help you. But I would compute the intersections inside the axis environment (and label them) and then you can do a foreach loop outside if you want. I'll contact Christian and ask him to have a look at this issue.
            – Stefan Pinnow
            Oct 28 at 18:53
















          2














          This is most likely because PGFPlots uses a "newer" version of the intersections library than PGF does and thus this is similar to the external library (compare https://tex.stackexchange.com/a/341662/95441). To support this you can do a diff on the both files



          pgflibraryintersections.code.tex
          pgfplotsoldpgfsupp_pgflibraryintersections.code.tex





          share|improve this answer

















          • 1




            Thanks! But this only addresses the more minor problem. The main issue is why the intersections are off if one computes them outside of the axis environment.
            – marmot
            Oct 28 at 18:34






          • 1




            There I cannot help you. But I would compute the intersections inside the axis environment (and label them) and then you can do a foreach loop outside if you want. I'll contact Christian and ask him to have a look at this issue.
            – Stefan Pinnow
            Oct 28 at 18:53














          2












          2








          2






          This is most likely because PGFPlots uses a "newer" version of the intersections library than PGF does and thus this is similar to the external library (compare https://tex.stackexchange.com/a/341662/95441). To support this you can do a diff on the both files



          pgflibraryintersections.code.tex
          pgfplotsoldpgfsupp_pgflibraryintersections.code.tex





          share|improve this answer












          This is most likely because PGFPlots uses a "newer" version of the intersections library than PGF does and thus this is similar to the external library (compare https://tex.stackexchange.com/a/341662/95441). To support this you can do a diff on the both files



          pgflibraryintersections.code.tex
          pgfplotsoldpgfsupp_pgflibraryintersections.code.tex






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Oct 28 at 18:18









          Stefan Pinnow

          19.4k83175




          19.4k83175








          • 1




            Thanks! But this only addresses the more minor problem. The main issue is why the intersections are off if one computes them outside of the axis environment.
            – marmot
            Oct 28 at 18:34






          • 1




            There I cannot help you. But I would compute the intersections inside the axis environment (and label them) and then you can do a foreach loop outside if you want. I'll contact Christian and ask him to have a look at this issue.
            – Stefan Pinnow
            Oct 28 at 18:53














          • 1




            Thanks! But this only addresses the more minor problem. The main issue is why the intersections are off if one computes them outside of the axis environment.
            – marmot
            Oct 28 at 18:34






          • 1




            There I cannot help you. But I would compute the intersections inside the axis environment (and label them) and then you can do a foreach loop outside if you want. I'll contact Christian and ask him to have a look at this issue.
            – Stefan Pinnow
            Oct 28 at 18:53








          1




          1




          Thanks! But this only addresses the more minor problem. The main issue is why the intersections are off if one computes them outside of the axis environment.
          – marmot
          Oct 28 at 18:34




          Thanks! But this only addresses the more minor problem. The main issue is why the intersections are off if one computes them outside of the axis environment.
          – marmot
          Oct 28 at 18:34




          1




          1




          There I cannot help you. But I would compute the intersections inside the axis environment (and label them) and then you can do a foreach loop outside if you want. I'll contact Christian and ask him to have a look at this issue.
          – Stefan Pinnow
          Oct 28 at 18:53




          There I cannot help you. But I would compute the intersections inside the axis environment (and label them) and then you can do a foreach loop outside if you want. I'll contact Christian and ask him to have a look at this issue.
          – Stefan Pinnow
          Oct 28 at 18:53


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to TeX - LaTeX Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f457012%2finteractions-between-intersections-fillbetween-and-axis-equal%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          How to change which sound is reproduced for terminal bell?

          Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents

          Can I use Tabulator js library in my java Spring + Thymeleaf project?