SPSSX Discussion

Casestovars

Classic

List

Threaded

5 messages Options

Tom

Casestovars

Dear List

I have an unknown problem with the Casestovars-Command, which seems actually appropriate in a repeated measure case:

ID	t	Trigger1	Infl1	Trigger2	Infl2	Trigger3	Infl3
1	1	1	-1			1	1
1	2	1	1	1	1	1	1
1	3			1	-1	1	1
1	4			1	1	1	-1
1	5	1	1	1	-1	1	1
2	1	1	1			1	1
2	3	1	1			1	1
2	4					1	1
3	1	1	1	1	1	1	1
3	3	1	1	1	-1	1	1
4	1	1	1

I applied the following syntax in order to have changed this data file above.

SORT CASES BY ID(A).

CASESTOVARS

/ID=ID

/INDEX=t.

I would have expected, that it gets me 4 rows fort he IDs from 1 to 4 and for each of the variables 5 new one’s for every measurement (t), like „Trigger1.1“, „Infl1.1“., „Trigger1.2“, „Infl1.2“...

I get 4 rows, that’s fine, but not all the variables:

ID, Trigger1, Trigger2, Trigger3, Infl1.1, Infl1.2, Infl1.3, Infl1.4, Infl1.5. Infl2.1, Infl2.2, Infl2.3, Infl2.4, Infl2.5, Infl3.1, Infl3.2, Infl3.3, Infl3.4, Infl3.5.

So, where are the other „Trigger“-Variables?

Are the missings a problem?

Thanks for help!

Tom

Maguin, Eugene

Re: Casestovars

I don’t have the correct explanation. But, with respect to this “Are the missings a problem?“, why not test it out by recoding sysmis to some relevant number, NOT declaring that value as user missing and running casestovars again. Let us know what you get. Gene Maguin

From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Balmer, Thomas
Sent: Friday, October 11, 2013 12:36 PM
To: [hidden email]
Subject: Casestovars

Dear List

I have an unknown problem with the Casestovars-Command, which seems actually appropriate in a repeated measure case:

ID	t	Trigger1	Infl1	Trigger2	Infl2	Trigger3	Infl3
1	1	1	-1			1	1
1	2	1	1	1	1	1	1
1	3			1	-1	1	1
1	4			1	1	1	-1
1	5	1	1	1	-1	1	1
2	1	1	1			1	1
2	3	1	1			1	1
2	4					1	1
3	1	1	1	1	1	1	1
3	3	1	1	1	-1	1	1
4	1	1	1

I applied the following syntax in order to have changed this data file above.

SORT CASES BY ID(A).

CASESTOVARS

/ID=ID

/INDEX=t.

I get 4 rows, that’s fine, but not all the variables:

ID, Trigger1, Trigger2, Trigger3, Infl1.1, Infl1.2, Infl1.3, Infl1.4, Infl1.5. Infl2.1, Infl2.2, Infl2.3, Infl2.4, Infl2.5, Infl3.1, Infl3.2, Infl3.3, Infl3.4, Infl3.5.

So, where are the other „Trigger“-Variables?

Are the missings a problem?

Thanks for help!

Tom

David Marso

Re: Casestovars

Administrator

In reply to this post by Tom

Try:
CASESTOVARS
/ID=ID
/INDEX=t / AUTOFIX=NO.

Please reply to the list and not to my personal email.
Those desiring my consulting or training services please feel free to email me.
---
"Nolite dare sanctum canibus neque mittatis margaritas vestras ante porcos ne forte conculcent eas pedibus suis."
Cum es damnatorum possederunt porcos iens ut salire off sanguinum cliff in abyssum?"

David Marso

Re: Casestovars

Administrator

In reply to this post by Maguin, Eugene

FWIW: It has NOTHING to do with missing values. It has EVERYTHING to do with the fact that within the data there is NO variation in the values of trigger1, trigger2, trigger3 hence CASESTOVARS by default treats them as fixed. See the FM for AUTOFIX option (IMHSHO the default AUGHT to be NO rather than YES!!!)

Maguin, Eugene wrote

I don't have the correct explanation. But, with respect to this "Are the missings a problem?", why not test it out by recoding sysmis to some relevant number, NOT declaring that value as user missing and running casestovars again. Let us know what you get. Gene Maguin

From: SPSSX(r) Discussion [mailto:[hidden email]] On Behalf Of Balmer, Thomas
Sent: Friday, October 11, 2013 12:36 PM
To: [hidden email]
Subject: Casestovars

Dear List

I have an unknown problem with the Casestovars-Command, which seems actually appropriate in a repeated measure case:

ID

t

Trigger1

Infl1

Trigger2

Infl2

Trigger3

Infl3

1

1

1

-1

1

1

1

2

1

1

1

1

1

1

1

3

1

-1

1

1

1

4

1

1

1

-1

1

5

1

1

1

-1

1

1

2

1

1

1

1

1

2

3

1

1

1

1

2

4

1

1

3

1

1

1

1

1

1

1

3

3

1

1

1

-1

1

1

4

1

1

1

I applied the following syntax in order to have changed this data file above.

SORT CASES BY ID(A).
CASESTOVARS
/ID=ID
/INDEX=t.

I would have expected, that it gets me 4 rows fort he IDs from 1 to 4 and for each of the variables 5 new one's for every measurement (t), like "Trigger1.1", "Infl1.1"., "Trigger1.2", "Infl1.2"...

I get 4 rows, that's fine, but not all the variables:
ID, Trigger1, Trigger2, Trigger3, Infl1.1, Infl1.2, Infl1.3, Infl1.4, Infl1.5. Infl2.1, Infl2.2, Infl2.3, Infl2.4, Infl2.5, Infl3.1, Infl3.2, Infl3.3, Infl3.4, Infl3.5.
So, where are the other "Trigger"-Variables?
Are the missings a problem?

Thanks for help!
Tom

Tom

AW: Casestovars

Thanks, David, that works fine!

Tom

David Marso wrote
Try:
CASESTOVARS
/ID=ID
/INDEX=t / AUTOFIX=NO.

FWIW: It has NOTHING to do with missing values. It has EVERYTHING to do with the fact that within the data there is NO variation in the values of trigger1, trigger2, trigger3 hence CASESTOVARS by default treats them as fixed. See the FM for AUTOFIX option (IMHSHO the default AUGHT to be NO rather than YES!!!)

Maguin, Eugene wrote
> I don't have the correct explanation. But, with respect to this "Are
> the missings a problem?", why not test it out by recoding sysmis to
> some relevant number, NOT declaring that value as user missing and
> running casestovars again. Let us know what you get. Gene Maguin
>
>
> From: SPSSX(r) Discussion [mailto:

> SPSSX-L@.UGA

> ] On Behalf Of Balmer, Thomas
> Sent: Friday, October 11, 2013 12:36 PM
> To:

> SPSSX-L@.UGA

> Subject: Casestovars
>
> Dear List
>
> I have an unknown problem with the Casestovars-Command, which seems
> actually appropriate in a repeated measure case:
>
> ID
>
> t
>
> Trigger1
>
> Infl1
>
> Trigger2
>
> Infl2
>
> Trigger3
>
> Infl3
>
> 1
>
> 1
>
> 1
>
> -1
>
> 1
>
> 1
>
> 1
>
> 2
>
> 1
>
> 1
>
> 1
>
> 1
>
> 1
>
> 1
>
> 1
>
> 3
>
> 1
>
> -1
>
> 1
>
> 1
>
> 1
>
> 4
>
> 1
>
> 1
>
> 1
>
> -1
>
> 1
>
> 5
>
> 1
>
> 1
>
> 1
>
> -1
>
> 1
>
> 1
>
> 2
>
> 1
>
> 1
>
> 1
>
> 1
>
> 1
>
> 2
>
> 3
>
> 1
>
> 1
>
> 1
>
> 1
>
> 2
>
> 4
>
> 1
>
> 1
>
> 3
>
> 1
>
> 1
>
> 1
>
> 1
>
> 1
>
> 1
>
> 1
>
> 3
>
> 3
>
> 1
>
> 1
>
> 1
>
> -1
>
> 1
>
> 1
>
> 4
>
> 1
>
> 1
>
> 1
>
>
> I applied the following syntax in order to have changed this data file
> above.
>
> SORT CASES BY ID(A).
> CASESTOVARS
> /ID=ID
> /INDEX=t.
>
> I would have expected, that it gets me 4 rows fort he IDs from 1 to 4
> and for each of the variables 5 new one's for every measurement (t),
> like "Trigger1.1", "Infl1.1"., "Trigger1.2", "Infl1.2"...
>
> I get 4 rows, that's fine, but not all the variables:
> ID, Trigger1, Trigger2, Trigger3, Infl1.1, Infl1.2, Infl1.3,
> Infl1.4, Infl1.5. Infl2.1, Infl2.2, Infl2.3, Infl2.4, Infl2.5,
> Infl3.1, Infl3.2, Infl3.3, Infl3.4, Infl3.5.
> So, where are the other "Trigger"-Variables?
> Are the missings a problem?
>
> Thanks for help!
> Tom

-----
Please reply to the list and not to my personal email.
Those desiring my consulting or training services please feel free to email me.
---
"Nolite dare sanctum canibus neque mittatis margaritas vestras ante porcos ne forte conculcent eas pedibus suis."
Cum es damnatorum possederunt porcos iens ut salire off sanguinum cliff in abyssum?"
--
View this message in context: http://spssx-discussion.1045642.n5.nabble.com/Casestovars-tp5722501p5722505.html
Sent from the SPSSX Discussion mailing list archive at Nabble.com.

=====================
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

=====================
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