Java Python COMP0035 Coursework 01 2024 Coursework specification 1. Table of contents
Introduction Coursework specification
Getting started
General requirements and constraints Section 1: Data exploration and preparation Section 2: Database design and creation Section 3: Tools
Section 4: References
Submission Marking
Module learning outcomes Mark allocation
Grading criteria
Appendices
Code quality
Code that does not fully function Guidance on Moodle
Version: 1. 28/09/24
2. Introduction
The aim of the combined coursework in this module is for you to select and apply some of the relevant software development and data science techniques that are used in a typical project lifecycle.
Coursework 1 focuses on data preparation and database design.
Coursework 2 continues from coursework 1, focusing on requirements, application design and testing.
This document specifies coursework 1 which is worth 40% of the assessment marks available for the module. This is an individual coursework.
You will submit a written report; and a repository of code files that combined meet the requirements detailed in this specification.
Aim to make progress each week of first five weeks of the module, in line with module’s teaching activities.
3. Coursework specification 3.1. Getting started
1. Select a dataset using the ‘group’ selection task in Moodle Week 1 (https://moodle.ucl.ac.uk/mod/ choicegroup/view.php?id=6089982). Each ‘group’ option is associated with a data set. ‘Group selection’ is a Moodle term for the type of task, the coursework is individual.
2. Accept a GitHub classroom assignment. This creates the repository. Instructions are also given in Tutorial 1.
1. Login to GitHub.com.
2. Click on the GitHub classroom link (https://classroom.github.com/a/zqVIaThf) 3. Accept the assignment.
4. If prompted, accept to join the comp0035-ucl organisation.
Page 1 of 10
3. Download the dataset for your group choice and add it to your repository. Use the links in Moodle (Resources > Datasets). For files > 25MB use GitHub large file storage (https://docs.github.com/ en/repositories/working-with-files/managing-large-files/about-git-large-file-storage).
3.2. General requirements and constraints
• Compile all written work into a single report in either PDF or Markdown format. Name the document coursework1.
• The report supports the code and techniques used in the coursework. It is not an essay, be succinct. There are no word limits.
• Demonstrate regular use of source code control using GitHub. Create the repository using the GitHub classroom assignment. Keep the repository private. Keep the repository in the ucl- comp0035 organisation.
• You must use the data set allocated to you on Moodle.
• This is an individual coursework. Do not collude with other students using the same data set.
• Use of code AI tools is permitted when writing code. UCL recommends using Microsoft Copilot
(https://liveuclac.sharepoint.com/sites/Office365/SitePages/Bing-Enterprise-Chat.aspx) using your
UCL credentials. This must be stated in the ‘References’ section.
• Use relevant techniques from the course, or from data science and/or software engineering
processes. Provide references for techniques not included in the course material.
• Diagrams can be hand-drawn and scanned. Using software to draw them does not increase marks.
3.3. Section 1: Data exploration and preparation
The purpose of this section is:
• to use python pandas to describe the data set structure and content; and as a result demonstrate that you understand the data set.
• to use python pandas prepare the data for later use in developing applications. The data you prepare will be used in COMP0034 coursework to create charts in a dashboard app.
• to demonstrate that you can write code that is reusable and understood by other developers.
• to demonstrate that you can apply relevant software engineering and data science techniques.
Code quality is also assessed.
Use only Python and pandas. matplotlib may be used where pandas DataFrame.plot() (https:// pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.plot.html) is not sufficient.
Create charts where they support your exploration and preparation; but do not focus on the visual aesthetic as this is not assessed.
You may need to prepare the data in order to complete the exploration and hence your code may not neatly split between 1.1 and 1.2. This is OK, the code structure does not need to exactly match the report structure.
3.3.1. Section 1.1 Data exploration
1. Code: Write python code to explore and describe the data structure and content. Including, but not limited to, size, attributes and their data types, statistics, distribution of the data, etc. Consider potential data quality issues.
2. Report: Describe the results of your exploration of the data. Do not include the code in the report.
3.3.2. Section 1.2 Data preparation
1. Report: Briefly describe a target audience and state at least 3 questions that they might be interested to explore using the data. This defines the purpose for which you will prepare the data.
Page 2 of 10
2. Code: Write python code to prepare the data such that it can be used to try to answer the questions for the audience described in step 1. Aim to have sufficient data, and avoid unnecessary data. The prepared data should be in a format that can be read into one or more pandas dataframes from a file (.csv or .xlsx). If relevant, address any data quality issues identified in section 1.1.
3. Report: Explain how you ensured the data is relevant for the purpose.
4. Include the original and prepared versions of your data set files in your repository.
3.4. Section 2: Database design and creation
The purpose of this section is:
• to demonstrate that you understand the structure of a relational database and the principles of normalisation by designing an appropriate database and drawing this as an entity relationship diagram (ERD).
• to demonstrate that you can write Python code to create an SQLite database based on the ERD. The database you create can be used in COMP0034 coursework in a data driven web application.
3.4.1. Section 2.1: Database design
Design a relational database that can store the data (based on either the prepared or the raw data set, your choice). Consider normalisation.
Document the design as an Entity Relationship Diagram (ERD) that includes the following details as a minimum:
• table(s)
• attributes in each table
• data type of each attribute
• primary key attribute for each table • foreign key attribute(s) if relevant
• relationship lines between tables
Include the ERD in your report. An explanation is not required, though you may discuss your normalisation if relevant.
3.4.2. Section 2.2: Database code
Write python code that:
• creates a database structure based on the ERD for an SQLite database file.
• takes the data from the dataset file and saves it to the SQLite database file. Note: do not create a
database that requires a server such as MySQL or PostgresSQL. The quality of the code is assessed.
Use relevant Python packages, i.e. pandas and sqlite3.
3.5. Section 3: Tools
The purpose of this section is to demonstrate appropriate and effective use of relevant software engineering tools.
Page 3 of 10
3.5.1. Section 3.1 Environment management
Provide relevant files and instructions that allow the marker to set up and run your code in a Python virtual environment. They will use pip and setuptools with the commands:
pip install -r requirements.txt
pip install -e .
As a minimum, edit the files that were provided in the starter code of the repository:
• requirements.txt: list the packages used in your code
• pyproject.toml: provide basic project details and code package location
• README.md: provide instructions to install and run your code for the data preparation and the
database creation
3.5.2. Section 3.2: Source code control
Add the URL for your repository to the report. Make regular use of source code control.
3.5.3. Section 3.3: Linting
Use a Python linter to demonstrate how your code meets Python style standards such as PEP8, PEP257. For example:
• state which Python linter you used.
• provide evidence of the results of running the linter.
• if issues are reported by the linter, address these and then run the linter again and show the results. • if any issue cannot be addressed, explain why not.
3.6. Section 4: References
Include code references in comments in the code files close to where it is used. Include all other references, if used, in the report.
3.6.1. Section 4.1 Reference use of AI
State either that you used AI, or state that you did not.
If you used AI, include the details stated in the UCL guidance (https://library-guides.ucl.ac.uk/ referencing-plagiarism/acknowledging-AI#s-lg-box-wrapper-19164308).
3.6.2. Section 4.1 Dataset attribution
Comply with any license condition required for your data set (given in the data set link in Moodle > Resources > Data sets).
Each license is different and tells you what has to be cited; e.g. see open government licence v3 (https:// www.nationalarchives.gov.uk/doc/open-government-licence/version/3/). Typically, but not always, ‘attribution’ is required: i.e. include a statement listing who owns the data and its location.
Page 4 of 10
4. Submission
Refer to Moodle > Assessment for the deadline date and time.
Submit your work on Moodle in the assignment submission. The submission states the upload format:
.zip for the code (and report if in markdown) plus .pdf for the report (if not in markdown).
GitHub is not an acceptable alternative for submission, though its facility to download the code files as
zip may be useful to you.
Make sure all files are in the submission. URLs linking to external files cannot be marked as they could be changed after the submission time. The only exception is where the original data files are too large to upload to Moodle - in this exceptional situation list url(s) to the data files in your report or the README.md instead.
Do not include your .venv folder in the zip file, this creates unnecessarily large zip files. Table: Submission checklist
Section Report Code files
1. Data exploration and preparation
Description and explanation.
Python code to explore/describe the data. Python code to prepare the data.
Original data set
Prepared dataset
2. Database design and creation
Entity Relationship Diagram (ERD).
Python code to create COMP0035、 python the database. SQLite database file.
3. Tools
Source code control: URL to GitHub repository Linting evidence.
Environment management: requirements.txt, pyproject.toml, README.md
4. References
Statement of AI use.
Data set attribution.
Other references if used.
Include code references within the code files.
5. Marking
5.1. Module learning outcomes
The module’s published learning outcomes that are assessed in this coursework are indicated in the table.
Page 5 of 10
Learning outcome
Coursework 1?
1. Describe how software development methodologies can be used to manage the software development process and select and apply an appropriate methodology for a given project.
2. Select and apply techniques for capturing and modelling requirements.
5. Model the design for a database. Yes
3. Select and apply techniques for modelling an application; and model an application using these.
Yes - database
4. Select the aspects of a software application can be modelled with the Unified Modelling Language (UML); and use UML to model different views of an application.
ERD (not UML)
6. Describe testing and recommend an appropriate approach to testing for a given pro ject.
7. Recognise the challenges of working in a team and organise themselves and their group to deliver a complex project.
8. Recognise the ethical implications of using data in the context of this course and be aware of their responsibilities to comply with relevant UCL and UK legislation.
Yes
9. Work in a group to apply the skills and knowledge gained in the course to: a) produce a coherent and cohesive specification for an application; and b) select, install, configure and use a set of open-source tools and use these to support the software development cycle for the application.
Yes, part (b)
The published learning outcomes are being revised. In particular:
• Data preparation and visualisation are core to the module content yet missing from the published learning outcomes.
• Following feedback from previous students, the coursework is now individual. Learning outcome 7 is not addressed; and learning outcome 9 needs to be re-worded.
5.2. Mark allocation
You are expected to spend 18 hours on coursework 1 (45 * 40%).
The weighting of each section is shown with an indication of the expected hours of effort required.
Section
Data preparation and understanding Database design and creation
Tools
5.3. Grading criteria
Weighting Effort (hours)
45% 8
35% 6
20% 3
The coursework is assessed according to the standards set in the standard UCL Computer Science grading criteria ( see copy on Moodle in the Assessment section). The criteria most relevant to this assessment are 1, 2, 4 and 5.
The following tables give the standard UCL CS criteria, and indicators specific to this coursework. The coursework is open-ended and allows for different solutions; it is not possible to describe every aspect that could be considered.
Page 6 of 10
The descriptors typically focus on quality and standard of the response, rather than quantity. If you are going to do something more (quantity), then you are advised to focus on demonstrating something that has not already been evidenced in your work.
5.3.1. Generic CS Descriptors
Grade band
Generic CS Descriptor
Distinction 90+
Exceptional response with a convincing, sophisticated argument with precise conclusions.
Exceptional grasp of complexities and significance of issues.
Exceptional thought and awareness of relevant issues. Sophisticated sense of conceptual framework in context.
Exceptional solution and advanced algorithm/technical design.
Distinction 70-89
A distinctive response that develops a clear argument and sensible conclusions, with evidence of nuance.
Thorough grasp of issues; some sophisticated insights.
Concepts deftly defined and used with some sense of theoretical context.
Excellent algorithmic solution, novel and creative approach.
Merit 60-69
A sound response with a reasonable argument and straightforward conclusions, logical conclusions.
Sound understanding of issues, with insights into broader implications.
Good solution, skilled use of concepts, mostly correct and only minor faults.
High pass 50-59
A reasonable response with a limited sense of argument and partial conclusions. Reasonable grasp of the issues and their broader implications.
Reasonable reproduction of ideas from taught materials. Rudimentary definition and use of concepts.
Reasonable solution, using basic required concepts, several flaws in implementation.
Low pass 40-49
An indirect response to the task set, towards a relevant argument and conclusions. Rudimentary, intermittent grasp of issues with confusions.
Analysis relying on the partial reproduction of ideas from taught materials. Some concepts absent or wrongly used.
Rudimentary algorithmic/technical solution, but mostly incomplete.
Page 7 of 10
5.3.2. Data preparation and understanding
Grade band
Coursework-specific indicators
Distinction 90+
Evidence beyond the earlier indicators - these solutions are distinctive and as such there is no set indication of what might be included.
Distinction 70-89
Evidence of a thorough understanding of the data. Analysis and preparation is clearly explained and decisions justified in the context of the intended purpose.
Code quality is high. Effective code structure. Effective code documentation. Error handling thorough and consistently applied.
Merit 60-69
Evidence of a good understanding of the data. Actions taken that would allow the data set to be used for the intended purpose.
Code quality mostly adheres to Python standards. Evidence of structure. Appropriate documentation. Evidence of error handling.
High pass 50-59
Evidence that the student has understood and/or prepared the data using code, though may be more limited. Decisions taken are not clearly explained. The purpose given is appropriate for the data.
Reasonable code, using basic required concepts, several flaws in implementation.
Low pass 40-49
The described purpose may not be clear and/or relate well to the given data. Insufficient evidence that the data has been described and explored. Rudimentary preparation code, but mostly incomplete.
5.3.3. Database design and creation
Grade band
Coursework-specific indicators
Distinction 90+
Evidence beyond the earlier indicators.
Distinction 70-89
ERD shows an understanding of potential issues that have been considered in the structure and the extent of the normalisation.
Code quality is high. Effective code structure. Effective code documentation. Error handling thorough and consistently applied. Data and relationships are correct in the database.
Merit 60-69
ERD is appropriate for the data given its intended use in applications. Design is clear and uses correct notation. Evidence of appropriate normalisation for the intended use. Code quality mostly adheres to Python standards. Evidence of structure. Appropriate documentation. Evidence of error handling. There may be minor issues in the data/ relationships in the database.
High pass 50-59
ERD provided and adheres to notation but may lack minor detail and/or limited evidence of the application of normalisation concepts.
Appropriate code that generates a database file with data. There may be minor issues with the code, code quality or data.
Low pass 40-49
ERD provided but may not adhere to an appropriate notation and/or misses required detail.
Code shows some understanding but may not generate a usable database file.
5.3.4. Software engineering tools
There are no generic CS criteria relating to this aspect.
Page 8 of 10
Grade band Coursework-specific indicators
Distinction 90+
Near flawless use of a range of appropriate tools. Use of tools beyond the expected tools.
Distinction 70-89
Effective to exceptional use of the expected tools.
Merit 60-69 Appropriate use of the expected tools.
‘Regular’ use of source code control is stated in section 3.3. ‘Regular’ cannot be precisely define since students work over different periods. You are expected to make progress on your coursework weekly. Commits over a period of weeks could be considered ‘regular’; commits only during a short period such as 1-2 days could not be considered ‘regular’.
6. Appendices
6.1. Code quality
This is considered as:
1. Code that is easy for others to read and understand.
2. Code that is re-usable. The focus in this IEP minor is on writing code that could be used in
applications, not simply on whether the code works.
When you are writing code consider:
• code structure, e.g. use of functions, classes, modules, packages.
• adherence to python conventions (PEP8 style guide (https://peps.python.org/pep-0008/), PEP275
docstring conventions (https://peps.python.org/pep-0257/)).
• documentation (docstrings, comments).
• error handling.
6.2. Code that does not fully function
If your code does not fully work, and you cannot ‘debug’ and fix it before submission, then in the relevant section of the coursework document state as much of the following as you can:
• What is the code that doesn’t work (e.g. a function name)
• What you think the problem may be. This shows you understand the issue even if you cannot solve
it.
• Any solutions you have tried. This shows that you understand the issue and were able to take steps
to try and resolve it.
Clear code documentation (docstrings, comments) is often useful in these situations as the marker can more easily see what you intended your code to do, even if it does not fully achieve that.
6.3. Guidance on Moodle
• Referencing: AI, Code, other (https://moodle.ucl.ac.uk/mod/page/view.php?id=6363796)
• Assessment information Q&A: support, late submission, SoRA and EC, submission date change
(https://moodle.ucl.ac.uk/mod/page/view.php?id=6363705)
• Computer science grading criteria (https://moodle.ucl.ac.uk/mod/resource/view.php?id=6089928)
High pass 50-59
Mostly appropriate use of the expected tools.
Low pass 40-49
Limited, or inappropriate, use of the expected tools.
Page 9 of 10
• Examples of previous student work (https://moodle.ucl.ac.uk/mod/page/view.php?id=6363498) • Data sets: ethics, collusion (https://moodle.ucl.ac.uk/mod/page/view.php?id=6370978)
• Academic terms (https://moodle.ucl.ac.uk/mod/page/view
相关推荐
如何处理动态语言(Python / JS)的“隐形”调用链?
本文揭示动态语言(Python/JS)中静态AST解析导致调用链“断链”的核心问题,提出通过运行时追踪补全图谱的解决方案。基于Code-Graph-RAG的cgr trace机制,分别利用pytest插件与V8 Profiler捕获真实调用路径,将动态边合并至静态图谱,并在权重体系中提升动态边优先级。实践表明,该方法可显著提升图谱覆盖率,实现“结构+行为”双视角理解代码,为MCP与Rerank系统提供可靠支持。
COMP0035 Coursework 02 specificationPython
Coursework02CourseworkGeneralandGettingstartedCourseworkcontentSubmissionMarkingModulelearningoutcomesMarkallocationGradingcriteriaAppendicesGuidanceonMoodleCodequalityCodethatdoesnotfullyfunction••。
XMind文件解析黑科技:用Python实现版本自适应读取(兼容2010-2024)
本文深入探讨了如何利用Python实现XMind文件的版本自适应解析,兼容从2010到2024年的各版本。通过分析XMind文件作为ZIP压缩包的本质,文章提供了智能探测文件内部结构(JSON或XML)并构建健壮读取逻辑的完整方案,有效解决了版本兼容性难题,并演示了将解析数据转换为PlantUML等下游应用的实战案例。
COMP0035 规定
GroupsGitHub forcontrolcontrol.PythoncodingPDF orMarkdownfor text1pandas andmatplotlibfor dataUse of AIcontent.marking.(csv/xlsx)✓ ✓the data.or if youmade.why thesereporting.project.testing.be missed.1. Datadata.pydata✓ ✓。
用LangFuse+LangChain打造可观测的AI应用:从埋点到成本监控实战
本文详细介绍了如何将开源可观测性平台LangFuse深度集成到基于LangChain构建的AI应用中,特别是电商客服机器人场景。通过从基础SDK集成、提示词管理到成本监控的完整实战,帮助开发者实现对LLM应用内部工作流的清晰追踪、问题排查与费用分析,从而打造稳定、可控的生产级AI应用。
uniapp [安卓苹果App端] - errMsg“: “request:fail abort statusCode:-1 不支持的URL(-1002)Uniapp真机运行APP网络请求报错失败排查
uniapp真机运行APP,网络请求报错errMsg“: “request:fail abort statusCode:-1 不支持的URL(-1002),uni.request网路请求报错,uniApp解决请求接口报错,uniapp app端打包上线后请求报错,真机运行测试请求失败,uniapp安卓app请求报错,uniapp苹果ios平台网络请求报错,uniapp真机预览请求失败怎么办,不是跨域问题,在H5中请求可以正常发送和接收,但在真机APP上请求报错,Hbuilder真机运行app网络请求报错,全
COMP0035 Data exploration
Appendices• table(s)3. Tools5. MarkingYesSectionTools45% 835% 620% 3。
Qwen大模型参数解析
Qwen系列模型的参数主要分为(决定模型结构)和(控制生成行为)两类。由于该系列已迭代多个版本,参数设计也在不断演进,我会结合最新版本为你进行分层梳理。
COMP0035 Data exploration and preparation
SubmissionMarkingAppendicesstructure.minimum:• table(s)tools.1. Dataand。
世界模型研究综述【20250702】
自2018年以来,世界模型研究从早期的生成式环境模型+简单控制器,发展到如今与大模型和多模态深度融合,取得了长足进展。Ha和Schmidhuber开创了让智能体“在梦中学习”的范式,随后模型式强化学习在复杂视觉任务中展现威力,如SimPLe和PlaNet将世界模型引入Atari和连续控制。Dreamer系列通过潜在空间想象将这一思路推向极致,从连续控制拓展到Atari甚至开放式3D游戏,实现了统一算法征服多领域任务的壮举。
《YOLO多模态创新改进专栏目录 》全网独家创新,多模态融合改进教程,包含早期融合、中期融合、后期融合、损失函数改进、二次创新模块、独家创新等几百种创新点改进,答疑群提供完整项目,永久更新中
🔥《YOLO多模态创新改进专栏》重磅来袭!🚀 本专栏汇集最新顶会顶刊创新点,提供1000+篇YOLO多模态改进方案(涵盖v8-v26),包含: 多模态融合策略(早期/中期/后期) 损失函数优化 独家创新模块 详细改进步骤 ✨特色服务: ✔️ 配套完整可运行项目 ✔️ 专业答疑群支持(含非计算机专业指导) ✔️ 持续更新至2026年 ✔️ 适用目标检测/OBB/分割/分类等多任务 💡适合人群: 科研人员 | 研究生 | 需发SCI/CCF论文者 环境要求宽松,新手友好,助力快速产出科研成果! 📈早订优
COMP0034 2023/24 Coursework 1 specificationPython
evidence of challenge and&nbsdai 写COMP0034 2023/24 Coursework 1 specificationPython p;
冲压机器人系列编程:ABB IRB 6700_(6).RAPID编程语言入门
主菜单:包含文件、编辑、视图、工具等常用操作。项目浏览器:显示当前项目的文件结构,包括机器人模型、程序模块等。图形界面:用于创建和编辑机器人的虚拟环境。RAPID代码编辑器:用于编写和编辑RAPID代码。仿真控制面板:用于控制仿真过程,包括启动、暂停、停止等。变量是存储数据的容器,可以通过变量名访问和修改其存储的数据。变量定义时需要指定其类型和名称。% 定义一个整数变量并赋初值% 定义一个实数变量,未赋初值函数定义时需要指定其返回类型和参数。num result;子程序类似于函数,但不返回值。
本地化部署 DeepSeek,构建单细胞与空间转录组 AI 分析平台
本地化部署 DeepSeek,构建单细胞与空间转录组 AI 分析平台
4 屏 + 8 摄像头一开,谁在悄悄拖慢你的座舱域控?
如果你觉得座舱卡顿:❌ 别第一反应怪 SoC❌ 别盲目堆算力。
锂电池充电器电路设计 里面有电路
锂电池充电器电路设计 里面有电路 3.7V升压到5V电路设计。
【第 009 讲】全面掌握 Python 注释:注释的定义与作用 | 单行注释 | 三引号与多行注释 | 注释使用的最佳实践
本文系统讲解 Python 注释的完整知识体系:从注释的定义与作用讲起,梳理单行注释的书写位置、临时屏蔽用法与 PEP 8 排版规范,剖析注释被忽略的底层机制;进而说明三引号字符串的本质与嵌套问题;最后给出注释使用的三条实践原则,帮助读者写好可读性高的注释。
C# WinForm 基于DirectShow.dll编写的程序,可边预览边保存视频,音频和图片
基于微软的DirectShow.dll的二次开发1.自动识别连接的摄像头跟麦克风且可以对其进行选择(默认选中第一个)2.可录制wmv和avi两种格式的视频并且都带有音频,avi可以录制的分辨率和帧数进行选择,wmv默认进行了淸晰度优化如不喜欢可去除代码中有相关提示3.可在预览点开之后进行拍照,也可边录制视频边拍照4.添加了视频和音频的压缩功能(酌情使用)这次二次开发发现C#对DirectShow的相关信息太少,这次做完也不敢藏私共享出来,还望大家指正
Python 的 yield from 到底转发了什么:拆开 send、throw 和那个 return 值
很多人把yield from记成「省一层 for 循环的语法糖」。写和写,结果看着一样,于是就当它只是少敲几个字。这个理解会在三个地方翻车:调用方.send()的值送不进去、子生成器return的值拿不到、异常和close()传不下去。yield from真正做的事是,外层生成器退成一个透明通道。本文所有输出来自本机 CPython 3.13.14 实测。yield from不是循环,是委托——nextsendthrowclose四个方向的流量全部直通子生成器,并且子生成器return。
计算机控制技术及应用
《计算机控制技术及应用》通过总结作者的科研成果和吸收国内外的先进理论、方法和技术,以计算机控制系统的网络化、开放化、智能化和集成化发展趋势为主线索,主要介绍计算机控制系统的基本概念和计算机控制系统的典型形式,计算机控制系统的数学描述与基本分析方法,以及数字PID控制器、最少拍控制系统、达林算法、状态变量设计法等设计方法及其各种改进算法。重点突出计算机控制系统输入输出通道接口的设计方法和典型控制系统的设计案例与实现方法等。
android 蓝牙通讯demo
android 下蓝牙通讯demo,实现了发现蓝牙,使能蓝牙,通过蓝牙发送消息。
AI全栈实战 | 3.9-01 爬虫入门:requests 加 BeautifulSoup 三分钟跑通,但 90% 的人栽在这 4 个“礼貌“问题上
⚠️:本文内容仅用于。请遵守目标站点的服务条款与相关法律法规,不得对目标服务造成负担,不得采集、传播个人隐私数据。技术是中性的,边界在你手里。爬虫的入门技术(requests 发请求 + BeautifulSoup 解析)三分钟就能学会。真正区分"会用爬虫"和"会做爬虫的人"的,是这篇我们跑通"请求→解析→存储"的最小闭环,然后重点把"合规与礼貌"这根弦给你绷上。
从一段视频到可漫游的 4D 有声场景:思路拆解与最小复现手记
只需一段手机视频,你就能生成可"走进去"的 4D 有声场景:转头时狗叫声方向随之变化,走近时声音更清晰。本文拆解 Video-to-4DAVScene 的核心思路,手把手带你用几十行 Python 搭出最小管线,把视频中的运动物体变成带空间位置的声源,并附上三个真实踩坑的排障经验,代码可直接跑。🎧
【每天一个 Python 小案例30】Python 基础知识综合小项目:我的工具盒
作为系列收官,本篇把前 29 篇的知识点合成一个能直接用的命令行工具"我的工具盒":计算器(用 ast 解析表达式,不碰 eval)、单位换算与温度转换(一张换算表 + 特例分支)、记账与分类统计(Decimal + JSON 持久化)、以及用"字典当命令表"把菜单和业务逻辑解耦的主循环。文中对比了 eval 的安全隐患与 ast 白名单的做法,解释了 lambda 闭包在字典里的写法与晚绑定陷阱,并在最后给出整个系列的知识地图,把变量、数据结构、控制流、函数、类、异常、文件、标准库八块内容对应到具体篇目。
双路径优化+双容差校准
默认使用向量化路径处理常规数据,当检测到内存非连续或需要极致短路性能时,自动切换至 Numba JIT 路径。“当 CI 宽度中位数为 $W$ 时,实际判定容差为 $10^{-12} + 10^{-9} \times W$"针对表征谱算子 2 的实际输出量纲(例如 $10^{-3}$ 至 $10^3$),调整。准确标记了哪些数组被复制。非短路、静默拷贝风险、量纲耦合容差),本方案重构了核心逻辑。,并完善审计元数据以记录内存拷贝状态。, 确保在不同量纲下判定标准的一致性。,否则需排查上游数据生成逻辑。
yolo 和 deft 算法的区别
你应该是打错了:是,不是 defrat;
两张表合并之后,行数悄悄多了一倍
pandas merge 行数异常膨胀源于右表键不唯一,导致数据静默复制。实测显示,未聚合的右表(756行)与左表合并后行数增至504行,合计膨胀3.5倍,但无报错。validate 参数仅在检查键唯一性时有效,one_to_one 和 many_to_one 可拦截问题,但需结合 duplicated() 前置检查。正确做法为先按键聚合右表,再合并,避免重复。建议合并前后核对行数、合计,并使用 indicator=True 排查匹配情况,确保数据一致性。
蓝桥杯·全国青少年信息素养大赛·电子学会Python/C++考级 备考:莫队算法离线区间查询详解
备赛进行时:第十八届蓝桥杯软件赛报名已于 2026-10-08 10:00 开启、12-18 14:00 截止,省赛定在 2027-04-10(C/C++·Python 程序设计 9:00–13:00);中国电子学会 2026 年 12 月软件编程(C/C++ 一级至十级、Python 一级至六级)考级报名 9/23–12/2 16:00、统考 12-12;全国青少年信息素养大赛 2026—2027 赛季算法应用主题赛也已进入复盘练兵窗口。
我用 200 行代码写了个“代码屎山检测器“,扫完公司的老项目后我沉默了
这个工具不能帮你把屎山铲平,但至少能让你知道自己面对的是多大的山,也能在代码评审时用数据说话——“这个 PR 把圈复杂度从 12 推到了 18,能不能拆一下?毕竟,不能量化的东西,就没法改进。
425



被折叠的 条评论
为什么被折叠?



