DEBUG: FC_WEIGHT didn't match

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

DEBUG: FC_WEIGHT didn't match

Ian McCallion
I have just updated to the latest windows version:

  > ver
  Microsoft Windows [Version 10.0.18363.592]

and now I get a message I've never seen before: "DEBUG: FC_WEIGHT didn't match" on the print statement in the code below. This applies under Octave versions 4.4.1 and 5.2.0. 

A quick internet search suggests it's a ghostscript problem, but I've tried removing myfont and the set statement and neither makes any difference. Apparently it's a fontconfig problem but nowhere am I explicitly using fontconfig.

Any ideas how to get rid of the debug message?

Cheers... Ian

-------------------------------------------------------
  % 23a. Set graphing defaults used by all subsequent plots
myfont={'fontsize',25,'fontweight','bold'};
mygraphs={'-dpng','-S800,800'};
mywidegraphs={'-dpng','-S1800,800'};
set(0, 'defaulttextfontsize', 15)
       
% 23b. Create png file of SD By Row
thisfig = figure(1, 'visible','off');
xrange = 1:length(listRowsInTouch);
ssd=sd1PieceByRn(listRowsInTouch);
plot(xrange, [ssd; mean(ssd)*ones(1,db.nRowsInTouch); msThreshold*ones(1,db.nRowsInTouch)], 'Linewidth',2);
thislegend=legend('Actual','Average over touch','Threshold');
setlegend(thislegend,16);
axis([0, xrange(end)+2, min(ssd)-5, 5+max(10,max(ssd))]);
setaxes(thisfig,28,[0:16:db.nRowsInTouch]);
xlabel('Row number', myfont{:});
ylabel('Milliseconds', myfont{:});
title('Standard Deviation (Touch only)', myfont{:});
grid ('on');
print (1, fsOutStdByRow, mywidegraphs{:});
---------------------------------------------------------------


Reply | Threaded
Open this post in threaded view
|

Re: DEBUG: FC_WEIGHT didn't match

siko1056
On 2/13/20 1:49 AM, Ian McCallion wrote:

> I have just updated to the latest windows version:
>
>   > ver
>   Microsoft Windows [Version 10.0.18363.592]
>
> and now I get a message I've never seen before: "DEBUG: FC_WEIGHT didn't
> match" on the print statement in the code below. This applies under
> Octave versions 4.4.1 and 5.2.0. 
>
> A quick internet search suggests it's a ghostscript problem, but I've
> tried removing myfont and the set statement and neither makes any
> difference. Apparently it's a fontconfig problem but nowhere am I
> explicitly using fontconfig.
>
> Any ideas how to get rid of the debug message?
>
> Cheers... Ian
>
> -------------------------------------------------------
>   % 23a. Set graphing defaults used by all subsequent plots
> myfont={'fontsize',25,'fontweight','bold'};
> mygraphs={'-dpng','-S800,800'};
> mywidegraphs={'-dpng','-S1800,800'};
> set(0, 'defaulttextfontsize', 15)
>        
> % 23b. Create png file of SD By Row
> thisfig = figure(1, 'visible','off');
> xrange = 1:length(listRowsInTouch);
> ssd=sd1PieceByRn(listRowsInTouch);
> plot(xrange, [ssd; mean(ssd)*ones(1,db.nRowsInTouch);
> msThreshold*ones(1,db.nRowsInTouch)], 'Linewidth',2);
> thislegend=legend('Actual','Average over touch','Threshold');
> setlegend(thislegend,16);
> axis([0, xrange(end)+2, min(ssd)-5, 5+max(10,max(ssd))]);
> setaxes(thisfig,28,[0:16:db.nRowsInTouch]);
> xlabel('Row number', myfont{:});
> ylabel('Milliseconds', myfont{:});
> title('Standard Deviation (Touch only)', myfont{:});
> grid ('on');
> print (1, fsOutStdByRow, mywidegraphs{:});
> ---------------------------------------------------------------
>


Sorry, I cannot reproduce the message.  In your example
"listRowsInTouch" is not defined.

Did you reinstall Octave since updating MS Windows?

Kai


Reply | Threaded
Open this post in threaded view
|

Re: DEBUG: FC_WEIGHT didn't match

Ian McCallion
On Thu, 13 Feb 2020 at 03:04, Kai Torben Ohlhus <[hidden email]> wrote:
On 2/13/20 1:49 AM, Ian McCallion wrote:
> I have just updated to the latest windows version:
>
>   > ver
>   Microsoft Windows [Version 10.0.18363.592]
>
> and now I get a message I've never seen before: "DEBUG: FC_WEIGHT didn't
> match" on the print statement in the code below. This applies under
> Octave versions 4.4.1 and 5.2.0. 
>
> A quick internet search suggests it's a ghostscript problem, but I've
> tried removing myfont and the set statement and neither makes any
> difference. Apparently it's a fontconfig problem but nowhere am I
> explicitly using fontconfig.
>
> Any ideas how to get rid of the debug message?
>
> Cheers... Ian
>
> -------------------------------------------------------
>   <snip>
> ---------------------------------------------------------------

Sorry, I cannot reproduce the message.  In your example
"listRowsInTouch" is not defined.

Apologies! I was hoping/expecting someone on the list to recognise the error.

An updated version of the code is attached which runs standalone on my machine and produces the error.

Did you reinstall Octave since updating MS Windows?

No. I will try that now, but I will need to re-download it so it will take some time. 

Cheers... Ian


Reply | Threaded
Open this post in threaded view
|

Re: DEBUG: FC_WEIGHT didn't match

Ian McCallion
On Thu, 13 Feb 2020 at 11:13, Ian McCallion <[hidden email]> wrote:
On Thu, 13 Feb 2020 at 03:04, Kai Torben Ohlhus <[hidden email]> wrote:
On 2/13/20 1:49 AM, Ian McCallion wrote:
> I have just updated to the latest windows version:
>
>   > ver
>   Microsoft Windows [Version 10.0.18363.592]
>
> and now I get a message I've never seen before: "DEBUG: FC_WEIGHT didn't
> match" on the print statement in the code below. This applies under
> Octave versions 4.4.1 and 5.2.0. 
>
> A quick internet search suggests it's a ghostscript problem, but I've
> tried removing myfont and the set statement and neither makes any
> difference. Apparently it's a fontconfig problem but nowhere am I
> explicitly using fontconfig.
>
> Any ideas how to get rid of the debug message?
>
> Cheers... Ian
>
> -------------------------------------------------------
>   <snip>
> ---------------------------------------------------------------

Sorry, I cannot reproduce the message.  In your example
"listRowsInTouch" is not defined.

Apologies! I was hoping/expecting someone on the list to recognise the error.

An updated version of the code is attached which runs standalone on my machine and produces the error.

Did you reinstall Octave since updating MS Windows?

No. I will try that now, but I will need to re-download it so it will take some time. 

I've now uninstalled and reinstalled:
   GNU Octave Version: 5.2.0 (hg id: eb46a9f47164)
   GNU Octave License: GNU General Public License
   Operating System: MINGW32_NT-6.2 Windows 6.2  x86_64 
and I still get the "DEBUG: FC_WEIGHT didn't match" message.

Code is below. 

Cheers... Ian

--------------------------------

close      
listRowsInTouch=5:14;
db.nRowsInTouch=10;
fsOutStdByRow='temp.png';
sd1PieceByRn=rand(1,20);
msThreshold = .5;
graphics_toolkit('gnuplot');
tic
% 23a. Set graphing defaults used by all subsequent plots
myfont={'fontsize',25,'fontweight','bold'};
mygraphs={'-dpng','-S800,800'};
mywidegraphs={'-dpng','-S1800,800'};
set(0, 'defaulttextfontsize', 15)

