crisprVerse/crisprScore

MacOS M1 chip

Jfortin1 opened this issue · 1 comments

From https://github.com/Jfortin1/crisprScore/issues/8:

Hello, received an error in RStudio when trying to use getAzimuthScores()

Error in checkForRemoteErrors(lapply(cl, recvResult)) :
one node produced an error: /Users/nkuperwasser/Library/Caches/org.R-project.R/R/basilisk/1.8.0/crisprScore/1.0.0/azimuth_basilisk/lib/libpython2.7.dylib - dlopen(/Users/nkuperwasser/Library/Caches/org.R-project.R/R/basilisk/1.8.0/crisprScore/1.0.0/azimuth_basilisk/lib/libpython2.7.dylib, 0x000A): tried: '/Users/nkuperwasser/Library/Caches/org.R-project.R/R/basilisk/1.8.0/crisprScore/1.0.0/azimuth_basilisk/lib/libpython2.7.dylib' (mach-o file, but is an incompatible architecture (have (x86_64), need (arm64e)))

I am not a coding expert by a long shot, but was wondering if this is perhaps due to the M1 chip?

Thanks

NK

Hi @nkuperwasser, yes, the M1 chip is causing the problem, see the issue here from the basilisk dependency: Bioconductor/basilisk#18

@nkuperwasser The issue should be fixed now, see Bioconductor/basilisk#18