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

Issue with drugPerturbationSig function in PharmacoGx package #161

Open
pijush1285 opened this issue Apr 29, 2024 · 0 comments
Open

Issue with drugPerturbationSig function in PharmacoGx package #161

pijush1285 opened this issue Apr 29, 2024 · 0 comments
Assignees

Comments

@pijush1285
Copy link

I am writing to bring to your attention an issue I encountered while using the drugPerturbationSig function in the PharmacoGx package.
I recently attempted to use the function with the following code:

GDSC <- downloadPSet("GDSC_2020(v2-8.2)")
drug.perturbation <- drugPerturbationSig(GDSC, mDataType="rna",verbose=FALSE)

However, upon running this code, I encountered the following error:
Error: subscript contains invalid names

Despite setting the verbose parameter to FALSE, I was unable to gather additional information about the nature of the error. This has made it challenging for me to diagnose and resolve the issue.
I have ensured that the input data provided to the function (GDSC) is correctly formatted and contains the necessary information. However, it seems that there may be an issue with how the function processes the data or handles certain operations internally.
Could you please provide some guidance on how to troubleshoot this issue or if there are any known issues with the drugPerturbationSig function in the PharmacoGx package? Additionally, if there are any updates or patches available that address this issue, I would greatly appreciate it if you could share them with me.

Thank you for your attention to this matter. I look forward to your response and appreciate your assistance in resolving this issue.

Best regards,
Pijush Das

@jjjermiah jjjermiah self-assigned this May 10, 2024
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