% 23b. Create png file of SD By Row
thisfig = figure(1, 'visible','on');
xrange = 1:length(listRowsInTouch);
ssd=sd1PieceByRn(listRowsInTouch);
plot(xrange, [ssd; mean(ssd)*ones(1,db.nRowsInTouch); msThreshold*ones(1,db.nRowsInTouch)], 'Linewidth',2);
thislegend=legend('Actual','Average over touch','Threshold');
%setlegend(thislegend,16);
axis([0, xrange(end)+2, min(ssd)-5, 5+max(10,max(ssd))]);
%setaxes(thisfig,28,[0:16:db.nRowsInTouch]);
xlabel('Row number', myfont{:});
ylabel('Milliseconds', myfont{:});
title('Standard Deviation (Touch only)', myfont{:});
grid ('on');
print (1, fsOutStdByRow, mywidegraphs{:});
toc
-------------------------------------------------



Reply | Threaded
Open this post in threaded view
|

Re: DEBUG: FC_WEIGHT didn't match

siko1056
On 2/13/20 9:31 PM, Ian McCallion wrote:

> On Thu, 13 Feb 2020 at 11:13, Ian McCallion <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     On Thu, 13 Feb 2020 at 03:04, Kai Torben Ohlhus <[hidden email]
>     <mailto:[hidden email]>> wrote:
>
>         On 2/13/20 1:49 AM, Ian McCallion wrote:
>         > I have just updated to the latest windows version:
>         >
>         >   > ver
>         >   Microsoft Windows [Version 10.0.18363.592]
>         >
>         > and now I get a message I've never seen before: "DEBUG:
>         FC_WEIGHT didn't
>         > match" on the print statement in the code below. This applies
>         under
>         > Octave versions 4.4.1 and 5.2.0. 
>         >
>         > A quick internet search suggests it's a ghostscript problem,
>         but I've
>         > tried removing myfont and the set statement and neither makes any
>         > difference. Apparently it's a fontconfig problem but nowhere am I
>         > explicitly using fontconfig.
>         >
>         > Any ideas how to get rid of the debug message?
>         >
>         > Cheers... Ian
>         >
> <snip>
>
> I've now uninstalled and reinstalled:
>    GNU Octave Version: 5.2.0 (hg id: eb46a9f47164)
>    GNU Octave License: GNU General Public License
>    Operating System: MINGW32_NT-6.2 Windows 6.2  x86_64 
> and I still get the "DEBUG: FC_WEIGHT didn't match" message.
>
> Code is below. 
>
> Cheers... Ian
>
> --------------------------------
>
> close      
> listRowsInTouch=5:14;
> db.nRowsInTouch=10;
> fsOutStdByRow='temp.png';
> sd1PieceByRn=rand(1,20);
> msThreshold = .5;
> graphics_toolkit('gnuplot');
> tic
> % 23a. Set graphing defaults used by all subsequent plots
> myfont={'fontsize',25,'fontweight','bold'};
> mygraphs={'-dpng','-S800,800'};
> mywidegraphs={'-dpng','-S1800,800'};
> set(0, 'defaulttextfontsize', 15)
>
> % 23b. Create png file of SD By Row
> thisfig = figure(1, 'visible','on');
> xrange = 1:length(listRowsInTouch);
> ssd=sd1PieceByRn(listRowsInTouch);
> plot(xrange, [ssd; mean(ssd)*ones(1,db.nRowsInTouch);
> msThreshold*ones(1,db.nRowsInTouch)], 'Linewidth',2);
> thislegend=legend('Actual','Average over touch','Threshold');
> %setlegend(thislegend,16);
> axis([0, xrange(end)+2, min(ssd)-5, 5+max(10,max(ssd))]);
> %setaxes(thisfig,28,[0:16:db.nRowsInTouch]);
> xlabel('Row number', myfont{:});
> ylabel('Milliseconds', myfont{:});
> title('Standard Deviation (Touch only)', myfont{:});
> grid ('on');
> print (1, fsOutStdByRow, mywidegraphs{:});
> toc
> -------------------------------------------------
>

Confirmed.  An important observation is, that you are plotting with
"gnuplot".  For "fltk" and "qt" I do not see this DEBUG message.  Is
there a particular reason, why you want to use "gnuplot"?

The message is printed in


C:\Octave\Octave-5.2.0\mingw64\share\octave\5.2.0\m\plot\util\private\__gnuplot_print__.m
(line 201)

with the gnuplot-pipeline:

