Applied Non Linear Control_听课笔记1--《应用非线性控制》

最新推荐文章于 2024-09-26 19:08:48 发布
原创 最新推荐文章于 2024-09-26 19:08:48 发布 · 置顶 · 2.7k 阅读 · 21 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

最低0.47元/天 解锁文章
Applied Non Linear Control_听课笔记2--《应用非线性控制》
chepwavege的专栏
09-23 1776
书本阅读难度： 1---较容易 ， 注意书本的编排顺序和课堂不一样，注意对照，建议授课顺序。 课堂听课难度： 2---一般（授课水平个人感觉一般）--前面可能略枯燥，需要2-3节课适用风格。其实总体还是很专业的。 Lecture1_intro:（课堂1） 系统稳定与否？ ，用高等数学，极限的定义来说明，系统方程 收敛与否， 能够收敛到我们期待的工作区间，就是稳定的。（李亚普诺夫对于稳...
应用非线性控制
05-07
本书系统介绍了现代非线性系统的控制理论，以及这些理论在实际非线性控制系统设计中的应用。
Applied Nonlinear Control
04-03
应用非线性控制，英文原版教科书，经典教材，有相应的中文版。
应用非线性控制（applied nonlinear control_slotine)/MIT经典教材
ccJun-的博客
04-07 9156
注，本文转载自http://muchong.com/t-6827996-1。 书籍资源：点击这里下载电子图书。 如果可以翻墙，去youtube看音频和视频质量好一些，下面是原作者整理分享的网盘资源，在此表示感谢！ 新年第一帖，MIT2013年秋Slotine非线性控制系统讲课视频，前十三讲，based on the outstanding textbook 《Applied Nonline...
APPLIED NONLINEAR CONTROL
02-23
Applied Nonlinear Control-J.E.Slotine 经典非线性控制英文教材，初学者必备
非线性系统课后习题答案英文版
06-25
非线性系统习题答案，英文版，中文版没找到，部分答案没有
nonlinear programming Dimitri P.B solution
11-16
nonlinear programming Dimitri P.B solution
非线性系统经典教材
01-23
非线性系统中文翻译第三版，哈森.哈里尔著。。。。。。
非线性控制
greatzls的博客
03-07 404
目录 Introduction Introduction some basic concept unforced system aotunomous system-----time invariant system Equilibrium point/Working point/train point single equilibrium continuous multiple isolated equilibrium Taylor expansion 近似线性化 abnorm.
【免费下载】 应用非线性控制（完整版 程代展中文译本）
gitblog_06625的博客
09-26 1488
应用非线性控制（完整版 程代展中文译本） 【下载地址】应用非线性控制.pdf_0 应用非线性控制（完整版 程代展中文译本） 项目地址: https://gitcode.com/Open-source-documentation-t...
非线性控制理论：理解和应用
AI天才研究院
01-08 5307
1.背景介绍 非线性控制理论是一种控制理论的分支，主要关注于非线性系统的控制。非线性系统在现实生活中非常普遍，例如机械系统、生物系统、电气系统等。由于非线性系统的特性，传统的线性控制理论在处理非线性系统时效果有限。因此，非线性控制理论诞生，为处理非线性系统提供了一种有效的方法。 非线性控制理论的研究内容包括非线性系统的模型建立、控制法则的设计以及控制算法的实现等。非线性控制理论的研究具有广泛的...
非线性控制策略：比较与应用
AI天才研究院
12-27 1125
1.背景介绍 非线性控制策略是一种在控制系统中广泛应用的方法，用于解决线性控制策略无法处理的复杂问题。在许多实际应用中，系统的动态特性往往是非线性的，这使得线性控制策略在这些应用中的效果不佳。因此，研究和开发非线性控制策略至关重要。 非线性控制策略的研究历史悠久，可以追溯到20世纪50年代，当时的科学家们开始关注非线性系统的控制问题。自那时以来，非线性控制策略的研究得到了广泛的关注和应用，包括...
mysql> SELECT * FROM performance_schema.replication_applier_status_by_worker \G *************************** 1. row *************************** CHANNEL_NAME: WORKER_ID: 1 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752528 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.872259 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.872259 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:07:20.962510 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:07:20.964174 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 2. row *************************** CHANNEL_NAME: WORKER_ID: 2 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752527 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.871746 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.871746 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:07:20.961392 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:07:20.963864 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 3. row *************************** CHANNEL_NAME: WORKER_ID: 3 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 1062 LAST_ERROR_MESSAGE: Worker 3 failed executing transaction '5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752529' at master log mysql_bin.040867, end_log_pos 15254660; Could not execute Write_rows event on table kk_control.control_site_venue_bet_statistics; Duplicate entry '2025-09-29-5-28-TY' for key 'control_site_venue_bet_statistics.unique_index', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log mysql_bin.040867, end_log_pos 15254660 LAST_ERROR_TIMESTAMP: 2025-10-04 08:07:20.962997 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752516 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.807107 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.807107 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:07:20.785319 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:07:20.787189 APPLYING_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752529 APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.874823 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.874823 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:07:20.962589 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 4. row *************************** CHANNEL_NAME: WORKER_ID: 4 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752456 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.660213 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.660213 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:07:20.707483 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:07:20.708907 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 5. row *************************** CHANNEL_NAME: WORKER_ID: 5 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752459 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.664357 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.664357 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:07:20.708929 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:07:20.711737 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 6. row *************************** CHANNEL_NAME: WORKER_ID: 6 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241748791 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:06:02.424222 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:06:02.424222 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:06:02.412803 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:06:02.413778 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 7. row *************************** CHANNEL_NAME: WORKER_ID: 7 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241748792 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:06:02.424239 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:06:02.424239 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:06:02.412833 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:06:02.413784 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 8. row *************************** CHANNEL_NAME: WORKER_ID: 8 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241748686 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:06:02.304209 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:06:02.304209 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:06:02.292898 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:06:02.293895 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 8 rows in set (0.00 sec) mysql>
最新发布
10-05
在MySQL复制架构中，错误1062表示插入重复键值，此次是Worker 3执行事务'5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752529'时，在表`kk_control.control_site_venue_bet_statistics`的`unique_index`键上出现了重复条目'2025-09-29-5-28-TY'。以下是几种解决方法： #### 检查并删除重复数据 在从库上执行以下查询，确认重复数据是否存在： ```sql SELECT * FROM kk_control.control_site_venue_bet_statistics WHERE unique_index = '2025-09-29-5-28-TY'; ``` 如果存在重复数据，可以使用`DELETE`语句删除： ```sql DELETE FROM kk_control.control_site_venue_bet_statistics WHERE unique_index = '2025-09-29-5-28-TY'; ``` #### 跳过错误事务 在从库上停止复制，设置跳过计数器，然后重新启动复制： ```sql STOP SLAVE; SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1; START SLAVE; ``` #### 调整唯一键约束 如果确定该重复数据是正常情况，可以考虑调整表的唯一键约束。例如，移除或修改唯一键： ```sql -- 移除唯一键 ALTER TABLE kk_control.control_site_venue_bet_statistics DROP INDEX unique_index; -- 修改唯一键 ALTER TABLE kk_control.control_site_venue_bet_statistics DROP INDEX unique_index; ALTER TABLE kk_control.control_site_venue_bet_statistics ADD UNIQUE (column1, column2); ``` #### 重新初始化从库 若上述方法无法解决问题，可以重新初始化从库。步骤如下： 1. 在主库上创建备份： ```bash mysqldump -u root -p --all-databases --master-data=2 > backup.sql ``` 2. 在从库上停止复制： ```sql STOP SLAVE; ``` 3. 清空从库数据： ```sql DROP DATABASE kk_control; CREATE DATABASE kk_control; ``` 4. 将主库备份恢复到从库： ```bash mysql -u root -p < backup.sql ``` 5. 配置从库复制： ```sql CHANGE MASTER TO MASTER_HOST='master_host', MASTER_USER='replication_user', MASTER_PASSWORD='replication_password', MASTER_LOG_FILE='mysql_bin.xxxxxx', MASTER_LOG_POS=xxxxxx; START SLAVE; ```
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值