活动介绍

(base) C:\Users\XC>pip install dlib==19.7.0 Collecting dlib==19.7.0 Using cached dlib-19.7.0.tar.gz (4.0 MB) Preparing metadata (setup.py) ... done Building wheels for collected packages: dlib DEPRECATION: Building 'dlib' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'dlib'. Discussion can be found at https://github.com/pypa/pip/issues/6334 Building wheel for dlib (setup.py) ... error error: subprocess-exited-with-error × python setup.py bdist_wheel did not run successfully. │ exit code: 1 ╰─> [76 lines of output] C:\Users\XC\AppData\Local\Temp\pip-install-t9ptlaxa\dlib_04710a2f6a364c8391ea5e7017c308fb\setup.py:360: SyntaxWarning: invalid escape sequence '\(' major = re.findall("set\(CPACK_PACKAGE_VERSION_MAJOR.*\"(.*)\"", open('dlib/CMakeLists.txt').read())[0] C:\Users\XC\AppData\Local\Temp\pip-install-t9ptlaxa\dlib_04710a2f6a364c8391ea5e7017c308fb\setup.py:361: SyntaxWarning: invalid escape sequence '\(' minor = re.findall("set\(CPACK_PACKAGE_VERSION_MINOR.*\"(.*)\"", open('dlib/CMakeLists.txt').read())[0] C:\Users\XC\AppData\Local\Temp\pip-install-t9ptlaxa\dlib_04710a2f6a364c8391ea5e7017c308fb\setup.py:362: SyntaxWarning: invalid escape sequence '\(' patch = re.findall("set\(CPACK_PACKAGE_VERSION_PATCH.*\"(.*)\"", open('dlib/CMakeLists.txt').read())[0] C:\Users\XC\AppData\Local\Temp\pip-install-t9ptlaxa\dlib_04710a2f6a364c8391ea5e7017c308fb\setup.py:72: DeprecationWarning: Use shutil.which instead of find_executable _cmake_path = find_executable("cmake") running bdist_wheel running build Detected Python architecture: 64bit Detected platform: win32 Configuring cmake ... D:\Anaconda\Lib\subprocess.py:1029: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used self.stdout = io.open(c2pread, 'rb', bufsize) Traceback (most recent call last): File "<string>", line 2, in <module> exec(compile(''' ~~~~^^^^^^^^^^^^ # This is <pip-setuptools-caller> -- a caller that pip uses to run setup.py ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ...<32 lines>... exec(compile(setup_py_code, filename, "exec")) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ''' % ('C:\\Users\\XC\\AppData\\Local\\Temp\\pip-install-t9ptlaxa\\dlib_04710a2f6a364c8391ea5e7017c308fb\\setup.py',), "<pip-setuptools-caller>", "exec")) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "<pip-setuptools-caller>", line 35, in <module> File "C:\Users\XC\AppData\Local\Temp\pip-install-t9ptlaxa\dlib_04710a2f6a364c8391ea5e7017c308fb\setup.py", line 616, in <module> setup( ~~~~~^ name='dlib', ^^^^^^^^^^^^ ...<40 lines>... ], ^^ ) ^ File "D:\Anaconda\Lib\site-packages\setuptools\__init__.py", line 108, in setup return distutils.core.setup(**attrs) ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^ File "D:\Anaconda\Lib\site-packages\setuptools\_distutils\core.py", line 184, in setup return run_commands(dist) File "D:\Anaconda\Lib\site-packages\setuptools\_distutils\core.py", line 200, in run_commands dist.run_commands() ~~~~~~~~~~~~~~~~~^^ File "D:\Anaconda\Lib\site-packages\setuptools\_distutils\dist.py", line 970, in run_commands self.run_command(cmd) ~~~~~~~~~~~~~~~~^^^^^ File "D:\Anaconda\Lib\site-packages\setuptools\dist.py", line 945, in run_command super().run_command(command) ~~~~~~~~~~~~~~~~~~~^^^^^^^^^ File "D:\Anaconda\Lib\site-packages\setuptools\_distutils\dist.py", line 989, in run_command cmd_obj.run() ~~~~~~~~~~~^^ File "D:\Anaconda\Lib\site-packages\setuptools\command\bdist_wheel.py", line 373, in run self.run_command("build") ~~~~~~~~~~~~~~~~^^^^^^^^^ File "D:\Anaconda\Lib\site-packages\setuptools\_distutils\cmd.py", line 316, in run_command self.distribution.run_command(command) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^ File "D:\Anaconda\Lib\site-packages\setuptools\dist.py", line 945, in run_command super().run_command(command) ~~~~~~~~~~~~~~~~~~~^^^^^^^^^ File "D:\Anaconda\Lib\site-packages\setuptools\_distutils\dist.py", line 989, in run_command cmd_obj.run() ~~~~~~~~~~~^^ File "C:\Users\XC\AppData\Local\Temp\pip-install-t9ptlaxa\dlib_04710a2f6a364c8391ea5e7017c308fb\setup.py", line 410, in run self.build_dlib() ~~~~~~~~~~~~~~~^^ File "C:\Users\XC\AppData\Local\Temp\pip-install-t9ptlaxa\dlib_04710a2f6a364c8391ea5e7017c308fb\setup.py", line 567, in build_dlib if run_process(cmake_cmd): ~~~~~~~~~~~^^^^^^^^^^^ File "C:\Users\XC\AppData\Local\Temp\pip-install-t9ptlaxa\dlib_04710a2f6a364c8391ea5e7017c308fb\setup.py", line 303, in run_process while t.isAlive(): ^^^^^^^^^ AttributeError: 'Thread' object has no attribute 'isAlive'. Did you mean: 'is_alive'? [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for dlib Running setup.py clean for dlib Failed to build dlib ERROR: Failed to build installable wheels for some pyproject.toml based projects (dlib)

时间: 2025-07-04 07:15:44 浏览: 18
从错误日志来看,`pip install dlib==19.7.0` 失败的核心原因是 **Python 3.9+ 中 `Thread.isAlive()` 方法已被弃用**(需替换为 `Thread.is_alive()`),而 `dlib-19.7.0` 的源码未适配这一变更。以下是详细解决方案: --- ### **解决方案** #### 方法 1:修改源码后手动安装 1. **下载源码包**: ```bash pip download dlib==19.7.0 --no-deps ``` 解压生成的 `dlib-19.7.0.tar.gz` 文件。 2. **修改 `setup.py`**: - 找到文件中的 `t.isAlive()`(约第 303 行),替换为 `t.is_alive()`。 - 同时修复 `SyntaxWarning`(可选): ```python # 将以下代码中的反斜杠转义替换为原始字符串或双反斜杠 major = re.findall(r"set\(CPACK_PACKAGE_VERSION_MAJOR.*\"(.*)\"", open('dlib/CMakeLists.txt').read())[0] ``` 3. **本地安装**: ```bash pip install /path/to/modified/dlib-19.7.0 ``` #### 方法 2:使用更高版本的 `dlib` 直接安装兼容 Python 3.9+ 的版本(如 `19.24.0`): ```bash pip install dlib --upgrade ``` #### 方法 3:通过 Conda 安装(推荐) Conda 的预编译包通常已解决兼容性问题: ```bash conda install -c conda-forge dlib=19.7.0 ``` #### 方法 4:降级 Python 版本 临时使用 Python 3.8(`dlib-19.7.0` 官方支持的最高版本): ```bash conda create -n py38 python=3.8 conda activate py38 pip install dlib==19.7.0 ``` --- ### **关键错误分析** 1. **`Thread.isAlive()` 问题**: - Python 3.9+ 移除了 `threading.Thread.isAlive()`,需改用 `is_alive()`。 - 这是 `dlib-19.7.0` 的遗留代码缺陷。 2. **CMake 配置警告**: - 日志中 `Configuring cmake ...` 后的错误表明 CMake 未正确安装或未加入系统路径。 3. **`SyntaxWarning`**: - 源码中的正则表达式使用了无效的转义序列(如 `\(`),虽不影响运行但需修复。 --- ### **附加建议** - **安装 CMake**:确保系统已安装 CMake 并添加到环境变量: ```bash conda install -c conda-forge cmake ``` - **启用 Pip 的 PEP 517 构建**(可能绕过部分问题): ```bash pip install dlib==19.7.0 --use-pep517 ``` ---
阅读全文