'C:\Octave\OCTAVE~1.0\mingw64\bin\gs.exe -dQUIET -dNOPAUSE -dBATCH
-dSAFER -dAutoRotatePages=/None -sDEVICE=png16m -dLanguageLevel=2
-dTextAlphaBits=4 -dGraphicsAlphaBits=1 -r72x72 -dEPSCrop
-sOutputFile="temp.png"
C:\Users\siko1056\AppData\Local\Temp\oct-tdNSWy.eps & del
C:\Users\siko1056\AppData\Local\Temp\oct-tdNSWy.eps'

Thus it seems indeed to be a ghostscript problem.

HTH,
Kai


Reply | Threaded
Open this post in threaded view
|

Re: DEBUG: FC_WEIGHT didn't match

Ian McCallion
On Thu, 13 Feb 2020 at 13:54, Kai Torben Ohlhus <[hidden email]> wrote:
On 2/13/20 9:31 PM, Ian McCallion wrote:
> On Thu, 13 Feb 2020 at 11:13, Ian McCallion <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     On Thu, 13 Feb 2020 at 03:04, Kai Torben Ohlhus <[hidden email]
>     <mailto:[hidden email]>> wrote:
>
>         On 2/13/20 1:49 AM, Ian McCallion wrote:
>         > I have just updated to the latest windows version:
>         >
>         >   > ver
>         >   Microsoft Windows [Version 10.0.18363.592]
>         >
>         > and now I get a message I've never seen before: "DEBUG:
>         FC_WEIGHT didn't
>         > match" on the print statement in the code below. This applies
>         under
>         > Octave versions 4.4.1 and 5.2.0. 
>         >
>         > A quick internet search suggests it's a ghostscript problem,
>         but I've
>         > tried removing myfont and the set statement and neither makes any
>         > difference. Apparently it's a fontconfig problem but nowhere am I
>         > explicitly using fontconfig.
>         >
>         > Any ideas how to get rid of the debug message?
>         >
>         > Cheers... Ian
>         >
> <snip>
>
> I've now uninstalled and reinstalled:
>    GNU Octave Version: 5.2.0 (hg id: eb46a9f47164)
>    GNU Octave License: GNU General Public License
>    Operating System: MINGW32_NT-6.2 Windows 6.2  x86_64 
> and I still get the "DEBUG: FC_WEIGHT didn't match" message.
>
> Code is below. 
>
> Cheers... Ian
> --------------------------------
> close      
> listRowsInTouch=5:14;
> db.nRowsInTouch=10;
> fsOutStdByRow='temp.png';
> sd1PieceByRn=rand(1,20);
> msThreshold = .5;
> graphics_toolkit('gnuplot');
> tic
> % 23a. Set graphing defaults used by all subsequent plots
> myfont={'fontsize',25,'fontweight','bold'};
> mygraphs={'-dpng','-S800,800'};
> mywidegraphs={'-dpng','-S1800,800'};
> set(0, 'defaulttextfontsize', 15)
>
> % 23b. Create png file of SD By Row
> thisfig = figure(1, 'visible','on');
> xrange = 1:length(listRowsInTouch);
> ssd=sd1PieceByRn(listRowsInTouch);
> plot(xrange, [ssd; mean(ssd)*ones(1,db.nRowsInTouch);
> msThreshold*ones(1,db.nRowsInTouch)], 'Linewidth',2);
> thislegend=legend('Actual','Average over touch','Threshold');
> %setlegend(thislegend,16);
> axis([0, xrange(end)+2, min(ssd)-5, 5+max(10,max(ssd))]);
> %setaxes(thisfig,28,[0:16:db.nRowsInTouch]);
> xlabel('Row number', myfont{:});
> ylabel('Milliseconds', myfont{:});
> title('Standard Deviation (Touch only)', myfont{:});
> grid ('on');
> print (1, fsOutStdByRow, mywidegraphs{:});
> toc
> -------------------------------------------------

Confirmed.  An important observation is, that you are plotting with
"gnuplot".  For "fltk" and "qt" I do not see this DEBUG message.  Is
there a particular reason, why you want to use "gnuplot"?

I think there was a reason, back when I first developed the code about 8 years ago, but I can confirm that qt works for me now. Many thanks for your help.

Cheers... Ian