On Sat, Nov 16, 2019 at 12:27 PM Alan Mead wrote:
>
> On 11/16/2019 1:14 PM, Ben Pfaff wrote:
>
> too_many_errors = true;
> if (m->severity == MSG_S_WARNING)
> submit_note (xasprintf (_("Warnings (%d) exceed limit (%d).
> Syntax processing will be halted."),
>
On 11/16/2019 1:14 PM, Ben Pfaff wrote:
>> too_many_errors = true;
>> if (m->severity == MSG_S_WARNING)
>> submit_note (xasprintf (_("Warnings (%d) exceed limit (%d).
>> Syntax processing will be halted."),
>> n_msgs, max_msgs));
On 11/16/2019 1:14 PM, Ben Pfaff wrote:
> Recent SPSS documentation specifies two ways that exceeding MXWARNS
> can be handled. In batch mode, it does what PSPP does here, stopping
> processing if MXWARNS is exceeded. In interactive mode, it just
> suppresses warnings beyond the warning limit. This
I'm sorry for missing Alan's point.
I wasn't aware of the difference between notes and warnings. But summary
notes ad the end of procedures seem a perfect solution to me.
Thanks
frans
On 11/16/19 8:00 PM, Ben Pfaff wrote:
In some of these cases, I think that PSPP could issue fewer warnings.
F
On Sat, Nov 16, 2019 at 10:40 AM Alan Mead wrote:
>
> On 11/16/2019 11:31 AM, Frans Houweling wrote:
>
> Yes, but for errors we have MXERRS. I personally would like PSPP to halt on
> the first error, but never on a warning.
> Greetings
> frans
>
>
> Sorry, that was my point. It's really unhelpful
In some of these cases, I think that PSPP could issue fewer warnings.
For example, when GET DATA finds bad data, it is probably useful to
issue one warning, but it might not be valuable to issue 100 warnings.
Perhaps it should simply summarize ("found 325 additional invalid
observations") or the de
On 11/16/2019 11:31 AM, Frans Houweling wrote:
> Yes, but for errors we have MXERRS. I personally would like PSPP to
> halt on the first error, but never on a warning.
> Greetings
> frans
Sorry, that was my point. It's really unhelpful to stop on warnings (of
any number). MXWARNS is helpful to sto
Yes, but for errors we have MXERRS. I personally would like PSPP to halt
on the first error, but never on a warning.
Greetings
frans
On 11/16/19 5:42 PM, Alan Mead wrote:
This is probably known, but SPSS will stop on some errors. If the GET
DATA command fails, it will stop at the first routine
This is probably known, but SPSS will stop on some errors. If the GET
DATA command fails, it will stop at the first routine that requires a
dataset. I think it will also stop on a duplicate key when merging files
by a condition.
I don't think it stops on errors like divide-by-zero (i.e., where I'v
Hi Ben,
GET DATA on csv files is the main source, like when missing values are
coded "NA" or ":".
Plus I do make the ehm occasional mistake - but as what I do wrong in
the first record I do wrong in all the following records too, I always
reach MXWARNS. I can see some justification for halting
I'm a little surprised you're receiving so many warnings. Is that a problem
of its own? What's the underlying cause?
On Fri, Nov 15, 2019, 12:36 PM Frans Houweling wrote:
> Correction: syntax processing does stop - only not in the first
> procedure. Bad!
> frans
>
> On 11/15/19 8:47 PM, Frans Ho
Correction: syntax processing does stop - only not in the first
procedure. Bad!
frans
On 11/15/19 8:47 PM, Frans Houweling wrote:
Hi,
I often see this message
"note: Warnings (n+1) exceed limit (n). Syntax processing will be
halted."
Luckily, syntax processing seems to go on anyway. I thin
12 matches
Mail list logo