相关推荐

PS C:\jichuang\Project\pythonProject> pip install deepface Collecting deepface Using cached deepface-0.0.93-py3-none-any.whl.metadata (30 kB) Collecting requests>=2.27.1 (from deepface) Using cached requests-2.32.4-py3-none-any.whl.metadata (4.9 kB) Requirement already satisfied: numpy>=1.14.0 in c:\users\zzysg\appdata\local\programs\python\python313\lib\site-packages (from deepface) (2.3.1) Requirement already satisfied: pandas>=0.23.4 in c:\users\zzysg\appdata\local\programs\python\python313\lib\site-packages (from deepface) (2.3.0) Collecting gdown>=3.10.1 (from deepface) Using cached gdown-5.2.0-py3-none-any.whl.metadata (5.8 kB) Collecting tqdm>=4.30.0 (from deepface) Using cached tqdm-4.67.1-py3-none-any.whl.metadata (57 kB) Requirement already satisfied: Pillow>=5.2.0 in c:\users\zzysg\appdata\local\programs\python\python313\lib\site-packages (from deepface) (11.3.0) Requirement already satisfied: opencv-python>=4.5.5.64 in c:\users\zzysg\appdata\local\programs\python\python313\lib\site-packages (from deepface) (4.11.0.86) INFO: pip is looking at multiple versions of deepface to determine which version is compatible with other requirements. This could take a while. Collecting deepface Using cached deepface-0.0.92-py3-none-any.whl.metadata (27 kB) Using cached deepface-0.0.91-py3-none-any.whl.metadata (26 kB) Using cached deepface-0.0.90-py3-none-any.whl.metadata (26 kB) Using cached deepface-0.0.89-py3-none-any.whl.metadata (26 kB) Using cached deepface-0.0.88-py3-none-any.whl.metadata (26 kB) Using cached deepface-0.0.87-py3-none-any.whl.metadata (26 kB) Using cached deepface-0.0.86-py3-none-any.whl.metadata (24 kB) INFO: pip is still looking at multiple versions of deepface to determine which version is compatible with other requirements. This could take a while. Using cached deepface-0.0.85-py3-none-any.whl.metadata (24 kB) Using cached deepface-0.0.84-py3-none-any.whl.metadata (24 kB) Using cached deepface-0.0.83-py3-none-any.whl.metadata (24 kB) Using cached deepface-0.0.82-py3-none-any.whl.metadata (24 kB) Using cached deepface-0.0.81-py3-none-any.whl.metadata (24 kB) INFO: This is taking longer than usual. You might need to provide the dependency resolver with stricter constraints to reduce runtime. See https://pip.pypa.io/warnings/backtracking for guidance. If you want to abort this run, press Ctrl + C. Using cached deepface-0.0.80-py3-none-any.whl.metadata (24 kB) Using cached deepface-0.0.79-py3-none-any.whl.metadata (26 kB) Using cached deepface-0.0.78-py3-none-any.whl.metadata (24 kB) Using cached deepface-0.0.75-py3-none-any.whl.metadata (19 kB) Using cached deepface-0.0.74-py3-none-any.whl.metadata (19 kB) Using cached deepface-0.0.73-py3-none-any.whl.metadata (19 kB) Using cached deepface-0.0.72-py3-none-any.whl.metadata (19 kB) Using cached deepface-0.0.71-py3-none-any.whl.metadata (19 kB) Using cached deepface-0.0.70-py3-none-any.whl.metadata (18 kB) Using cached deepface-0.0.69-py3-none-any.whl.metadata (18 kB) Using cached deepface-0.0.68-py3-none-any.whl.metadata (16 kB) Using cached deepface-0.0.67-py3-none-any.whl.metadata (16 kB) Using cached deepface-0.0.66-py3-none-any.whl.metadata (16 kB) Using cached deepface-0.0.65-py3-none-any.whl.metadata (16 kB) Using cached deepface-0.0.64-py3-none-any.whl.metadata (16 kB) Using cached deepface-0.0.63-py3-none-any.whl.metadata (19 kB) Using cached deepface-0.0.62-py3-none-any.whl.metadata (20 kB) Using cached deepface-0.0.61-py3-none-any.whl.metadata (20 kB) Using cached deepface-0.0.60-py3-none-any.whl.metadata (20 kB) Using cached deepface-0.0.59-py3-none-any.whl.metadata (20 kB) Using cached deepface-0.0.58-py3-none-any.whl.metadata (21 kB) Using cached deepface-0.0.57-py3-none-any.whl.metadata (21 kB) Using cached deepface-0.0.56-py3-none-any.whl.metadata (20 kB) Using cached deepface-0.0.55-py3-none-any.whl.metadata (20 kB) Using cached deepface-0.0.54-py3-none-any.whl.metadata (20 kB) Using cached deepface-0.0.53-py3-none-any.whl.metadata (20 kB) Using cached deepface-0.0.52-py3-none-any.whl.metadata (20 kB) Using cached deepface-0.0.51-py3-none-any.whl.metadata (21 kB) Using cached deepface-0.0.50-py3-none-any.whl.metadata (21 kB) Using cached deepface-0.0.49-py3-none-any.whl.metadata (17 kB) Using cached deepface-0.0.48-py3-none-any.whl.metadata (17 kB) Using cached deepface-0.0.47-py3-none-any.whl.metadata (16 kB) Using cached deepface-0.0.46-py3-none-any.whl.metadata (16 kB) Using cached deepface-0.0.45-py3-none-any.whl.metadata (16 kB) Using cached deepface-0.0.44-py3-none-any.whl.metadata (16 kB) Using cached deepface-0.0.43-py3-none-any.whl.metadata (16 kB) Using cached deepface-0.0.41-py3-none-any.whl.metadata (15 kB) Using cached deepface-0.0.40-py3-none-any.whl.metadata (15 kB) Using cached deepface-0.0.39-py3-none-any.whl.metadata (15 kB) Using cached deepface-0.0.38-py3-none-any.whl.metadata (15 kB) Using cached deepface-0.0.37-py3-none-any.whl.metadata (15 kB) Using cached deepface-0.0.36-py3-none-any.whl.metadata (15 kB) Using cached deepface-0.0.35-py3-none-any.whl.metadata (14 kB) Using cached deepface-0.0.34-py3-none-any.whl.metadata (13 kB) Using cached deepface-0.0.33-py3-none-any.whl.metadata (13 kB) Using cached deepface-0.0.32-py3-none-any.whl.metadata (13 kB) Using cached deepface-0.0.31-py3-none-any.whl.metadata (13 kB) Using cached deepface-0.0.30-py3-none-any.whl.metadata (13 kB) Using cached deepface-0.0.26-py3-none-any.whl.metadata (15 kB) Using cached deepface-0.0.25-py3-none-any.whl.metadata (15 kB) Using cached deepface-0.0.24-py3-none-any.whl.metadata (13 kB) Using cached deepface-0.0.23-py3-none-any.whl.metadata (13 kB) Using cached deepface-0.0.22-py3-none-any.whl.metadata (12 kB) Using cached deepface-0.0.21-py3-none-any.whl.metadata (12 kB) Using cached deepface-0.0.20-py3-none-any.whl.metadata (10 kB) Using cached deepface-0.0.19-py3-none-any.whl.metadata (10 kB) Using cached deepface-0.0.18-py3-none-any.whl.metadata (9.6 kB) Using cached deepface-0.0.16-py3-none-any.whl.metadata (9.6 kB) Using cached deepface-0.0.15-py3-none-any.whl.metadata (9.7 kB) Using cached deepface-0.0.14-py3-none-any.whl.metadata (9.7 kB) Requirement already satisfied: matplotlib>=2.2.2 in c:\users\zzysg\appdata\local\programs\python\python313\lib\site-packages (from deepface) (3.10.3) Using cached deepface-0.0.13-py3-none-any.whl.metadata (9.7 kB) Using cached deepface-0.0.12-py3-none-any.whl.metadata (9.2 kB) Using cached deepface-0.0.11-py3-none-any.whl.metadata (9.2 kB) Using cached deepface-0.0.10-py3-none-any.whl.metadata (9.2 kB) Using cached deepface-0.0.9-py3-none-any.whl.metadata (8.6 kB) Using cached deepface-0.0.7-py3-none-any.whl.metadata (8.3 kB) Using cached deepface-0.0.6-py3-none-any.whl.metadata (7.9 kB) Using cached deepface-0.0.5-py3-none-any.whl.metadata (8.3 kB) Using cached deepface-0.0.4-py3-none-any.whl.metadata (8.1 kB) Using cached deepface-0.0.3-py3-none-any.whl.metadata (8.1 kB) Using cached deepface-0.0.2-py3-none-any.whl.metadata (8.0 kB) Using cached deepface-0.0.1-py3-none-any.whl.metadata (4.4 kB) ERROR: Cannot install deepface==0.0.1, deepface==0.0.10, deepface==0.0.11, deepface==0.0.12, deepface==0.0.13, deepface==0.0.14, deepface==0.0.15, d eepface==0.0.16, deepface==0.0.18, deepface==0.0.19, deepface==0.0.2, deepface==0.0.20, deepface==0.0.21, deepface==0.0.22, deepface==0.0.23, deepfa ce==0.0.24, deepface==0.0.25, deepface==0.0.26, deepface==0.0.3, deepface==0.0.30, deepface==0.0.31, deepface==0.0.32, deepface==0.0.33, deepface==0 .0.34, deepface==0.0.35, deepface==0.0.36, deepface==0.0.37, deepface==0.0.38, deepface==0.0.39, deepface==0.0.4, deepface==0.0.40, deepface==0.0.41 , deepface==0.0.43, deepface==0.0.44, deepface==0.0.45, deepface==0.0.46, deepface==0.0.47, deepface==0.0.48, deepface==0.0.49, deepface==0.0.5, dee pface==0.0.50, deepface==0.0.51, deepface==0.0.52, deepface==0.0.53, deepface==0.0.54, deepface==0.0.55, deepface==0.0.56, deepface==0.0.57, deepfac e==0.0.58, deepface==0.0.59, deepface==0.0.6, deepface==0.0.60, deepface==0.0.61, deepface==0.0.62, deepface==0.0.63, deepface==0.0.64, deepface==0. 0.65, deepface==0.0.66, deepface==0.0.67, deepface==0.0.68, deepface==0.0.69, deepface==0.0.7, deepface==0.0.70, deepface==0.0.71, deepface==0.0.72, deepface==0.0.73, deepface==0.0.74, deepface==0.0.75, deepface==0.0.78, deepface==0.0.79, deepface==0.0.80, deepface==0.0.81, deepface==0.0.82, dee pface==0.0.83, deepface==0.0.84, deepface==0.0.85, deepface==0.0.86, deepface==0.0.87, deepface==0.0.88, deepface==0.0.89, deepface==0.0.9, deepface==0.0.90, deepface==0.0.91, deepface==0.0.92 and deepface==0.0.93 because these package versions have conflicting dependencies. The conflict is caused by: deepface 0.0.93 depends on tensorflow>=1.9.0 deepface 0.0.92 depends on tensorflow>=1.9.0 deepface 0.0.91 depends on tensorflow>=1.9.0 deepface 0.0.90 depends on tensorflow>=1.9.0 deepface 0.0.89 depends on tensorflow>=1.9.0 deepface 0.0.88 depends on tensorflow>=1.9.0 deepface 0.0.87 depends on tensorflow>=1.9.0 deepface 0.0.86 depends on tensorflow>=1.9.0 deepface 0.0.85 depends on tensorflow>=1.9.0 deepface 0.0.84 depends on tensorflow>=1.9.0 deepface 0.0.83 depends on tensorflow>=1.9.0 deepface 0.0.82 depends on tensorflow>=1.9.0 deepface 0.0.81 depends on tensorflow>=1.9.0 deepface 0.0.80 depends on tensorflow>=1.9.0 deepface 0.0.79 depends on tensorflow>=1.9.0 deepface 0.0.78 depends on tensorflow>=1.9.0 deepface 0.0.75 depends on tensorflow>=1.9.0 deepface 0.0.74 depends on tensorflow>=1.9.0 deepface 0.0.73 depends on tensorflow>=1.9.0 deepface 0.0.72 depends on tensorflow>=1.9.0 deepface 0.0.71 depends on tensorflow>=1.9.0 deepface 0.0.70 depends on tensorflow>=1.9.0 deepface 0.0.69 depends on tensorflow>=1.9.0 deepface 0.0.68 depends on tensorflow>=1.9.0 deepface 0.0.67 depends on tensorflow>=1.9.0 deepface 0.0.66 depends on tensorflow>=1.9.0 deepface 0.0.65 depends on tensorflow>=1.9.0 deepface 0.0.64 depends on tensorflow>=1.9.0 deepface 0.0.63 depends on tensorflow>=1.9.0 deepface 0.0.62 depends on tensorflow>=1.9.0 deepface 0.0.61 depends on tensorflow>=1.9.0 deepface 0.0.60 depends on tensorflow>=1.9.0 deepface 0.0.59 depends on tensorflow>=1.9.0 deepface 0.0.58 depends on tensorflow>=1.9.0 deepface 0.0.57 depends on tensorflow>=1.9.0 deepface 0.0.56 depends on tensorflow>=1.9.0 deepface 0.0.55 depends on tensorflow>=1.9.0 deepface 0.0.54 depends on tensorflow>=1.9.0 deepface 0.0.53 depends on tensorflow>=1.9.0 deepface 0.0.52 depends on tensorflow>=1.9.0 deepface 0.0.51 depends on tensorflow>=1.9.0 deepface 0.0.50 depends on tensorflow>=1.9.0 deepface 0.0.49 depends on tensorflow>=1.9.0 deepface 0.0.48 depends on tensorflow>=1.9.0 deepface 0.0.47 depends on tensorflow>=1.9.0 deepface 0.0.46 depends on tensorflow>=1.9.0 deepface 0.0.45 depends on tensorflow>=1.9.0 deepface 0.0.44 depends on tensorflow>=1.9.0 deepface 0.0.43 depends on tensorflow>=1.9.0 deepface 0.0.41 depends on tensorflow>=1.9.0 deepface 0.0.40 depends on tensorflow>=1.9.0 deepface 0.0.39 depends on tensorflow>=1.9.0 deepface 0.0.38 depends on tensorflow>=1.9.0 deepface 0.0.37 depends on tensorflow>=1.9.0 deepface 0.0.36 depends on tensorflow>=1.9.0 deepface 0.0.35 depends on tensorflow>=1.9.0 deepface 0.0.34 depends on tensorflow>=1.9.0 deepface 0.0.33 depends on tensorflow>=1.9.0 deepface 0.0.32 depends on tensorflow>=1.9.0 deepface 0.0.31 depends on tensorflow>=1.9.0 deepface 0.0.30 depends on tensorflow>=1.9.0 deepface 0.0.26 depends on tensorflow>=1.9.0 deepface 0.0.25 depends on tensorflow>=1.9.0 deepface 0.0.24 depends on tensorflow>=1.9.0 deepface 0.0.23 depends on tensorflow>=1.9.0 deepface 0.0.22 depends on tensorflow>=1.9.0 deepface 0.0.21 depends on tensorflow>=1.9.0 deepface 0.0.20 depends on tensorflow>=1.9.0 deepface 0.0.19 depends on tensorflow>=1.9.0 deepface 0.0.18 depends on tensorflow>=1.9.0 deepface 0.0.16 depends on tensorflow>=1.9.0 deepface 0.0.15 depends on tensorflow>=1.9.0 deepface 0.0.14 depends on tensorflow>=1.9.0 deepface 0.0.13 depends on tensorflow>=1.9.0 deepface 0.0.12 depends on tensorflow>=1.9.0 deepface 0.0.11 depends on tensorflow>=1.9.0 deepface 0.0.10 depends on tensorflow>=1.9.0 deepface 0.0.9 depends on tensorflow>=1.9.0 deepface 0.0.7 depends on tensorflow>=1.9.0 deepface 0.0.6 depends on tensorflow>=1.9.0 deepface 0.0.5 depends on tensorflow>=1.9.0 deepface 0.0.4 depends on tensorflow>=1.9.0 deepface 0.0.3 depends on tensorflow>=1.9.0 deepface 0.0.2 depends on tensorflow>=1.9.0 deepface 0.0.1 depends on tensorflow>=1.9.0 To fix this you could try to: 1. loosen the range of package versions you've specified 2. remove package versions to allow pip to attempt to solve the dependency conflict ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts 此时我应该怎么在终端输入指令

Collecting face_recognition Using cached face_recognition-1.3.0-py2.py3-none-any.whl (15 kB) Requirement already satisfied: Pillow in d:\anaconda\envs\pytorch\lib\site-packages (from face_recognition) (9.4.0) Requirement already satisfied: face-recognition-models>=0.3.0 in d:\anaconda\envs\pytorch\lib\site-packages (from face_recognition) (0.3.0) Collecting dlib>=19.7 Using cached dlib-19.24.1.tar.gz (3.2 MB) Preparing metadata (setup.py) ... done Requirement already satisfied: Click>=6.0 in d:\anaconda\envs\pytorch\lib\site-packages (from face_recognition) (8.1.3) Requirement already satisfied: numpy in d:\anaconda\envs\pytorch\lib\site-packages (from face_recognition) (1.24.2) Requirement already satisfied: colorama in d:\anaconda\envs\pytorch\lib\site-packages (from Click>=6.0->face_recognition) (0.4.6) Building wheels for collected packages: dlib Building wheel for dlib (setup.py) ... error error: subprocess-exited-with-error × python setup.py bdist_wheel did not run successfully. │ exit code: 1 ╰─> [7 lines of output] running bdist_wheel running build running build_py running build_ext ERROR: CMake must be installed to build dlib [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for dlib Running setup.py clean for dlib Failed to build dlib Installing collected packages: dlib, face_recognition Running setup.py install for dlib ... error error: subprocess-exited-with-error × Running setup.py install for dlib did not run successfully. │ exit code: 1 ╰─> [9 lines of output] running install D:\anaconda\envs\pytorch\lib\site-packages\setuptools\command\install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools. warnings.warn( running build running build_py running build_ext ERROR: CMake must be installed to build dlib [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: legacy-install-failure × Encountered error while trying to install package. ╰─> dlib note: This is an issue with the package mentioned above, not pip. hint: See above for output from the failure.

D:\BCRJ_XMML\Pycharm\test001>pip install dlib Collecting dlib Using cached dlib-19.24.8.tar.gz (3.4 MB) Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... done Building wheels for collected packages: dlib Building wheel for dlib (pyproject.toml) ... error error: subprocess-exited-with-error × Building wheel for dlib (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [50 lines of output] <string>:234: SyntaxWarning: invalid escape sequence '\(' <string>:235: SyntaxWarning: invalid escape sequence '\(' <string>:236: SyntaxWarning: invalid escape sequence '\(' running bdist_wheel running build running build_ext Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "D:\RJ_AZLJ\python\python311\Scripts\cmake.exe\__main__.py", line 4, in <module> from cmake import cmake ModuleNotFoundError: No module named 'cmake' ================================================================================ ================================================================================ ================================================================================ CMake is not installed on your system! Or it is possible some broken copy of cmake is installed on your system. It is unfortunately very common for python package managers to include broken copies of cmake. So if the error above this refers to some file path to a cmake file inside a python or anaconda or miniconda path then you should delete that broken copy of cmake from your computer. Instead, please get an official copy of cmake from one of these known good sources of an official cmake: - cmake.org (this is how windows users

命令行运行:pip install dlib==19.24.0报错: Collecting dlib==19.24.0 Using cached dlib-19.24.0.tar.gz (3.2 MB) Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... done Building wheels for collected packages: dlib Building wheel for dlib (pyproject.toml) ... error error: subprocess-exited-with-error × Building wheel for dlib (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [29 lines of output] <string>:212: SyntaxWarning: invalid escape sequence '\(' <string>:213: SyntaxWarning: invalid escape sequence '\(' <string>:214: SyntaxWarning: invalid escape sequence '\(' <string>:194: SetuptoolsDeprecationWarning: The test command is disabled and references to it are deprecated. !! ******************************************************************************** Please remove any references to setuptools.command.test in all supported versions of the affected package. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. ******************************************************************************** !! C:\Users\徐庆凯\AppData\Local\Temp\pip-build-env-r6nhe5ov\overlay\Lib\site-packages\setuptools\_distutils\dist.py:289: UserWarning: Unknown distribution option: 'tests_require' warnings.warn(msg) running bdist_wheel running build running build_py running build_ext Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "D:\Users\徐庆凯\AppData\Local\Programs\Python\Python313\Scripts\cmake.exe\__main__.py", line 4, in <module> from cmake import cmake ModuleNotFoundError: No module named 'cmake' ERROR: CMake must be installed to build dlib [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for dlib Failed to build dlib ERROR: Failed to build installable wheels for some pyproject.toml based projects (dlib)

.venv1) PS E:\PythonProject> pip install dlib -i https://pypi.tuna.tsinghua.edu.cn/simple/ Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple/ Collecting dlib Using cached https://pypi.tuna.tsinghua.edu.cn/packages/28/f4/f8949b18ec1df2ef05fc2ea1d1dd82ff2d050b8704b7d0d088017315c221/dlib-20.0.0.tar.gz (3.3 MB) Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... done Building wheels for collected packages: dlib Building wheel for dlib (pyproject.toml) ... error error: subprocess-exited-with-error × Building wheel for dlib (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [48 lines of output] running bdist_wheel running build running build_ext Traceback (most recent call last): File "E:\python3.8\lib\runpy.py", line 194, in _run_module_as_main return _run_code(code, main_globals, None, File "E:\python3.8\lib\runpy.py", line 87, in _run_code exec(code, run_globals) File "E:\PythonProject\.venv1\Scripts\cmake.exe\__main__.py", line 4, in <module> ModuleNotFoundError: No module named 'cmake' ================================================================================ ================================================================================ ================================================================================ CMake is not installed on your system! Or it is possible some broken copy of cmake is installed on your system. It is unfortunately very common for python package managers to include broken copies of cmake. So if the error above this refers to some file path to a cmake file inside a python or anaconda or miniconda path then you should delete that broken copy of cmake from your computer. Instead, please get an official copy of cmake from one of these known good sources of an official cmake: - cmake.org (this is how windows users should get cmake) - apt install cmake (for Ubuntu or Debian based systems) - yum install cmake (for Redhat or CenOS based systems) On a linux machine you can run which cmake to see what cmake you are actually using. If it tells you it's some cmake from any kind of python packager delete it and install an official cmake. More generally, cmake is not installed if when you open a terminal window and type cmake --version you get an error. So you can use that as a very basic test to see if you have cmake installed. That is, if cmake --version doesn't run from the same terminal window from which you are reading this error message, then you have not installed cmake. Windows users should take note that they need to tell the cmake installer to add cmake to their PATH. Since you can't run commands that are not in your PATH. This is how the PATH works on Linux as well, but failing to add cmake to the PATH is a particularly common problem on windows and rarely a problem on Linux. ================================================================================ ================================================================================ ================================================================================ [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for dlib Failed to build dlib ERROR: Failed to build installable wheels for some pyproject.toml based projects (dlib) (.venv1) PS E:\PythonProject> pip3 install dlib -i http://pypi.douban.com/simple/ Looking in indexes: http://pypi.douban.com/simple/ WARNING: The repository located at pypi.douban.com is not a trusted or secure host and is being ignored. If this repository is available via HTTPS we recommend you use HTTPS instead, otherwise you may silence this warning and allow it anyway with '--trusted-host pypi.douban.com'. ERROR: Could not find a version that satisfies the requirement dlib (from versions: none) ERROR: No matching distribution found for dlib

权所有(C) Microsoft Corporation。保留所有权利。 安装最新的 PowerShell,了解新功能和改进!https://aka.ms/PSWindows (.venv1) PS D:\OCR\AW> pip install -r requirements.txt -i https://pypi.tuna.tsinghua.edu.cn/simple Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple Collecting altgraph==0.17.2 (from -r requirements.txt (line 1)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/84/3f/1a5c9bef54cac9bf41edd6f4aaf61cd52ed578e10ccc607e0278012cb4a5/altgraph-0.17.2-py2.py3-none-any.whl (21 kB) Collecting cycler==0.11.0 (from -r requirements.txt (line 2)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/5c/f9/695d6bedebd747e5eb0fe8fad57b72fdf25411273a39791cde838d5a8f51/cycler-0.11.0-py3-none-any.whl (6.4 kB) Collecting dlib==19.23.0 (from -r requirements.txt (line 3)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/25/0f/05e70b2ebf6a539c4c397c7c3dd19b69e0b3d650443e12a8af4866f65b03/dlib-19.23.0.tar.gz (3.2 MB) Preparing metadata (setup.py) ... done Collecting fonttools==4.33.3 (from -r requirements.txt (line 4)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/2f/85/2f6e42fb4b537b9998835410578fb1973175b81691e9a82ab6668cf64b0b/fonttools-4.33.3-py3-none-any.whl (930 kB) Collecting future==0.18.2 (from -r requirements.txt (line 5)) Using cached future-0.18.2-py3-none-any.whl Collecting importlib-metadata==4.11.4 (from -r requirements.txt (line 6)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/ab/b5/1bd220dd470b0b912fc31499e0d9c652007a60caf137995867ccc4b98cb6/importlib_metadata-4.11.4-py3-none-any.whl (18 kB) Collecting kiwisolver==1.4.2 (from -r requirements.txt (line 7)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/49/75/3a5f894ff63a2f13bd68d7962d01b9393bba139335cf9f47b2eb8739e63b/kiwisolver-1.4.2-cp39-cp39-win_amd64.whl (55 kB) Collecting matplotlib==3.5.2 (from -r requirements.txt (line 8)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/43/64/1d949d0fab5b83071290a46c93de28cbd8ff15a75b533d6c134012c61e4d/matplotlib-3.5.2-cp39-cp39-win_amd64.whl (7.2 MB) Collecting numpy==1.21.6 (from -r requirements.txt (line 9)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/4d/04/bcd62448f2e772bc90a73ba21bacaa19817ae9905ae639969462862bd071/numpy-1.21.6-cp39-cp39-win_amd64.whl (14.0 MB) Collecting opencv-python==4.5.2.54 (from -r requirements.txt (line 10)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/7c/5d/5581984f71c3378f913057beb4a0c53a22d71dd1b6d49457314ecd26c5af/opencv_python-4.5.2.54-cp39-cp39-win_amd64.whl (34.7 MB) Collecting packaging==21.3 (from -r requirements.txt (line 11)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/05/8e/8de486cbd03baba4deef4142bd643a3e7bbe954a784dc1bb17142572d127/packaging-21.3-py3-none-any.whl (40 kB) Collecting pefile==2022.5.30 (from -r requirements.txt (line 12)) Using cached pefile-2022.5.30-py3-none-any.whl Collecting Pillow==9.1.1 (from -r requirements.txt (line 13)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/cc/d9/5d0c2a0146fe68781a1920fa2a68d81bc55de38bed50beb8bf2493e0c7c1/Pillow-9.1.1-cp39-cp39-win_amd64.whl (3.3 MB) Collecting pyinstaller==5.1 (from -r requirements.txt (line 14)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/39/0c/fcedab1fc19e4a7b275c5298bb9c69e411d5092ceaf5a167b611de4c023d/pyinstaller-5.1-py3-none-win_amd64.whl (1.2 MB) Collecting pyinstaller-hooks-contrib==2022.7 (from -r requirements.txt (line 15)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/de/97/9901350320f0454a04a937666235f532353c55507679cca9712464760431/pyinstaller_hooks_contrib-2022.7-py2.py3-none-any.whl (234 kB) Collecting pyparsing==3.0.9 (from -r requirements.txt (line 16)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/6c/10/a7d0fa5baea8fe7b50f448ab742f26f52b80bfca85ac2be9d35cdd9a3246/pyparsing-3.0.9-py3-none-any.whl (98 kB) Collecting PyQt5==5.15.6 (from -r requirements.txt (line 17)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/be/f2/8e7b751d102ce3500cbeff97cb514eaf5c06d5e423676c37e9de28d0c06b/PyQt5-5.15.6-cp36-abi3-win_amd64.whl (6.7 MB) Collecting PyQt5-Qt5==5.15.2 (from -r requirements.txt (line 18)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/37/97/5d3b222b924fa2ed4c2488925155cd0b03fd5d09ee1cfcf7c553c11c9f66/PyQt5_Qt5-5.15.2-py3-none-win_amd64.whl (50.1 MB) Collecting PyQt5-sip==12.10.1 (from -r requirements.txt (line 19)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/f7/83/eecd013e3d38648e54a63ffe85639a481a14e09f4e75423968e915196937/PyQt5_sip-12.10.1-cp39-cp39-win_amd64.whl (77 kB) Collecting python-dateutil==2.8.2 (from -r requirements.txt (line 20)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/36/7a/87837f39d0296e723bb9b62bbb257d0355c7f6128853c78955f57342a56d/python_dateutil-2.8.2-py2.py3-none-any.whl (247 kB) Collecting pywin32-ctypes==0.2.0 (from -r requirements.txt (line 21)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/9e/4b/3ab2720f1fa4b4bc924ef1932b842edf10007e4547ea8157b0b9fc78599a/pywin32_ctypes-0.2.0-py2.py3-none-any.whl (28 kB) Collecting six==1.16.0 (from -r requirements.txt (line 22)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/d9/5a/e7c31adbe875f2abbb91bd84cf2dc52d792b5a01506781dbcf25c91daf11/six-1.16.0-py2.py3-none-any.whl (11 kB) Collecting typing_extensions==4.2.0 (from -r requirements.txt (line 23)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/75/e1/932e06004039dd670c9d5e1df0cd606bf46e29a28e65d5bb28e894ea29c9/typing_extensions-4.2.0-py3-none-any.whl (24 kB) Collecting zipp==3.8.0 (from -r requirements.txt (line 24)) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/80/0e/16a7ee38617aab6a624e95948d314097cc2669edae9b02ded53309941cfc/zipp-3.8.0-py3-none-any.whl (5.4 kB) Requirement already satisfied: setuptools in d:\ocr\aw\.venv1\lib\site-packages (from pyinstaller==5.1->-r requirements.txt (line 14)) (68.2.0) Building wheels for collected packages: dlib Building wheel for dlib (setup.py) ... error error: subprocess-exited-with-error × python setup.py bdist_wheel did not run successfully. │ exit code: 1 ╰─> [60 lines of output] running bdist_wheel running build running build_py running build_ext C:\Users\Admin\AppData\Local\Temp\pip-install-o09thgtz\dlib_63c12b5a1a2f485aaf617ed09e75027e\setup.py:129: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead. if LooseVersion(cmake_version) < '3.1.0': Building extension for Python 3.9.13 (tags/v3.9.13:6de2ca5, May 17 2022, 16:36:42) [MSC v.1929 64 bit (AMD64)] Invoking CMake setup: 'cmake C:\Users\Admin\AppData\Local\Temp\pip-install-o09thgtz\dlib_63c12b5a1a2f485aaf617ed09e75027e\tools\python -DCMAKE_LIBRARY_OUTPUT_DIRECTORY=C:\Users\Admin\AppData\Local\Temp\pip-install-o09thgtz\d lib_63c12b5a1a2f485aaf617ed09e75027e\build\lib.win-amd64-cpython-39 -DPYTHON_EXECUTABLE=D:\OCR\AW\.venv1\Scripts\python.exe -DCMAKE_LIBRARY_OUTPUT_DIRECTORY_RELEASE=C:\Users\Admin\AppData\Local\Temp\pip-install-o09thgtz\dlib_63c12b5a1a2f485aaf617ed09e75027e\build\lib.win-amd64-cpython-39 -A x64' -- Building for: Visual Studio 17 2022 CMake Error at CMakeLists.txt:2 (CMAKE_MINIMUM_REQUIRED): Compatibility with CMake < 3.5 has been removed from CMake. Update the VERSION argument <min> value. Or, use the <min>...<max> syntax to tell CMake that the project requires at least <min> but has been updated to work with policies introduced by <max> or earlier. Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway. -- Configuring incomplete, errors occurred! Traceback (most recent call last): File "<string>", line 2, in <module> File "", line 34, in <module> File "C:\Users\Admin\AppData\Local\Temp\pip-install-o09thgtz\dlib_63c12b5a1a2f485aaf617ed09e75027e\setup.py", line 222, in <module> setup( File "D:\OCR\AW\.venv1\lib\site-packages\setuptools\__init__.py", line 103, in setup return distutils.core.setup(**attrs) File "D:\OCR\AW\.venv1\lib\site-packages\setuptools\_distutils\core.py", line 185, in setup return run_commands(dist) File "D:\OCR\AW\.venv1\lib\site-packages\setuptools\_distutils\core.py", line 201, in run_commands dist.run_commands() File "D:\OCR\AW\.venv1\lib\site-packages\setuptools\_distutils\dist.py", line 969, in run_commands self.run_command(cmd) File "D:\OCR\AW\.venv1\lib\site-packages\setuptools\dist.py", line 1001, in run_command super().run_command(command) File "D:\OCR\AW\.venv1\lib\site-packages\setuptools\_distutils\dist.py", line 988, in run_command cmd_obj.run() File "D:\OCR\AW\.venv1\lib\site-packages\wheel\bdist_wheel.py", line 364, in run self.run_command("build") File "D:\OCR\AW\.venv1\lib\site-packages\setuptools\_distutils\cmd.py", line 318, in run_command self.distribution.run_command(command) File "D:\OCR\AW\.venv1\lib\site-packages\setuptools\dist.py", line 1001, in run_command super().run_command(command) File "D:\OCR\AW\.venv1\lib\site-packages\setuptools\_distutils\dist.py", line 988, in run_command cmd_obj.run() File "D:\OCR\AW\.venv1\lib\site-packages\setuptools\_distutils\command\build.py", line 131, in run self.run_command(cmd_name) File "D:\OCR\AW\.venv1\lib\site-packages\setuptools\_distutils\cmd.py", line 318, in run_command self.distribution.run_command(command) File "D:\OCR\AW\.venv1\lib\site-packages\setuptools\dist.py", line 1001, in run_command super().run_command(command) File "D:\OCR\AW\.venv1\lib\site-packages\setuptools\_distutils\dist.py", line 988, in run_command cmd_obj.run() File "C:\Users\Admin\AppData\Local\Temp\pip-install-o09thgtz\dlib_63c12b5a1a2f485aaf617ed09e75027e\setup.py", line 134, in run self.build_extension(ext) File "C:\Users\Admin\AppData\Local\Temp\pip-install-o09thgtz\dlib_63c12b5a1a2f485aaf617ed09e75027e\setup.py", line 171, in build_extension subprocess.check_call(cmake_setup, cwd=build_folder) File "C:\Users\Admin\AppData\Local\Programs\Python\Python39\lib\subprocess.py", line 373, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['cmake', 'C:\\Users\\Admin\\AppData\\Local\\Temp\\pip-install-o09thgtz\\dlib_63c12b5a1a2f485aaf617ed09e75027e\\tools\\python', '-DCMAKE_LIBRARY_OUTPUT_DIRECTORY=C:\\Users\\Admin\\AppD ata\\Local\\Temp\\pip-install-o09thgtz\\dlib_63c12b5a1a2f485aaf617ed09e75027e\\build\\lib.win-amd64-cpython-39', '-DPYTHON_EXECUTABLE=D:\\OCR\\AW\\.venv1\\Scripts\\python.exe', '-DCMAKE_LIBRARY_OUTPUT_DIRECTORY_RELEASE=C:\\Users\\Admin\\AppData\\Local\\Temp\\pip-install-o09thgtz\\dlib_63c12b5a1a2f485aaf617ed09e75027e\\build\\lib.win-amd64-cpython-39', '-A', 'x64']' returned non-zero exit status 1. [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for dlib Running setup.py clean for dlib Failed to build dlib ERROR: Could not build wheels for dlib, which is required to install pyproject.toml-based projects [notice] A new release of pip is available: 23.2.1 -> 25.1.1 [notice] To update, run: python.exe -m pip install --upgrade pip (.venv1) PS D:\OCR\AW> 怎么办

avi
一、综合实战—使用极轴追踪方式绘制信号灯 实战目标:利用对象捕捉追踪和极轴追踪功能创建信号灯图形 技术要点:结合两种追踪方式实现精确绘图,适用于工程制图中需要精确定位的场景 1. 切换至AutoCAD 操作步骤: 启动AutoCAD 2016软件 打开随书光盘中的素材文件 确认工作空间为"草图与注释"模式 2. 绘图设置 1)草图设置对话框 打开方式:通过"工具→绘图设置"菜单命令 功能定位:该对话框包含捕捉、追踪等核心绘图辅助功能设置 2)对象捕捉设置 关键配置: 启用对象捕捉(F3快捷键) 启用对象捕捉追踪(F11快捷键) 勾选端点、中心、圆心、象限点等常用捕捉模式 追踪原理:命令执行时悬停光标可显示追踪矢量,再次悬停可停止追踪 3)极轴追踪设置 参数设置: 启用极轴追踪功能 设置角度增量为45度 确认后退出对话框 3. 绘制信号灯 1)绘制圆形 执行命令:"绘图→圆→圆心、半径"命令 绘制过程: 使用对象捕捉追踪定位矩形中心作为圆心 输入半径值30并按Enter确认 通过象限点捕捉确保圆形位置准确 2)绘制直线 操作要点: 选择"绘图→直线"命令 捕捉矩形上边中点作为起点 捕捉圆的上象限点作为终点 按Enter结束当前直线命令 重复技巧: 按Enter可重复最近使用的直线命令 通过圆心捕捉和极轴追踪绘制放射状直线 最终形成完整的信号灯指示图案 3)完成绘制 验证要点: 检查所有直线是否准确连接圆心和象限点 确认极轴追踪的45度增量是否体现 保存绘图文件(快捷键Ctrl+S)

大家在看

recommend-type

Delphi编写的SQL查询分析器.rar

因为需要在客户那里维护一些数据, 但是人家的电脑不见得都安装了SQL Server客户端, 每次带光盘去给人家装程序也不好意思. 于是就写这个SQL查询分析器。代码不够艺术, 结构也松散, 如果代码看不懂, 只好见谅了. 程序中用到的图标, 动画都是从微软的SQLServer搞过来的, 唯一值得一提的是, 我用了ADO Binding for VC Extension(MSDN上有详细资料), 速度比用Variant快(在ADOBinding.pas和RowData.pas)。
recommend-type

kb4474419和kb4490628系统补丁.rar

要安装一些软件需要这两个补丁包,比如在win7上安装NOD32。
recommend-type

ceph心跳丢失问题分析

最近测试了ceph集群承载vm上限的实验,以及在极端压力下的表现,发现在极端大压力下,ceph集群出现osd心跳丢失,osd mark成down, pg从而运行在degrade的状态。分析了根本原因,总结成ppt分享。
recommend-type

web仿淘宝项目

大一时团队做的一个仿淘宝的web项目,没有实现后台功能
recommend-type

FPGA驱动代码详解:AD7606 SPI与并行模式读取双模式Verilog实现,注释详尽版,FPGA驱动代码详解:AD7606 SPI与并行模式读取双模式Verilog实现,注释详尽版,FPGA V

FPGA驱动代码详解:AD7606 SPI与并行模式读取双模式Verilog实现,注释详尽版,FPGA驱动代码详解:AD7606 SPI与并行模式读取双模式Verilog实现,注释详尽版,FPGA Verilog AD7606驱动代码,包含SPI模式读取和并行模式读取两种,代码注释详细。 ,FPGA; Verilog; AD7606驱动代码; SPI模式读取; 并行模式读取; 代码注释详细。,FPGA驱动代码:AD7606双模式读取(SPI+并行)Verilog代码详解

最新推荐

recommend-type

随机阻塞下毫米波通信的多波束功率分配”.zip

1.版本:matlab2014a/2019b/2024b 2.附赠案例数据可直接运行。 3.代码特点:参数化编程、参数可方便更改、代码编程思路清晰、注释明细。 4.适用对象:计算机,电子信息工程、数学等专业的大学生课程设计、期末大作业和毕业设计。
recommend-type

基于分时电价与改进粒子群算法的电动汽车充放电优化调度策略研究

内容概要:本文探讨了基于分时电价和改进粒子群算法的电动汽车充放电优化调度策略。首先介绍了分时电价制度及其对电动汽车充放电的影响,随后详细解释了改进粒子群算法的工作原理以及如何应用于电动汽车的充放电调度。文中还提供了具体的Python代码实现,展示了如何通过定义电价信息、电池容量等参数并应用改进粒子群算法来找到最优的充电时间点。最后,文章总结了该方法的优势,并展望了未来的研究方向,如与智能电网和V2G技术的结合。 适合人群:对电动汽车充放电调度感兴趣的科研人员和技术开发者。 使用场景及目标:适用于希望优化电动汽车充放电策略以降低成本、提高电力系统效率的人群。主要目标是在不同电价时段内,通过智能调度实现最低成本或最高效率的充电。 其他说明:本文不仅提供理论分析,还有详细的代码实现,便于读者理解和实践。
recommend-type

