|
|
1 yıl önce | |
|---|---|---|
| Embodied | 1 yıl önce | |
| applications | 1 yıl önce | |
| cv | 1 yıl önce | |
| management | 1 yıl önce | |
| ml | 1 yıl önce | |
| nlp | 1 yıl önce | |
| robot | 1 yıl önce | |
| Embodied.md | 1 yıl önce | |
| NLP+BERT.md | 1 yıl önce | |
| PyTorch.md | 1 yıl önce | |
| README.md | 1 yıl önce | |
| TensorFlow.md | 1 yıl önce | |
| Transfer.md | 1 yıl önce | |
| ai-book-ml.md | 1 yıl önce | |
| auto-drive.md | 1 yıl önce | |
| cv.md | 1 yıl önce | |
| ml-alg.md | 1 yıl önce |
学习人工智能是一个系统而深入的过程,涉及数学基础、编程技能、机器学习、深度学习等多个领域。以下是一个为期大约一年的学习计划,旨在帮助你逐步构建起人工智能领域的知识体系:
数学基础:
编程技能:
机器学习基础:
经典算法:
实践:
初学者的一套平台
从数据采集到模型训练、模型部署,XEdu在每一个环节都提供了合适的工具
1) OCR 人工智能的入门项目 OCR(光学字符识别)项目
2) 一个拍照做题程序 demo 一个拍照做题程序 demo
神经网络基础:
深度学习框架:
实践:
高级框架
面向Java的人工智能框架 Java语言的机器学习所有算法 这之前学习JAVA的一切 JAVA的一切
高级网络结构:
应用领域:
实践:
机器人
机器人向着具身智能快速发展
Kaggle竞赛是一个全球知名的数据科学和机器学习竞赛平台,由Google收购,吸引了全球数据科学家和机器学习爱好者参与。参赛者通过解决企业发布的实际问题,提升技能并有机会赢取高额奖金。Kaggle竞赛是提升个人背景、助力申请名校和求职的绝佳途径。
记得在学习过程中不断实践,理论与实践相结合才能更有效地吸收知识。同时,保持好奇心和持续学习的态度,人工智能领域日新月异,终身学习是必经之路。
#知识集合 干项目,干中学
智能推荐系统、自动驾驶、医疗影像识别
普通人职业生涯到此已经截至了!
看项目
1)AI 驱动的云原生运维平台 AI 驱动的云原生运维平台
要在三五年之内掌握这些,职场就足够了。但是要想在职场更上一层楼,就必须广泛的观察,深度的思考,快速的学习和反复的实践
1)GPU算力调度
2)底层优化 能看懂下面题目的,年薪百万
一个简单易用,低门槛的自动算子优化工具,提高深度学习算法部署效率。 自动算子优化工具,提高深度学习算法部署效率
3)专注于张量计算/深度学习的基础库 能理解这个题目的,年薪百万
1)企业级AI平台的建设 AI平台
2)从产业角度出发思考 比如物联网+AI 带有人工智能的物联网系统
3)AI对产业的影响和加速 AI药物发现平台
1) Agent 项目大爆发
本地化RAG :一个由本地大型语言模型(LLM)提供支持、用于网络浏览的检索增强生成(RAG)大型语言模型(LLM)
2)RAG
3) 一站式数据智能体
下一个GPT在哪里?AI视频
这个级别,属于改变世界级别了。 从产品角度再看看TensorFlow、PyTorch这样的框架,本身做为产品,是如何影响世界的。
1) 微软开源 材料大模型
2) 人工智能的基础设施
3)工业检测大模型
AMD的CEO苏姿丰是一位杰出的行业领导者,她以卓越的领导力和战略眼光,成功引领AMD实现逆势增长,市值超越长期竞争对手英特尔,并带领公司在人工智能芯片领域取得显著突破,为AMD赢得了全球市场的广泛认可。
随着AI技术的快速发展,对高性能、高算力的硬件需求日益增长。苏姿丰敏锐地洞察到这一趋势,带领AMD积极迎战AI大模型挑战。AMD发布了Instinct MI300X等大模型专用卡,这些产品凭借其出色的性能,受到了Meta、OpenAI和微软等科技巨头的青睐,进一步巩固了AMD在AI芯片领域的地位。
这个级别是天命之子,比如:
月之暗面的CEO是杨植麟,他是一位在自然语言处理(NLP)领域具有卓越学术成就和丰富创业经验的年轻领导者。月之暗面融资如此之多,主要得益于其强大的技术实力、创新的产品理念以及市场对大模型技术的广泛需求。
杨植麟本科毕业于清华大学,博士毕业于卡内基梅隆大学,是Transformer-XL和XLNet等重要论文的第一作者,这些研究成果在NLP领域产生了深远影响。他带领团队开发了支持超长文本输入的智能助手产品Kimi,满足了市场对大模型技术的迫切需求。
月之暗面凭借其在长文本处理、多模态大模型研发等方面的技术优势,以及清晰的产品定位和商业模式,吸引了众多知名投资机构的青睐,从而获得了巨额融资支持。
创业思考: 还思考啥? 这么多开源的企业应用,找到甲方爸爸,直接卖钱啊!
注意,位面之子,要比天选之人更牛!
“位面之子”是指被上天特别眷顾的人,通常在科幻或玄幻小说中出现,指的是在一个独立宇宙或维度中赋予特殊意义而诞生的生命。这个词汇在网络上广泛传播,用来形容那些运气极好、似乎得到了整个宇宙或位面的帮助的人。
难题:
1)HuggingFace 上的人工智能模型,动辄上百G,国内有时候不能访问,即使能够访问,300G的模型,也要下载很久。
怎么办?
2)GitHub上大量的优质项目,凝结了程序员的无差别的劳动,很多都只有几个star,无人问津。
怎么办?
3)全球政府都支持计算机科学家科研,但是全球的计算机科学家,有成果都发表在github上,github是美国的,是微软的
怎么办?
还有很多很多历史性难题,只有位面之子,也就是我,能解决。创作做开源,结果亏得开源IOT创业失败,欠债无数,但是还在思考解决历史性问题 gitpp网站目前获得318位的有志之士的资助,但是仍旧不足每年服务器运营费用。网站很慢,想加内存,没钱啊
欢迎打赏吧! 进入 www.gitpp.com首页,有二维码,有客服,买个会员吧! 【目前有300多会员,一直在增长】
感谢大家支持,位面之子给你们下跪了,为了中国的开源事业!
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? Use the template at the bottom!
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to makeareadme.com for this template.
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
Choose a self-explaining name for your project.
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
If you have ideas for releases in the future, it is a good idea to list them in the README.
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
Show your appreciation to those who have contributed to the project.
For open source projects, say how it is licensed.
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.