Am 26.01.2023 um 11:43 schrieb Marcin Błażejowski:
On 26.01.2023 08:51, Sven Schreiber wrote:
Am 26.01.2023 um 08:45 schrieb Marcin Błażejowski:
Hi,
the solution was simpler that I thought: the problem was that
print_NR_status() did verify 'set messages on/off' , but did not
checked for
On 26.01.2023 08:51, Sven Schreiber wrote:
Am 26.01.2023 um 08:45 schrieb Marcin Błażejowski:
Hi,
the solution was simpler that I thought: the problem was that
print_NR_status() did verify 'set messages on/off' , but did not
checked for 'set warnings on/off'. The patch in attachment.
On 26.01.2023 09:15, Riccardo (Jack) Lucchetti wrote:
On Thu, 26 Jan 2023, Marcin Błażejowski wrote:
Hi,
the solution was simpler that I thought: the problem was that
print_NR_status() did verify 'set messages on/off' , but did not
checked for 'set warnings on/off'. The patch in attachment.
Am 26.01.2023 um 09:15 schrieb Riccardo (Jack) Lucchetti:
On Thu, 26 Jan 2023, Marcin Błażejowski wrote:
Hi,
the solution was simpler that I thought: the problem was that
print_NR_status() did verify 'set messages on/off' , but did not
checked for 'set warnings on/off'. The patch in
On Thu, 26 Jan 2023, Marcin Błażejowski wrote:
Hi,
the solution was simpler that I thought: the problem was that
print_NR_status() did verify 'set messages on/off' , but did not checked for
'set warnings on/off'. The patch in attachment.
Marcin,
of course in this case this is not a
Am 26.01.2023 um 08:45 schrieb Marcin Błażejowski:
Hi,
the solution was simpler that I thought: the problem was that
print_NR_status() did verify 'set messages on/off' , but did not
checked for 'set warnings on/off'. The patch in attachment.
Marcin, I don't think this is the complete
On 19.01.2023 18:28, Cottrell, Allin wrote:
On Thu, Jan 19, 2023 at 10:55 AM Sven Schreiber
wrote:
Am 19.01.2023 um 14:47 schrieb Cottrell, Allin:
Or more efficiently:
outfile null
# do stuff silently
end outfile
Ah, thanks, Allin, I was looking only for double-dash options in the doc and
On Thu, Jan 19, 2023 at 10:55 AM Sven Schreiber
wrote:
>
> Am 19.01.2023 um 14:47 schrieb Cottrell, Allin:
>
> Or more efficiently:
>
> outfile null
> # do stuff silently
> end outfile
>
> Ah, thanks, Allin, I was looking only for double-dash options in the doc and
> so I overlooked this one.
>
On Thu, Jan 19, 2023 at 11:11 AM Marcin Błażejowski
wrote:
>
> On 19.01.2023 16:48, Cottrell, Allin wrote:
> > My feeling is that neither --quiet nor even --silent as applied to
> > individual commands should suppress warnings; they're about reducing
> > or eliminating regular output.
>
> Ok. But
On 19.01.2023 16:48, Cottrell, Allin wrote:
On Thu, Jan 19, 2023 at 9:52 AM Marcin Błażejowski wrote:
On 19.01.2023 14:47, Cottrell, Allin wrote:
Or more efficiently:
outfile null
# do stuff silently
end outfile
Well, it works of course but for me it is a trick rather than a true
solution.
Am 19.01.2023 um 14:47 schrieb Cottrell, Allin:
Or more efficiently:
outfile null
# do stuff silently
end outfile
Ah, thanks, Allin, I was looking only for double-dash options in the doc
and so I overlooked this one.
Actually, for Marcin's case something like "outfile stderr" might also
be
On Thu, Jan 19, 2023 at 9:52 AM Marcin Błażejowski wrote:
>
> On 19.01.2023 14:47, Cottrell, Allin wrote:
> > Or more efficiently:
> >
> > outfile null
> > # do stuff silently
> > end outfile
>
> Well, it works of course but for me it is a trick rather than a true
> solution. It is because the
On Thu, 19 Jan 2023, Marcin Błażejowski wrote:
On 19.01.2023 10:48, Riccardo (Jack) Lucchetti wrote:
On Thu, 19 Jan 2023, Marcin Błażejowski wrote:
Since the message in fact comes from 'gretl_bfgs.c', there could be a set
option for optimizers for suppressing any warnings/messages.
Does
On 19.01.2023 14:47, Cottrell, Allin wrote:
Or more efficiently:
outfile null
# do stuff silently
end outfile
Well, it works of course but for me it is a trick rather than a true
solution. It is because the message does not come from triggered command
but from underlying apparatus. So from
On Thu, Jan 19, 2023 at 4:19 AM Sven Schreiber
wrote:
>
> Am 19.01.2023 um 09:22 schrieb Marcin Błażejowski:
>
> Hi,
>
> when we perform tobit command with --guiet flag we sometimes get the
> following message: "Warning: couldn't improve criterion (gradient =
> 6.04477e-06)", which per se makes
On 19.01.2023 10:48, Riccardo (Jack) Lucchetti wrote:
On Thu, 19 Jan 2023, Marcin Błażejowski wrote:
Since the message in fact comes from 'gretl_bfgs.c', there could be a
set option for optimizers for suppressing any warnings/messages.
Does the "set warnings" command help?
Nope.
#set
Am 19.01.2023 um 10:48 schrieb Riccardo (Jack) Lucchetti:
On Thu, 19 Jan 2023, Marcin Błażejowski wrote:
Since the message in fact comes from 'gretl_bfgs.c', there could be a
set option for optimizers for suppressing any warnings/messages.
Does the "set warnings" command help?
As per the
On Thu, 19 Jan 2023, Marcin Błażejowski wrote:
Since the message in fact comes from 'gretl_bfgs.c', there could be a set
option for optimizers for suppressing any warnings/messages.
Does the "set warnings" command help?
---
Riccardo
On 19.01.2023 10:19, Sven Schreiber wrote:
Am 19.01.2023 um 09:22 schrieb Marcin Błażejowski:
Hi,
when we perform tobit command with --guiet flag we sometimes get the
following message: "Warning: couldn't improve criterion (gradient =
6.04477e-06)", which /per se/ makes estimation not so
Am 19.01.2023 um 09:22 schrieb Marcin Błażejowski:
Hi,
when we perform tobit command with --guiet flag we sometimes get the
following message: "Warning: couldn't improve criterion (gradient =
6.04477e-06)", which /per se/ makes estimation not so quiet. So, the
question is: shall we leave
20 matches
Mail list logo
