Skip to content
This repository has been archived by the owner on Jan 24, 2024. It is now read-only.

explanation of the df from subsetCommunication #750

Open
amberqiong opened this issue Jan 19, 2024 · 4 comments
Open

explanation of the df from subsetCommunication #750

amberqiong opened this issue Jan 19, 2024 · 4 comments

Comments

@amberqiong
Copy link

amberqiong commented Jan 19, 2024

Hello,

Thanks for the wonderful cellchat tool! I have some questions regarding regarding the explanation of the dataframe from subsetCommunication(). Does the 'prob' column represent the communication probability (strength)? Can I directly compare this value between two datasets to assess if the signaling is up-regulated or down-regulated?

lipo.control.signaling.df=subsetCommunication(object.list[[1]],sources.use = c(1:3),targets.use = c(1:3)) lipo.PA.signaling.df=subsetCommunication(object.list[[2]],sources.use = c(1:3),targets.use = c(1:3))

My goal is to identify the list of the differential signaling, and then comparing to other dataset (find common changed pathways).

Thanks in advance.

@amberqiong amberqiong changed the title how to get the list of the differential signalings from the comparison explanation of the df from subsetCommunication Jan 19, 2024
@sqjin
Copy link
Owner

sqjin commented Jan 22, 2024

@amberqiong Yes, you can compare the value between two datasets. the 'prob' column represent the communication probability (strength)

@amberqiong
Copy link
Author

Thank you for the clarification!

@amberqiong Yes, you can compare the value between two datasets. the 'prob' column represent the communication probability (strength)

@amberqiong
Copy link
Author

Is there a defined threshold for the 'prob' column that signifies strong communication?

@sqjin
Copy link
Owner

sqjin commented Jan 23, 2024

@amberqiong no threshold is for prob. But high values indicate strong communicaitons

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

No branches or pull requests

2 participants