<?xml version="1.0" encoding="utf-8" ?><rss version="2.0"><channel><title><![CDATA[mutongyindi的博客]]></title><description><![CDATA[]]></description><link>https://blog.youkuaiyun.com/mutongyindi</link><language>zh-cn</language><generator>https://blog.youkuaiyun.com/</generator><copyright><![CDATA[Copyright &copy; mutongyindi]]></copyright><item><title><![CDATA[固态硬盘初始化]]></title><link>https://blog.youkuaiyun.com/mutongyindi/article/details/153194739</link><guid>https://blog.youkuaiyun.com/mutongyindi/article/details/153194739</guid><author>mutongyindi</author><pubDate>Mon, 13 Oct 2025 14:36:57 +0800</pubDate><description><![CDATA[​ 在 设备管理器中能识别到两块 NVMe SSD，但在文件资源管理器中看不到，很可能是因为新加的那块硬盘还没有被初始化、分区和格式化。这是 Windows 系统的正常行为 —— 只有已经格式化并分配了驱动器盘符的硬盘才会在“此电脑”中显示。如果出现了你所买的新的固态硬盘名称，则证明你安装成功，系统已正确识别你的新固态硬盘。如有本文未说明确，可进一步查看原Blog进行学习交流！完成后，这块硬盘就会在资源管理器中显示出来了。加装固态硬盘的检查与初始化工作。按住win + x 打开。文章参考csdn大佬的。]]></description><category></category></item><item><title><![CDATA[安装ubuntu 24.04双系统至固态硬盘]]></title><link>https://blog.youkuaiyun.com/mutongyindi/article/details/153188454</link><guid>https://blog.youkuaiyun.com/mutongyindi/article/details/153188454</guid><author>mutongyindi</author><pubDate>Mon, 13 Oct 2025 14:13:24 +0800</pubDate><description><![CDATA[有了 Ventoy 你就无需反复地格式化 U 盘，你只需要把镜像文件或者可引导文件直接拷贝到 U 盘里面就可以启动了，无需其他操作。安装完成重启到 Windows，发现时间慢了 12 小时，右键右下角时钟 -> 调整日期和时间 -> 立即同步 即可。Ubuntu 安装后的首次重启可以选择启动 Windows 还是 Ubuntu，默认为 Ubuntu。可以自行必应搜索各自型号修改引导顺序的方法，使对应引导方式的 U 盘引导在最前面即可。同理，要使用 Ubuntu 时，将 Ubuntu 切换至第一个即可。]]></description><category></category></item><item><title><![CDATA[Datawhale AI夏令营]]></title><link>https://blog.youkuaiyun.com/mutongyindi/article/details/149602561</link><guid>https://blog.youkuaiyun.com/mutongyindi/article/details/149602561</guid><author>mutongyindi</author><pubDate>Thu, 24 Jul 2025 13:45:42 +0800</pubDate><description><![CDATA[模型微调。]]></description><category></category></item><item><title><![CDATA[day50]]></title><link>https://blog.youkuaiyun.com/mutongyindi/article/details/149109693</link><guid>https://blog.youkuaiyun.com/mutongyindi/article/details/149109693</guid><author>mutongyindi</author><pubDate>Fri, 04 Jul 2025 09:01:36 +0800</pubDate><description><![CDATA[【代码】day50。]]></description><category></category></item><item><title><![CDATA[day49]]></title><link>https://blog.youkuaiyun.com/mutongyindi/article/details/149086670</link><guid>https://blog.youkuaiyun.com/mutongyindi/article/details/149086670</guid><author>mutongyindi</author><pubDate>Thu, 03 Jul 2025 09:12:57 +0800</pubDate><description><![CDATA[【代码】day49。]]></description><category></category></item><item><title><![CDATA[day48]]></title><link>https://blog.youkuaiyun.com/mutongyindi/article/details/149062180</link><guid>https://blog.youkuaiyun.com/mutongyindi/article/details/149062180</guid><author>mutongyindi</author><pubDate>Wed, 02 Jul 2025 09:24:30 +0800</pubDate><description><![CDATA[··]]></description><category></category></item><item><title><![CDATA[day47]]></title><link>https://blog.youkuaiyun.com/mutongyindi/article/details/149038709</link><guid>https://blog.youkuaiyun.com/mutongyindi/article/details/149038709</guid><author>mutongyindi</author><pubDate>Tue, 01 Jul 2025 09:04:55 +0800</pubDate><description><![CDATA[【代码】day47。]]></description><category></category></item><item><title><![CDATA[day46]]></title><link>https://blog.youkuaiyun.com/mutongyindi/article/details/149012908</link><guid>https://blog.youkuaiyun.com/mutongyindi/article/details/149012908</guid><author>mutongyindi</author><pubDate>Mon, 30 Jun 2025 09:08:32 +0800</pubDate><description><![CDATA[【代码】day45。]]></description><category></category></item><item><title><![CDATA[day 45]]></title><link>https://blog.youkuaiyun.com/mutongyindi/article/details/148984440</link><guid>https://blog.youkuaiyun.com/mutongyindi/article/details/148984440</guid><author>mutongyindi</author><pubDate>Sun, 29 Jun 2025 00:07:45 +0800</pubDate><description><![CDATA[【代码】day 45。]]></description><category></category></item><item><title><![CDATA[day44]]></title><link>https://blog.youkuaiyun.com/mutongyindi/article/details/148983260</link><guid>https://blog.youkuaiyun.com/mutongyindi/article/details/148983260</guid><author>mutongyindi</author><pubDate>Sat, 28 Jun 2025 22:38:24 +0800</pubDate><description><![CDATA[【代码】day44。]]></description><category></category></item><item><title><![CDATA[day43]]></title><link>https://blog.youkuaiyun.com/mutongyindi/article/details/148942898</link><guid>https://blog.youkuaiyun.com/mutongyindi/article/details/148942898</guid><author>mutongyindi</author><pubDate>Fri, 27 Jun 2025 09:09:10 +0800</pubDate><description><![CDATA[【代码】day43。]]></description><category></category></item><item><title><![CDATA[day42]]></title><link>https://blog.youkuaiyun.com/mutongyindi/article/details/148918503</link><guid>https://blog.youkuaiyun.com/mutongyindi/article/details/148918503</guid><author>mutongyindi</author><pubDate>Thu, 26 Jun 2025 09:37:06 +0800</pubDate><description><![CDATA[【代码】day42。]]></description><category></category></item><item><title><![CDATA[day41]]></title><link>https://blog.youkuaiyun.com/mutongyindi/article/details/148890235</link><guid>https://blog.youkuaiyun.com/mutongyindi/article/details/148890235</guid><author>mutongyindi</author><pubDate>Wed, 25 Jun 2025 09:12:50 +0800</pubDate><description><![CDATA[··]]></description><category></category></item><item><title><![CDATA[day 40]]></title><link>https://blog.youkuaiyun.com/mutongyindi/article/details/148860261</link><guid>https://blog.youkuaiyun.com/mutongyindi/article/details/148860261</guid><author>mutongyindi</author><pubDate>Tue, 24 Jun 2025 08:52:11 +0800</pubDate><description><![CDATA[【代码】day 40。]]></description><category></category></item><item><title><![CDATA[day 39]]></title><link>https://blog.youkuaiyun.com/mutongyindi/article/details/148838495</link><guid>https://blog.youkuaiyun.com/mutongyindi/article/details/148838495</guid><author>mutongyindi</author><pubDate>Mon, 23 Jun 2025 08:55:42 +0800</pubDate><description><![CDATA[【代码】day 39。]]></description><category></category></item><item><title><![CDATA[day38]]></title><link>https://blog.youkuaiyun.com/mutongyindi/article/details/148810070</link><guid>https://blog.youkuaiyun.com/mutongyindi/article/details/148810070</guid><author>mutongyindi</author><pubDate>Sat, 21 Jun 2025 14:16:08 +0800</pubDate><description><![CDATA[【代码】day38。]]></description><category></category></item><item><title><![CDATA[day37]]></title><link>https://blog.youkuaiyun.com/mutongyindi/article/details/148782152</link><guid>https://blog.youkuaiyun.com/mutongyindi/article/details/148782152</guid><author>mutongyindi</author><pubDate>Fri, 20 Jun 2025 09:38:09 +0800</pubDate><description><![CDATA[早停。]]></description><category></category></item><item><title><![CDATA[day 36]]></title><link>https://blog.youkuaiyun.com/mutongyindi/article/details/148758771</link><guid>https://blog.youkuaiyun.com/mutongyindi/article/details/148758771</guid><author>mutongyindi</author><pubDate>Thu, 19 Jun 2025 09:28:26 +0800</pubDate><description><![CDATA[复习日。]]></description><category></category></item><item><title><![CDATA[day 35]]></title><link>https://blog.youkuaiyun.com/mutongyindi/article/details/148730930</link><guid>https://blog.youkuaiyun.com/mutongyindi/article/details/148730930</guid><author>mutongyindi</author><pubDate>Wed, 18 Jun 2025 09:02:55 +0800</pubDate><description><![CDATA[一、模型结构可视化理解一个深度学习网络最重要的2点：了解损失如何定义的，知道损失从何而来----把抽象的任务通过损失函数量化出来了解参数总量，即知道每一层的设计才能退出—层设计决定参数总量为了了解参数总量，我们需要知道层设计，以及每一层参数的数量。下面介绍1几个层可视化工具：1.1 nn.model自带的方法。]]></description><category></category></item><item><title><![CDATA[day34]]></title><link>https://blog.youkuaiyun.com/mutongyindi/article/details/148708062</link><guid>https://blog.youkuaiyun.com/mutongyindi/article/details/148708062</guid><author>mutongyindi</author><pubDate>Tue, 17 Jun 2025 09:19:00 +0800</pubDate><description><![CDATA[数据传输开销 (CPU 内存 <-> GPU 显存)在 GPU 进行任何计算之前，数据（输入张量 X_train、y_train，模型参数）需要从计算机的主内存 (RAM) 复制到 GPU 专用的显存 (VRAM) 中。当结果传回 CPU 时（例如，使用 loss.item() 获取损失值用于打印或记录，或者获取最终预测结果），数据也需要从 GPU 显存复制回 CPU 内存。对于少量数据和非常快速的计算任务，这个传输时间可能比 GPU 通过并行计算节省下来的时间还要长。]]></description><category></category></item></channel></rss>