Unable using 13.1.0 for Mac OS X ARM (64-bit) also seen on 12.3.0 for Mac OS X x86 (64-bit) (May 10, 2021), and MMA version 13.1 Windows 10 to suppress pink box output around ListLogLinearPlot and warning message. Interestingly, this occured on the second time the code was run, but not the first time the code was run, such that some parameter in the ListLogLinearPlot routine is not being properly reinitialized. The trace for the error, when it occurs is:
Message[N::precsm, 15.9546]
N[{5, 10, 50, 100, 500, 1000}, 15.9546]
What this is doing is converting 55 decimal place integers into machine numbers, and it does not help to input them as integers with infinite precision, they get converted to machine numbers of <16 place precision anyway. It may have to do with having extended precision y-values in the plot at the same time, see below. What gives?
Nothing, block structure, Quiet, etc. works to suppress error when I use $MinPrecision = 55; only changing that to $MinPrecision=0; which I cannot use in the remainder of my code, works as a preamble to the following code example
$MinPrecision = 55;
xy = {{5.`55.,
0.0440577197159802285287831435698347138365015230619050622630249999\
9977411452125`55.}, {10.`55.,
0.0397767351603008920529547774037456110013244540775730484884499999\
9979606327965`55.}, {15.`55.,
0.0379735868537246582793143777075686109229095658861249757409999999\
9980530808444`55.}, {20.`55.,
0.0403678334462315117337176898869294620204074803390080127334749999\
9979303269795`55.}, {30.`55.,
0.0425471352074908671223890338905870945655115670604601536368499999\
9978185934116`55.}, {40.`55.,
0.0339015764395359449229476472678576372358931627517952220530499999\
9982618542507`55.}, {60.`55.,
0.0305579901756859750115614756458075708653225091517590606670499999\
9984332810946`55.}, {90.`55.,
0.0280861246163397472556438416252205575127934902403037556423999999\
9985600145114`55.}, {120.`55.,
0.0250470435300903996040446249187500507581140925931280303826249999\
9987158292677`55.}, {180.`55.,
0.0223841158985241735674763525197601764701238934759563732787749999\
9988523585041`55.}, {240.`55.,
0.0183718123819042096738129465733000968254391091559129796155749999\
9990580707167`55.}, {360.`55.,
0.0146878968019123678250178253397199344135782283144445660884999999\
9992469463644`55.}, {480.`55.,
0.0129026605646067588901884229915182025478628257672824013484749999\
9993384760543`55.}, {720.`55.,
0.0092485984333992917727449640045634871571677543329571678337749999\
9995258211051`55.}, {1440.`55.,
0.0055288587148662002463278480750327883199079022029169382918499999\
9997165334689`55.}};
ListLogLinearPlot[xy, ImageSize -> Medium]
Other than reinitializing Mathematica by quitting the kernel and then rerunning code, which gets me one, and only one error free plot, the only other thing I seem to be able to do is distract it, for example,
by adding ListPlot[{1, 2}] afterwords, which for some reason, does work. However, when the second plot run is ListLogLinearPlot[{1,2}] rather than ListPlot[{1,2}] although the error box around the first plot is cleared, the same error box, message and trace occurs for the second 'ListLogLinearPlot` command.
Therefore, there is an incomplete clearing of some code setting, flag or parameter in the ListLinearLogPlot routine that is properly cleared when ListPlot is run, at least for the two Versions on two different Mac OS, one with an Intel processor and the other with an M1 chip, as well as a v13.1 MMA Windows 10 OS.
Because this is annoying, I offered a bounty for confirmation of this bug and/or the best fix or recommendation offered.
P.S. Another error I have seen concerns tick marks, with no numerical axes labeling occurring, but it was inconsistent, so there is something rather seriously wrong with the runtime code.
