Skip to content

Commit 57a3ea9

Browse files
19wolflstein
authored andcommitted
Update 'ldm' env to 'invokeai' in troubleshooting steps
1 parent a3a50bb commit 57a3ea9

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

docs/installation/INSTALL_MAC.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -178,7 +178,7 @@ conda install \
178178
pytorch \
179179
torchvision \
180180
-c pytorch-nightly \
181-
-n ldm
181+
-n invokeai
182182
```
183183

184184
If it takes forever to run `conda env create -f environment-mac.yml`, try this:
@@ -206,7 +206,7 @@ conda update \
206206

207207
There are several causes of these errors:
208208

209-
1. Did you remember to `conda activate ldm`? If your terminal prompt begins with
209+
1. Did you remember to `conda activate invokeai`? If your terminal prompt begins with
210210
"(invokeai)" then you activated it. If it begins with "(base)" or something else
211211
you haven't.
212212

@@ -221,17 +221,17 @@ There are several causes of these errors:
221221

222222
```bash
223223
conda deactivate
224-
conda env remove -n ldm
224+
conda env remove -n invokeai
225225
conda env create -f environment-mac.yml
226226
```
227227

228-
4. If you have activated the ldm virtual environment and tried rebuilding it,
228+
4. If you have activated the invokeai virtual environment and tried rebuilding it,
229229
maybe the problem could be that I have something installed that you don't and
230230
you'll just need to manually install it. Make sure you activate the virtual
231231
environment so it installs there instead of globally.
232232

233233
```bash
234-
conda activate ldm
234+
conda activate invokeai
235235
pip install <package name>
236236
```
237237

@@ -290,11 +290,11 @@ output of `python3 -V` and `python -V`.
290290

291291
```bash
292292
(invokeai) % which python
293-
/Users/name/miniforge3/envs/ldm/bin/python
293+
/Users/name/miniforge3/envs/invokeai/bin/python
294294
```
295295

296296
The above is what you'll see if you have miniforge and correctly activated the
297-
ldm environment, while usingd the standalone setup instructions above.
297+
invokeai environment, while usingd the standalone setup instructions above.
298298
299299
If you otherwise installed via pyenv, you will get this result:
300300
@@ -474,7 +474,7 @@ this issue too. I should probably test it.
474474
### "view size is not compatible with input tensor's size and stride"
475475
476476
```bash
477-
File "/opt/anaconda3/envs/ldm/lib/python3.10/site-packages/torch/nn/functional.py", line 2511, in layer_norm
477+
File "/opt/anaconda3/envs/invokeai/lib/python3.10/site-packages/torch/nn/functional.py", line 2511, in layer_norm
478478
return torch.layer_norm(input, normalized_shape, weight, bias, eps, torch.backends.cudnn.enabled)
479479
RuntimeError: view size is not compatible with input tensor's size and stride (at least one dimension spans across two contiguous subspaces). Use .reshape(...) instead.
480480
```
@@ -510,7 +510,7 @@ Generating: 0%| |
510510
loc("mps_add"("(mpsFileLoc): /AppleInternal/Library/BuildRoots/20d6c351-ee94-11ec-bcaf-7247572f23b4/Library/Caches/com.apple.xbs/Sources/MetalPerformanceShadersGraph/mpsgraph/MetalPerformanceShadersGraph/Core/Files/MPSGraphUtilities.mm":219:0)): error: input types 'tensor<2x1280xf32>' and 'tensor<*xf16>' are not broadcast compatible
511511
LLVM ERROR: Failed to infer result type(s).
512512
Abort trap: 6
513-
/Users/[...]/opt/anaconda3/envs/ldm/lib/python3.9/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 1 leaked semaphore objects to clean up at shutdown
513+
/Users/[...]/opt/anaconda3/envs/invokeai/lib/python3.9/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 1 leaked semaphore objects to clean up at shutdown
514514
warnings.warn('resource_tracker: There appear to be %d '
515515
```
516516

0 commit comments

Comments
 (0)