步进电机脉冲精准计算方法

资源下载链接为: https://pan.quark.cn/s/d9ef5828b597 根据步进电机的步进角、脉冲总数、减速比以及丝杠导程,计算出实现直线行走距离为1mm所需的脉冲数量。
recommend-type

【CAD入门基础课程】3.7 综合实战-使用极轴追踪方式绘制信号灯.avi

一、综合实战—使用极轴追踪方式绘制信号灯 实战目标:利用对象捕捉追踪和极轴追踪功能创建信号灯图形 技术要点:结合两种追踪方式实现精确绘图,适用于工程制图中需要精确定位的场景 1. 切换至AutoCAD 操作步骤: 启动AutoCAD 2016软件 打开随书光盘中的素材文件 确认工作空间为"草图与注释"模式 2. 绘图设置 1)草图设置对话框 打开方式:通过"工具→绘图设置"菜单命令 功能定位:该对话框包含捕捉、追踪等核心绘图辅助功能设置 2)对象捕捉设置 关键配置: 启用对象捕捉(F3快捷键) 启用对象捕捉追踪(F11快捷键) 勾选端点、中心、圆心、象限点等常用捕捉模式 追踪原理:命令执行时悬停光标可显示追踪矢量,再次悬停可停止追踪 3)极轴追踪设置 参数设置: 启用极轴追踪功能 设置角度增量为45度 确认后退出对话框 3. 绘制信号灯 1)绘制圆形 执行命令:"绘图→圆→圆心、半径"命令 绘制过程: 使用对象捕捉追踪定位矩形中心作为圆心 输入半径值30并按Enter确认 通过象限点捕捉确保圆形位置准确 2)绘制直线 操作要点: 选择"绘图→直线"命令 捕捉矩形上边中点作为起点 捕捉圆的上象限点作为终点 按Enter结束当前直线命令 重复技巧: 按Enter可重复最近使用的直线命令 通过圆心捕捉和极轴追踪绘制放射状直线 最终形成完整的信号灯指示图案 3)完成绘制 验证要点: 检查所有直线是否准确连接圆心和象限点 确认极轴追踪的45度增量是否体现 保存绘图文件(快捷键Ctrl+S)
recommend-type

基于MATLAB的蒙特卡洛抽样在电动汽车充放电负荷计算中的应用研究

内容概要:本文探讨了利用蒙特卡洛抽样方法在MATLAB仿真平台上对大规模电动汽车的充放电负荷进行计算的方法。研究内容涵盖电动汽车充电功率、电池容量、起始充电时间及每日行驶里程的概率密度分布的抽样生成,并在此基础上计算充放电负荷。文中详细介绍了蒙特卡洛抽样方法及其在电动汽车参数抽样中的应用,同时提供了完整的MATLAB代码实现,包括数据准备、抽样、负荷计算及结果可视化。此外,代码注释详尽,出图效果优秀,有助于理解和学习。 适合人群:电力系统研究人员、电动汽车行业从业者、高校师生及相关领域的科研工作者。 使用场景及目标:适用于需要评估电动汽车对电网影响的研究项目,旨在提高电网规划和运行效率,确保电力系统的稳定性和可靠性。 其他说明:本文不仅提供了详细的理论解释和技术实现,还附带了高质量的MATLAB代码,便于读者直接上手实践并进行二次开发。
recommend-type

Mockingbird v2:PocketMine-MP新防作弊机制详解

标题和描述中所涉及的知识点如下: 1. Mockingbird反作弊系统: Mockingbird是一个正在开发中的反作弊系统,专门针对PocketMine-MP服务器。PocketMine-MP是Minecraft Pocket Edition(Minecraft PE)的一个服务器软件,允许玩家在移动平台上共同游戏。随着游戏的普及,作弊问题也随之而来,因此Mockingbird的出现正是为了应对这种情况。 2. Mockingbird的版本迭代: 从描述中提到的“Mockingbird的v1变体”和“v2版本”的变化来看,Mockingbird正在经历持续的开发和改进过程。软件版本迭代是常见的开发实践,有助于修复已知问题,改善性能和用户体验,添加新功能等。 3. 服务器性能要求: 描述中强调了运行Mockingbird的服务器需要具备一定的性能,例如提及“WitherHosting的$ 1.25计划”,这暗示了反作弊系统对服务器资源的需求较高。这可能是因为反作弊机制需要频繁处理大量的数据和事件,以便及时检测和阻止作弊行为。 4. Waterdog问题: Waterdog是另一种Minecraft服务器软件,特别适合 PocketMine-MP。描述中提到如果将Mockingbird和Waterdog结合使用可能会遇到问题,这可能是因为两者在某些机制上的不兼容或Mockingbird对Waterdog的特定实现尚未完全优化。 5. GitHub使用及问题反馈: 作者鼓励用户通过GitHub问题跟踪系统来报告问题、旁路和功能建议。这是一个公共代码托管平台,广泛用于开源项目协作,便于开发者和用户进行沟通和问题管理。作者还提到请用户在GitHub上发布问题而不是在评论区留下不好的评论,这体现了良好的社区维护和用户交流的实践。 6. 软件标签: “pocketmine”和“anticheat”(反作弊)作为标签,说明Mockingbird是一个特别为PocketMine-MP平台开发的反作弊软件。而“PHP”则可能指的是Mockingbird的开发语言,虽然这个信息与常见的Java或C++等开发Minecraft相关软件的语言不同,但并不排除使用PHP进行服务器端开发的可能性,尤其是对于处理动态网页、服务器端脚本等场景。 7. 压缩包文件: “Mockingbird-stable”是一个文件名称,很可能表示这是一个包含最新稳定版Mockingbird反作弊系统的压缩包。通常,这样的文件名中包含“stable”意味着这是一个经过充分测试且推荐用于生产环境的版本。 8. 社区协作和用户参与: 特别感谢部分提到了shur,这可能是对某位贡献者或社区成员的感激之情。这种感谢表明了软件开发不仅是开发者个人的劳动成果,同时也依赖于社区的支持和参与,包括提供反馈、报告问题、贡献代码和文档等。 总结以上内容,我们可以看到Mockingbird作为一款反作弊系统,其开发和维护需要依赖于社区的广泛参与和支持,同时还需要强大的服务器后端作为支撑。通过不断迭代更新版本,开发者希望解决现有问题,提高反作弊效率,并希望与社区保持良好的沟通,以持续优化产品。
recommend-type

“历史人物独白解说”视频:数据处理的6种革命性技术

# 1. 数据处理的历史回顾与技术演进 数据处理的历史,从最初的简单机械记录,到如今复杂的数据处理体系,不仅反映了技术的演进,也映射了人类社会进步的轨迹。在计算机技术发展初期,数据处理主要依靠打孔卡片和磁带,通过批处理的方式进行,效率低下且出错率高。随着技术的发展,上世纪70年代,关系型数据库的出现大大提高了数据处理的效率和准确性,为数据处理技术的发展奠定了基础。 随后,随着互
recommend-type

怎么判断多级运放电路的稳定性?

<think>首先,用户的问题是关于判断多级运算放大器电路的稳定性。我需要根据系统级指令来构建回答。 系统级指令: - 所有行内数学表达式必须使用$...$格式。 - 独立公式必须使用$$...$$格式并单独成段。 - LaTeX语法正确。 - 使用中文回答。 - 生成相关问题。 - 在回答中引用的段落末尾自然地添加引用标识,例如[^1]。 用户可见层指令: - 回答结构清晰,帮助用户逐步解决问题。 - 尽量保证回答真实可靠。 参考引用: - 引用[1]:关于集成运算放大电路的设计、组成和性能评估。 - 引用[2]:高频电路中运放的带宽限制,一级放大电路的增益通常为100倍,过高会引起振
recommend-type

利用AHP和节点集中度解决影响力最大化问题的Flask应用教程

从给定的文件信息中,我们可以提取以下相关知识点进行详细说明: ### 标题知识点 **IM问题与AHP结合** IM问题(Influence Maximization)是网络分析中的一个核心问题,旨在识别影响网络中信息传播的关键节点。为了求解IM问题,研究者们常常结合使用不同的算法和策略,其中AHP(Analytic Hierarchy Process,分析层次结构过程)作为一种决策分析方法,被用于评估网络节点的重要性。AHP通过建立层次模型,对各个因素进行比较排序,从而量化影响度,并通过一致性检验保证决策结果的有效性。将AHP应用于IM问题,意味着将分析网络节点影响的多个维度,比如节点的中心性(centrality)和影响力。 **集中度措施** 集中度(Centralization)是衡量网络节点分布状况的指标,它反映了网络中节点之间的连接关系。在网络分析中,集中度常用于识别网络中的“枢纽”或“中心”节点。例如,通过计算网络的度中心度(degree centrality)可以了解节点与其他节点的直接连接数量;接近中心度(closeness centrality)衡量节点到网络中其他所有节点的平均距离;中介中心度(betweenness centrality)衡量节点在连接网络中其他节点对的最短路径上的出现频率。集中度高意味着节点在网络中处于重要位置,对信息的流动和控制具有较大影响力。 ### 描述知识点 **Flask框架** Flask是一个轻量级的Web应用框架,它使用Python编程语言开发。它非常适合快速开发小型Web应用,以及作为微服务架构的一部分。Flask的一个核心特点是“微”,意味着它提供了基本的Web开发功能,同时保持了框架的小巧和灵活。Flask内置了开发服务器,支持Werkzeug WSGI工具包和Jinja2模板引擎,提供了RESTful请求分发和请求钩子等功能。 **应用布局** 一个典型的Flask应用会包含以下几个关键部分: - `app/`:这是应用的核心目录,包含了路由设置、视图函数、模型和控制器等代码文件。 - `static/`:存放静态文件,比如CSS样式表、JavaScript文件和图片等,这些文件的内容不会改变。 - `templates/`:存放HTML模板文件,Flask将使用这些模板渲染最终的HTML页面。模板语言通常是Jinja2。 - `wsgi.py`:WSGI(Web Server Gateway Interface)是Python应用程序和Web服务器之间的一种标准接口。这个文件通常用于部署到生产服务器时,作为应用的入口点。 **部署到Heroku** Heroku是一个支持多种编程语言的云平台即服务(PaaS),它允许开发者轻松部署、运行和管理应用。部署Flask应用到Heroku,需要几个步骤:首先,创建一个Procfile文件,告知Heroku如何启动应用;其次,确保应用的依赖关系被正确管理,通常通过一个requirements.txt文件列出所有依赖;最后,使用Git将应用推送到Heroku提供的仓库,Heroku会自动识别Procfile并开始部署过程。 ### 标签知识点 **HTML** HTML(HyperText Markup Language,超文本标记语言)是用于创建网页和Web应用的标准标记语言。它定义了网页的结构和内容。HTML文件由一系列元素组成,这些元素通过标签(tags)来表示,如`<p>`代表段落,`<a>`代表链接,`<img>`代表图像等。HTML5是当前使用的最新版本,支持更多的特性,如离线存储、多媒体和图形等。 ### 压缩包子文件的文件名称列表知识点 **IMproblem-using-AHP-and-centralisation-of-nodes-master** 这里的文件名称“IMproblem-using-AHP-and-centralisation-of-nodes-master”表明了一个GitHub仓库的名称,其中包含了源代码以及与项目相关的所有文件。从名称中可以看出,该仓库是关于如何结合AHP和节点集中度分析来解决IM问题的Flask应用程序。文件名中的“master”表明这是仓库的主分支(现在叫做main分支),它是项目最新的、可部署的代码版本。 综合来看,本段信息为我们提供了构建和部署一个使用Flask框架、针对IM问题使用AHP和节点集中度分析的Web应用的方法和步骤。同时,介绍了应用在不同环节中所需技术和组件的详细知识点。
recommend-type

视频内容自动生成算法:突破性的8大最新进展

# 1. 视频内容自动生成算法概述 ## 算法发展背景 随着人工智能技术的迅速发展,视频内容自动生成算法已经成为媒体和娱乐行业的重要工具。这些算法能够自动编辑和合成视频内容,使内容创作者能够以较低的成本和时间生成高质量的视频。从社交媒体动态到在线教育内容,视频内容自动生成的应用场景正在不断扩大。 ## 核心技术简述 视