CTABLES DOES NOT SUPPORT DEFAULT SUB-COMMAND FOR SPLIT FILES
Locked
CTABLES DOES NOT SUPPORT DEFAULT SUB-COMMAND FOR SPLIT FILES
 
|
Thanks to Gene who picked up the problem of using SPLIT FILES with CTABLES as being due to the
fact that CTABLES DOES NOT support the DEFAULT subcommand [Layered] for SPLIT FILES. Hence, to generate tables for each SPLIT FILE Group in the data, it is necessary to specify: SPLIT FILES SEPARATE by GROUP. The CTABLES Manual does not address this issue â and the error message at run time is missleading. It is a little weird that a DEFAULT value of a command is not supported!!! Perhaps SPSS can amend the Manuals and onscreen HELP to make this matter explicit. Cheers Peter ===================== To manage your subscription to SPSSX-L, send a message to [hidden email] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD |
Re: CTABLES DOES NOT SUPPORT DEFAULT SUB-COMMAND FOR SPLIT FILES
|
|
Hi Peter, Although the documentation on this isn't what it could be, the functioning of the software is as designed, and the error message seems to point accurately to the issue. It reads: "The SPLIT FILE option LAYERED is ignored in Custom tables. To compare groups, use the split variables as the outermost row variables in the table." SPLIT FILE has two options or modes, LAYERED and SEPARATE. LAYERED is the default. It results in the tables for all splits being combined in a single large table, with the splits occupying the first position of rows in the table structure. The SEPARATE option puts the results for each split into a separate table. The design of CTABLES (Custom Tables) includes the functionality offered by SPLIT FILE with the default LAYERED. Not all procedures work with SPLIT FILE. AGGREGATE, for example, ignores SPLIT FILE, as do all of the procedures in the Categories module. I certainly agree that the documentation could be clearer about this (the Custom Tables manual indeed doesn't mention this at all). I've opened a support case and we'll file a bug report to get improvements made on the documentation. Our apologies for the confusion. David Nichols SPSS, an IBM Company
Thanks to Gene who picked up the problem of using SPLIT FILES with CTABLES as being due to the fact that CTABLES DOES NOT support the DEFAULT subcommand [Layered] for SPLIT FILES. Hence, to generate tables for each SPLIT FILE Group in the data, it is necessary to specify: SPLIT FILES SEPARATE by GROUP. The CTABLES Manual does not address this issue — and the error message at run time is missleading. It is a little weird that a DEFAULT value of a command is not supported!!! Perhaps SPSS can amend the Manuals and onscreen HELP to make this matter explicit. Cheers Peter ===================== To manage your subscription to SPSSX-L, send a message to [hidden email] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD |
Re: CTABLES DOES NOT SUPPORT DEFAULT SUB-COMMAND FOR SPLIT FILES
|
Perhaps part of the fix would be to have procedures that support only
SEPARATE or ignore SPLIT FILES completely, still detect that split
files is turned on and which option was chosen and the put a message in
the listing file.
Art Kendall Social Research Consultants On 2/8/2010 12:24 PM, SPSS Support wrote: ===================== To manage your subscription to SPSSX-L, send a message to [hidden email] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD
Art Kendall
Social Research Consultants |
Re: CTABLES DOES NOT SUPPORT DEFAULT SUB-COMMAND FOR SPLIT FILES
|
|
Bear in mind that there is a reason that CTABLES does not support SPLIT FILE LAYERED: That functionality is redundant with the layer capabilities of CTABLES. Besides adding no useful functionality, figuring out what it should do if both splitting and the table has layers would be a challenge. Note that the output already includes this warning: The SPLIT FILE option LAYERED is ignored in Custom tables. To compare groups, use the split variables as the outermost row variables in the table. Jon Peck SPSS, an IBM Company [hidden email] 312-651-3435
Perhaps part of the fix would be to have procedures that support only SEPARATE or ignore SPLIT FILES completely, still detect that split files is turned on and which option was chosen and the put a message in the listing file. Art Kendall Social Research Consultants On 2/8/2010 12:24 PM, SPSS Support wrote: Hi Peter, Although the documentation on this isn't what it could be, the functioning of the software is as designed, and the error message seems to point accurately to the issue. It reads: "The SPLIT FILE option LAYERED is ignored in Custom tables. To compare groups, use the split variables as the outermost row variables in the table." SPLIT FILE has two options or modes, LAYERED and SEPARATE. LAYERED is the default. It results in the tables for all splits being combined in a single large table, with the splits occupying the first position of rows in the table structure. The SEPARATE option puts the results for each split into a separate table. The design of CTABLES (Custom Tables) includes the functionality offered by SPLIT FILE with the default LAYERED. Not all procedures work with SPLIT FILE. AGGREGATE, for example, ignores SPLIT FILE, as do all of the procedures in the Categories module. I certainly agree that the documentation could be clearer about this (the Custom Tables manual indeed doesn't mention this at all). I've opened a support case and we'll file a bug report to get improvements made on the documentation. Our apologies for the confusion. David Nichols SPSS, an IBM Company
Thanks to Gene who picked up the problem of using SPLIT FILES with CTABLES as being due to the fact that CTABLES DOES NOT support the DEFAULT subcommand [Layered] for SPLIT FILES. Hence, to generate tables for each SPLIT FILE Group in the data, it is necessary to specify: SPLIT FILES SEPARATE by GROUP. The CTABLES Manual does not address this issue — and the error message at run time is missleading. It is a little weird that a DEFAULT value of a command is not supported!!! Perhaps SPSS can amend the Manuals and onscreen HELP to make this matter explicit. Cheers Peter ===================== To manage your subscription to SPSSX-L, send a message to LISTSERV@... (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD ===================== To manage your subscription to SPSSX-L, send a message to [hidden email] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD |
Re: CTABLES DOES NOT SUPPORT DEFAULT SUB-COMMAND FOR SPLIT FILES
|
|
Re: CTABLES DOES NOT SUPPORT DEFAULT SUB-COMMAND FOR SPLIT FILES
|
|
In reply to this post by Jon K Peck
It makes sense that CTABLES and AGGREGATE would ignore SPLIT FILES
since they have similar capabilities.
However, I'm glad to see that CTABLES does have the message. I wonder if the OP saw that message. Do other procedures that ignore SPLIT FILE such as AGGREGATE and graphs have similar messages? Art On 2/8/2010 1:55 PM, Jon K Peck wrote: ===================== To manage your subscription to SPSSX-L, send a message to [hidden email] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD
Art Kendall
Social Research Consultants |
Re: CTABLES DOES NOT SUPPORT DEFAULT SUB-COMMAND FOR SPLIT FILES
|
|
Yes, there is a message, but it is OPAQUE to anyone who is not an experienced CTABLES user — it would be useful also to indicate that if the user is wants separate tables for each group, then the SPLIT FILE command must include the SEPARATE subcommand.
Prof Peter Cuttance Director Research Australia Development and Innovation Institute (radii.org) Ph. +613 9534 2934 Mob. +61 428 990 904 Fax. +613 8640 0741 Suite 71 197 Canterbury Road St Kilda West Victoria AUSTRALIA 3182 On 09/02/2010, at 11:23 PM, Art Kendall wrote:
|
Re: CTABLES DOES NOT SUPPORT DEFAULT SUB-COMMAND FOR SPLIT FILES
|
|
In reply to this post by Peter Cuttance
In answer to Art, AGGREGATE and the Categories procedures do indeed produce warning messages telling you that SPLIT FILE has been ignored. Peter, two requests have been filed with SPSS Development, one to have the functioning of CTABLES with regard to SPLIT FILE included in the Custom Tables manual, and the other to consider changes to the warning message. David Nichols SPSS, an IBM Company
Yes, there is a message, but it is OPAQUE to anyone who is not an experienced CTABLES user — it would be useful also to indicate that if the user is wants separate tables for each group, then the SPLIT FILE command must include the SEPARATE subcommand. Prof Peter Cuttance Director Research Australia Development and Innovation Institute (radii.org) Ph. +613 9534 2934 Mob. +61 428 990 904 Fax. +613 8640 0741 Suite 71 197 Canterbury Road St Kilda West Victoria AUSTRALIA 3182 On 09/02/2010, at 11:23 PM, Art Kendall wrote: It makes sense that CTABLES and AGGREGATE would ignore SPLIT FILES since they have similar capabilities. However, I'm glad to see that CTABLES does have the message. I wonder if the OP saw that message. Do other procedures that ignore SPLIT FILE such as AGGREGATE and graphs have similar messages? Art On 2/8/2010 1:55 PM, Jon K Peck wrote: Bear in mind that there is a reason that CTABLES does not support SPLIT FILE LAYERED: That functionality is redundant with the layer capabilities of CTABLES. Besides adding no useful functionality, figuring out what it should do if both splitting and the table has layers would be a challenge. Note that the output already includes this warning: The SPLIT FILE option LAYERED is ignored in Custom tables. To compare groups, use the split variables as the outermost row variables in the table. Jon Peck SPSS, an IBM Company peck@... 312-651-3435
Perhaps part of the fix would be to have procedures that support only SEPARATE or ignore SPLIT FILES completely, still detect that split files is turned on and which option was chosen and the put a message in the listing file. Art Kendall Social Research Consultants On 2/8/2010 12:24 PM, SPSS Support wrote: Hi Peter, Although the documentation on this isn't what it could be, the functioning of the software is as designed, and the error message seems to point accurately to the issue. It reads: "The SPLIT FILE option LAYERED is ignored in Custom tables. To compare groups, use the split variables as the outermost row variables in the table." SPLIT FILE has two options or modes, LAYERED and SEPARATE. LAYERED is the default. It results in the tables for all splits being combined in a single large table, with the splits occupying the first position of rows in the table structure. The SEPARATE option puts the results for each split into a separate table. The design of CTABLES (Custom Tables) includes the functionality offered by SPLIT FILE with the default LAYERED. Not all procedures work with SPLIT FILE. AGGREGATE, for example, ignores SPLIT FILE, as do all of the procedures in the Categories module. I certainly agree that the documentation could be clearer about this (the Custom Tables manual indeed doesn't mention this at all). I've opened a support case and we'll file a bug report to get improvements made on the documentation. Our apologies for the confusion. David Nichols SPSS, an IBM Company
Thanks to Gene who picked up the problem of using SPLIT FILES with CTABLES as being due to the fact that CTABLES DOES NOT support the DEFAULT subcommand [Layered] for SPLIT FILES. Hence, to generate tables for each SPLIT FILE Group in the data, it is necessary to specify: SPLIT FILES SEPARATE by GROUP. The CTABLES Manual does not address this issue — and the error message at run time is missleading. It is a little weird that a DEFAULT value of a command is not supported!!! Perhaps SPSS can amend the Manuals and onscreen HELP to make this matter explicit. Cheers Peter ===================== To manage your subscription to SPSSX-L, send a message to LISTSERV@... (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD ===================== To manage your subscription to SPSSX-L, send a message to LISTSERV@... (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD ===================== To manage your subscription to SPSSX-L, send a message to LISTSERV@... (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD |
«
Return to SPSSX Discussion
|
1 view|%1 views
| Free forum by Nabble | Edit this page |