-
Notifications
You must be signed in to change notification settings - Fork 3
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
Error Retrieving Cell Line Datasets from PharmacoGx - Build Blocked #284
Comments
PharmacoGx data is no longer accessible. Looks like it has been down for at least 3 weeks. Someone already created an issue on their github but there is no response yet. Data: https://www.pmgenomics.ca/bhklab/sites/default/files/downloads/ Error:
|
Have you not run the build in the past few weeks? |
Last time I ran the full build was on the 15th/16th. I've done some partial ones since, but mostly been working on the sample/drug mapping update. Looks like their whole site is down now too. https://pharmacodb.pmgenomics.ca/ |
OK, Can you try to salvage the files to assemble a build? I'll check in with the PI. We might need to rewrite everything if we can't figure it out. |
Yes, will do |
Developer from BHKLab here, apologies for this. Is this an R package that depends on PharmacoGx? The fix should be pushed to Bioconductor's release branch but may take some time to reflect when installing. temporarily we have a tool for just downloading datasets i will post updates as i have them. Once again, apologies! |
Not an R package - a larger workflow. I created an issue (#287) to move to orcestra-downloader when we have the chance. Will close this one once the new build is up on Bioconductor! Thanks. |
Thanks @jjjermiah! Looks like this is still unavailable. Do you have any estimate on when this will be released? |
https://www.bioconductor.org/packages/release/bioc/html/PharmacoGx.html |
Great, this immediate issue appears to be resolved. I'll let you know if any other issues arise |
In build/broad_sanger/03-createDrugFile.R, I am receiving the following error. I will look into this. It might just be a version / dependency issue.
The text was updated successfully, but these errors were encountered: