You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for developing these tools, which are incredibly beneficial for analyzing cell-cell communication. As I was examining the regulatory heatmap, I noticed that some ligands, such as EFNA1, target only a few genes. Despite that, EFNA1's rank seems more optimized than CDH1, which targets a much larger number of genes. This observation puzzled me, so I decided to investigate how ranks are calculated, which led me to the predict_ligand_activities function. Upon reviewing the function's code on rdrr.io, I found that get_single_ligand_importances plays a crucial role within it. In turn, the critical function for that one is evaluate_target_prediction. Yet, it seems this isn't the final function responsible for calculating metrics like AUPR, etc. My search ultimately led me to focus on the evaluate_target_prediction_strict function, which is nested within evaluate_target_prediction. However, I haven't been able to locate the detailed code for this function, and my attempts to Google it turned up no useful results. I’m wondering if evaluate_target_prediction_strict is indeed the key function for calculating metrics such as "auroc", "aupr", "aupr_corrected", and "pearson", and if so, where could I access these detailed codes?
The text was updated successfully, but these errors were encountered:
Thank you for your enquiry.
To compute the prediction values, the function evaluate_target_prediction_strict calls classification_evaluation_continuous_pred using the response and prediction vectors as inputs.
Inside classification_evaluation_continuous_pred you will find all the functions that are called to compute the AUPR and correlation scores. In this way, you should be able to reconstruct all the steps and inputs used to prioritize EFNA1 and CDH1.
Thank you for developing these tools, which are incredibly beneficial for analyzing cell-cell communication. As I was examining the regulatory heatmap, I noticed that some ligands, such as EFNA1, target only a few genes. Despite that, EFNA1's rank seems more optimized than CDH1, which targets a much larger number of genes. This observation puzzled me, so I decided to investigate how ranks are calculated, which led me to the
![test_heatmap](https://private-user-images.githubusercontent.com/39393136/324266003-d2fb1bd8-34ca-4d1a-90fb-3941cd814e2c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjM5ODQ0MTcsIm5iZiI6MTcyMzk4NDExNywicGF0aCI6Ii8zOTM5MzEzNi8zMjQyNjYwMDMtZDJmYjFiZDgtMzRjYS00ZDFhLTkwZmItMzk0MWNkODE0ZTJjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODE4VDEyMjgzN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWZmOWRmOGE2MGMyOGIxZjVmZGVlODYxMTY0YTZkMTk1NTc4MjMzZDhkYjBjZDdjMzcwNWZlNzcwNzJjNWJlYzcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.mpINuJ5ZQgTfWQsaGwsxWjm6AwPw59EKjofD2kPzPww)
predict_ligand_activities
function. Upon reviewing the function's code on rdrr.io, I found thatget_single_ligand_importances
plays a crucial role within it. In turn, the critical function for that one isevaluate_target_prediction
. Yet, it seems this isn't the final function responsible for calculating metrics like AUPR, etc. My search ultimately led me to focus on theevaluate_target_prediction_strict
function, which is nested withinevaluate_target_prediction
. However, I haven't been able to locate the detailed code for this function, and my attempts to Google it turned up no useful results. I’m wondering ifevaluate_target_prediction_strict
is indeed the key function for calculating metrics such as "auroc", "aupr", "aupr_corrected", and "pearson", and if so, where could I access these detailed codes?The text was updated successfully, but these errors were encountered: