Derek
Derek
@PidgeyBE Would you happen to have a wheel for aarch64 + Python 3.8? I'm trying to make this work natively on a mac M1 but I haven't been able to...
@PidgeyBE WOW thank you so much! Ahah best Christmas gift ever! I will test it later tonight after all the Christmas activities. Merry Christmas!
@Johannes-Lange I feel your pain. I spent most of last night trying to compile Pytorch for 3.8 (there's only a 3.9 beta wheel) and I couldn't get it to work...
Both 3.8 and 3.9 wheels gets this issue `ERROR: py_spy-0.3.3-cp38-cp38-linux_aarch64.whl is not a supported wheel on this platform.` :(
Edit: Works now! I had to run `pip3 install --no-dependencies --force ray-1.2.0.dev0-cp39-cp39-macosx_11_0_arm64.whl` for 3.9 but decided to use the 3.8 for tensorflow reasons (I used the same renaming trick). I...
@Johannes-Lange I have issues too loading ray but with a different issue `OSError: dlopen(/Users/USERNNAME/miniforge3/envs/ENVNNAME/lib/python3.8/site-packages/ray/_raylet.so, 10): no suitable image found.` I'm running python 3.8 with conda, tensorflow + pytorch (nightly build).
Thank you for the prompt reply! I am current using Ubuntu 20.04, conda + python 3.8 environment, 16GB of RAM, 512 GB SSD, and an older i7-4700. I run all...
After some trial and error, a major symptom is that the memory leaks when explain_level=2. Every other type of explain_level works fine so it might be the SHAP portion that...
@underlines: Can you go into more details how you got `gpt4x-alpaca` to work? I tried following your suggestion and renamed both the folder and .pt file to `gpt4x-alpaca`. But when...
@3dluvr Thanks! A mix of both your advice and @underlines worked for me! I was missing `--model_type LLaMA` flag. After doing a `git pull`, renaming the *-cuda.pt file to just...