Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interpretation of values #21

Open
evgkra opened this issue Jan 8, 2021 · 8 comments
Open

Interpretation of values #21

evgkra opened this issue Jan 8, 2021 · 8 comments

Comments

@evgkra
Copy link

evgkra commented Jan 8, 2021

Hello, thank you for your package!
I cannot find any information on how to interpret the values that one recieves after causal inference.
Is it correct to intuitively assume that the higher the value, the higher the correlation between variables? Is there a maximum value?

@sshimizu2006
Copy link
Collaborator

Hi, if you are talking about the values in the adjacency matrix, they are direct causal effects. Higher the value, higher the direct causal effect.

@evgkra
Copy link
Author

evgkra commented Jan 9, 2021

Thank you!
I have one more question, is there any good way of implementing deltas in the algorithm? In AMOS for example, one has to set causal effects from T1 to T2 and delta to T2, to 1. Here I can only think of adding prior knowledge abouth paths but there is no way of setting the value to 1 from what I can see

@sshimizu2006
Copy link
Collaborator

sshimizu2006 commented Jan 9, 2021

Currently, such a way of setting coefficients to be some specific values is not implemented.

@evgkra
Copy link
Author

evgkra commented Jan 10, 2021

How would you propose to work with delta variables, or would you say that the algorithm should not be used for such?

@sshimizu2006
Copy link
Collaborator

Though I'm not quite sure what delta refers to, the coefficients from error terms to the corresponding observed variables are automatically set to 1.

@evgkra
Copy link
Author

evgkra commented Jan 11, 2021

Deltas refer to the difference between a variable measured at time-point 1 and time-point 2

@sshimizu2006
Copy link
Collaborator

I see. The current package would not be able to do such an analysis.

@evgkra
Copy link
Author

evgkra commented Jan 11, 2021

Thank you very much for getting back to me so quickly!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants