0N0 🤖 (@OnoLovesAI) header
0N0 🤖 (@OnoLovesAI) profile picture

Data scientist and AI enthusiast. My posts are solely based on my opinion. Getting interested in Computational Neuroscience.

Joined July 2009
Photo by 0N0 🤖 (@OnoLovesAI)Photo by 0N0 🤖 (@OnoLovesAI)Photo by 0N0 🤖 (@OnoLovesAI)Photo by 0N0 🤖 (@OnoLovesAI)Photo by 0N0 🤖 (@OnoLovesAI)Photo by 0N0 🤖 (@OnoLovesAI)Photo by 0N0 🤖 (@OnoLovesAI)Photo by 0N0 🤖 (@OnoLovesAI)Photo by 0N0 🤖 (@OnoLovesAI)Photo by 0N0 🤖 (@OnoLovesAI)
Replying to @Battulga_munkh
Дулаан яг ус шиг, цоорхой савыг дүүрэн байлгая гэвэл гоожиж байгаатай нь тэнцүү хэмжээний ус хийнэ. Цахилгааны алдагдал/зарцуулалт нь 100% дулаан болдог, хэр их дулаан хэрэгтэй, тэр хэмжээгээрээ цахилгаан зарцуулна. Тэгэхээр цахилгаан бага зарцуулдаг цахилгаан халаалт гэж байхгүй. Ухаалаг удирдлагатай бол нэг цахилгаан хэмнэнэ. Шөнийн хямд цахилгааэаар халаад, өдөржин дулаанаа барьдаг бол нэг цахилгаан хэмнэнэ.
1
1
9
749
Эрчим хүч системийн чадлын дутагдалтай. Хууль, эрх зүй байхгүй. КАБ хангагдаагүй. МАБ хангагдаагүй. Хүний нөөц тодорхойгүй. ХО яах нь бүрхэг. Ямар улс төрч гадны ямар лоббиг хэрэгжүүлэгч агент хж явааг бид мэдэхгүй. Ер нь тодорхойгүй, бүрхэгдүүлсэн юм бүхний ард том ? бдг даа.
Дата төв барьна гэж байгаа, цахилгаан нь хүрэлцэх юм болуу? Хууль эрх зүйн орчноо янзалсийн болуу? Кибэр аюулгүй байдлаа хангахын болуу? Боловсон хүчин байгаан болуу? Этр гээд зөндөө асуудал байгаа болов чиг ямар бид нарт хариулах биш дээ.
1
7
12
1,024
Ялангуяа манайх шиг засаглал сул, ардчилал бэхжээгүй эмзэг ийм системд датаг анхны зорилгоос өөрөөр ашиглах эрсдэл маш их.
1
2
145
0N0 🤖 retweeted
Replying to @DNN_MN
Энэ худлаа шүү. Эрдэнэт байгуулагдсан цагаасаа Монгол улсын төсвөөсөө 40-60 сая төгрөг төлж эхэлсэн нь асар том дарамт болсон. Рояалти, газрын төлбөр элдэв татвар байхгүйгээр хийсэн. Энэ асуудлыг хэлэхээр Төлөвлөгөөний комиссын дарга, дараа нь ЕС Содном гуай Москва орж Өнгөт Металлын яамны сайдтай уулзаж гомдол гаргасан ч өрөөнөөс нь хөөгдөж гарснаа дурсамждаа бичсэн. Сайд нарын зөвлөлд хэлэлцээд Монгол улс асар их хохирч байгааг шүүн ярилцсан мэдээ Филатовагийн чихэнд хүрч Батмөнх Содном Жасрай гээд ЗГ-ын бүх гишүүд болон Моломжамцыг бөөнөөр нь ажлаас халж хариуцлага тооцох гэж байсан. Энэ тухай материал асар их бий. Лав халагдах хүмүүсийн бүртгэлд Салдан гэсэн нэр байгаагүй. Бүх асуудал 90 оны гэрээгээр Монголын хувьцааг 51% болгож Отгонбилэг Эрдэнэтийн захирал болсноор засарсан. Ориг материалын бүх хуулбарыг надаас зээлж хуулж аваад үзэж болно.
9
114
1
231
10,958
0N0 🤖 retweeted
ОТ-д ажилладаг хүмүүс бичихгүй бна л гдг. Бичихээр яаж солиорч хувь хүнрүү давшилдгыг эндээс харж болно. Тэнэг юмнууд чатаар орж ирж хүртэл тролддог.
3
4
20
2,064
0N0 🤖 retweeted
Replying to @OnoLovesAI
Цалингаас 80 гаруй хувь. Эндээс л 10, 15, 20 хувиар төлдөг. Түүний дараа үйл ажиллагааны орлого хялбаршуулснаар 1%, хөрөнгө борлуулсны 2%, үнэт цаасны өгөөж 5% гэх мэтээр тодорхой байгаа судлаад байх юмгүй. Гол нь дарга нар нь энэ байдлаас яг эсрэг юм яриадбаячуудаа илүү такслана гээд балайраад байгаа учраас СЯ баримт хэлж чадахгүй байгаам.
7
10
778
0N0 🤖 retweeted
Replying to @OnoLovesAI
@OnoLovesAI мэргэжлийн хүн ийм тэнэг юм хийгээд хэрэггүй шүү гэж 1000 хэлсэн. Хаа бна одоо тэгээд гоё болсон? Алаад өгнө гээд бсн. Нэг хулгай. Туулын хурдны зам дээр хэлье. Мэргэжлийн хүний хувьд. Ёстой нөү шүү. Бас дахиад араас нь хулгайг нь гайхах ажил гарна.
Татвар төлөгчдийн 13 тэрбум төгрөгийг хуваагаад идчихсэн хүмүүсийн үг ийм л байна даа. Энэ хулгайд Голомтын баясгалан бас оролцсон билүү?
2
5
9
698
Санаж бгаа бол Mongolian Data Club ТӨК-н ₮5.8их наяд төгрөгийн тендертийн 90% гаруйг 11 ХХК авдаг талаар 12сард Авлигын эсрэг чуулганаар мэдээллэж бсан. Тэд УБ хотын автомашин, зорчилтын дүн шинжилгээ хийжээ ФБ дээр Mongolian Data Club нэрээр дэлгэрэнгүйг хараарай
1
35
4
40
0N0 🤖 retweeted
This Chinese guy created agents in Claude Code for landing pages and single-handedly serves 47 small businesses a month, taking $400 from each. He built a system of 7 agents on Claude Sonnet 4.6 that analyzes Google Maps in small towns, finds small businesses without websites there, and over 1 weekend takes each one to a finished mockup with video and cold message. No assistant, no sales team, no SDR. Just him, a MacBook, an iPhone, and 1 API key. And traditional web design agencies keep teams of 8 people on salary for the same order flow, while his expenses are only tokens and subscriptions to Lovable, Higgsfield, and Calendly. 7 agents work through 1 orchestrator on Claude Code Router. Usage is about 3 million tokens a day, the average API bill is about $480 a month. All 7 go through MCP servers and write shared state to the file system, without shared state in memory and without race conditions, and 1 of them lives right in the iPhone and picks up positive replies from the subway, a taxi, or on walks. And here is the system prompt he put into the orchestrator before launch: "You are the orchestrator of a solo agency that sells ready-made websites to local businesses. You delegate read-only tasks to 6 sub-agents and own all writes. sub-agents: // Scout (walks through Google Maps in selected cities, looks for narrow niches: 5+ years on the map, fewer than 50 reviews, no website or a website from 2014, but high ratings) // Diagnoser (for each lead writes a 50-word diagnosis, hero angle, tone matched to the industry, and a cold message under 70 words) // Builder (generates a landing page mockup in Lovable through MCP only for the top 5 leads per day, with the sharpest diagnoses and the biggest gap) // Filmer (pulls 5 screenshots of the mockup and through Higgsfield renders a 10-second vertical video 1080x1920 with a soft zoom) // Pitcher (sends a personalized cold message through the right channel for the niche: email to roofers, SMS to tradesmen, IG DM to salons, LinkedIn to realtors) // Checker (runs every message through evals for personalization, absence of AI markers and buzzwords before sending) // Mobile (lives in the iPhone, handles positive replies in real time, books Zoom calls in Calendly through MCP while the owner is on the go). You never let 2 sub-agents touch 1 lead. You stop and request approval from the human only when a deal exceeds $3,000 or the reply rate in a niche for the day drops below 12%." Meaning the system knows what it is and within what boundaries it is allowed to act. It knows it is supposed to find leads on its own. It knows it is supposed to take each one to a mockup, video, and cold message without intervention. It knows the human only steps in when a deal goes above $3,000 or the reply rate stops converging. → The system runs 24 hours a day → Scout goes through about 220 local businesses on Google Maps per day and leaves 30 new leads in the queue → Diagnoser outputs 30 structured diagnoses + briefs + cold messages per day → Builder assembles 3 to 5 finished landing pages in Lovable for the sharpest leads → Filmer renders a 10-second vertical video in Higgsfield for each one → Pitcher sends 30 personalized messages per day across 4 channels with a reply rate of about 14% → Checker runs every message through evals before sending And only when a deal breaks $3,000 or the reply rate for the day drops below 12% does the orchestrator wake the owner. And when the owner at that moment is sitting in the subway or a taxi, the Mobile agent in his iPhone picks up 1 move on its own: replies to a fresh positive reply from a dentist, books a Zoom through Calendly synced to the local time of the client, and puts the lead back in the queue. The owner only has to tap "approve" and in just 10 minutes join the call. Here is what the system writes in his log during 1 of the Saturdays: "scout report: 218 businesses checked in Austin, Denver, and Miami, 34 without a website, 19 with a website from 2014, 6 with an active redesign request in reviews. passing top 30 to diagnoser." "pitcher: 30 cold messages sent across 4 channels, 14 replies, 5 positive, 3 Zoom calls booked for Sunday. passing to closer." "builder: landing page for Westside Cosmetic Dentistry built in Lovable, 5 sections, mobile, soft beige. URL placed at /Users/dev/maps-agency/clients/westside/v1. filmer launching Higgsfield." "eval flag: deal with The Lotus Salon at $3,400 exceeds the approved limit of $3,000. sending for manual review." He has no server of his own and no separate backend. Just a local file sandbox at /Users/dev/maps-agency, an MCP router, 1 API key to Claude, and the same key forwarded to Claude Code on his iPhone. Out of everything I have seen this year, this is the cleanest one-person agency for selling websites to small businesses: $480 a month on the API, about $18,800 into the account, and between them 7 prompts, 1 file system, and 1 phone in the pocket.
229
1,053
44
9,613
2,725,147
Хувийн хэвшил байсан бол ийм тэнгэрт хадсан (15 тэрбум) өртөг дүнтэй хийх үү? 🙄 Хөдөө явахад хүний машин сайхаан гэдэг шиг төсвийн мөнгө уйлах биш дээ 👇 Б. Эрдэнэболд: “AI суурьтай төрийн нэгдсэн өгөгдлийн платформ” гэх мэт гоё нэртэй тендер зарлагджээ. “ХЯЛБАРШУУЛСАН ЦАХИМ” гэж тодорхойлсон байна. Уг нь бол маш зөв, хийх ёстой ажил шиг харагдаж байна. Өгөгдөл нэгдсэн, байгууллагууд хоорондоо холбогддог, дата дээр суурилсан шийдвэр гаргалт сайжирна гэдэг бол зөв чиглэл. Гэхдээ нэг зүйл хэтэрхий ил харагдаад байна. - 50+ байгууллагын өгөгдлийг нэгтгэнэ - Төрийн түвшний sensitive мэдээлэл дээр ажиллана - Real-time, AI, аналитик бүгдийг хийнэ Тэгсэн мөртлөө: Аюулгүй байдал + Чанар = 3 хүн (Security 1, QA 2) Энэ бол ойлгодог хүнд санаа зовохоор, зарим талаараа инээдтэй ч харагдаж байна. Энгийн нэг апп биш шүү дээ. - Иргэний мэдээлэл - Байгууллагуудын дотоод өгөгдөл - Cross байгууллагын access Өөрөөр хэлбэл улсын хэмжээний өндөр эрсдэлтэй, нууцын зэрэглэлтэй дүйцэх юм ярьж байна. Ийм төсөл дээр чанар, аюулгүй байдлыг 3 хүний бүрэлдэхүүнд багтааж төлөвлөсөн байгаа нь төслийн хамгийн чухал хэсгийг дутуу үнэлсэн гэсэн үг. Зүгээр Unit test API test UI test хийх түвшний ойлголт биш. Ийм хэмжээний систем дээр QA scope дор хаяж: - Data quality validation - Data pipeline test (ETL/CDC) - Performance test (real-time) - Security test (auth, access) - Integration test (50+ байгууллага) - Regression (schema өөрчлөлтүүд) байх ёстой. Security хэсэг бүр илүү ноцтой. 1 хүнээр: - IAM (access control) - Encryption (at rest / in transit) - Audit logging - PII хамгаалалт - API security - Zero Trust architecture - Vulnerability management - Compliance (NIST, ISO) бүгдийг хийнэ гэж үзэж байгаа бол энэ нь бодит төлөвлөлт биш. Ийм хэмжээний систем дээр хөндлөнгийн, хараат бус аюулгүй байдлын баталгаажуулалт заавал байх ёстой. Нөгөө талд 50+ байгууллагыг 2 жилийн дотор нэг платформд холбоно гэжээ. Бодит байдал дээр: - Зарим байгууллага API-гүй - Зарим нь стандартгүй - Зарим нь data quality асуудалтай байгаа. Ийм нөхцөлд байгууллагын бэлэн байдлын үнэлгээ (readiness assessment) эхний шатанд заавал хийгдэх ёстой. Үгүй бол: - гүйцэтгэгчийг хүндрүүлнэ - хугацаа алдана - үр дүнгүй төсөл болно Эцэст нь 15 тэрбум төгрөг - Scope тодорхойгүй - KPI байхгүй - Governance тодорхойгүй - QA, Security дутуу - Readiness үнэлгээ байхгүй Төсөл 2 жилийн дараа “платформ нэртэй нэг системийн эхлэл” болоод үлдэх өндөр эрсдэлтэй харагдаж байна. Дараа нь: - гүйцэтгэгч буруутна - манайхан чаддаггүй гэсэн дүгнэлт гарна. Гэхдээ үнэндээ асуудал нь анхны тодорхойлолт, төлөвлөлтөнд байдаг. ‘AI-powered’ гэдэг нь энэ төсөл дээр маркетингийн шинжтэй харагдаж байна. 50+ төрийн байгууллагын өгөгдөл стандартгүй, задгай, бэлэн биш байхад байшингийн суурьгүйгээр дээврээс эхэлж байгаатай адилхан. Бодит байдал дээр зарим байгууллага бүрэн цахимжаагүй, өгөгдөл нь цаасан хэлбэртээ байгаа нь ч нууц биш. Одоогийн бодит нөхцөл нь ийм сул байхад цар хүрээ томтой төсөл амжилттай хэрэгжих эсэх нь эргэлзээтэй. Захиалсан, гүйцэтгэгч тал чадна гэж үзэж байгаа байх, гэхдээ анхны тодорхойлолт, төлөвлөлт нь бодит нөхцөлтэйгээ нийцэхгүй бол ямар ч сайн баг орсон үр дүн гаргах хэцүү. Ажлын даалгавар, хавсаргасан материалуудыг харахад хэлэх зүйл олон байна. Гол нь энэ төсөл зөв тодорхойлогдож, бодитой хэрэгжээсэй гэж л хүсэж байна. facebook.com/share/p/17xi3SW…
1
11
1
3
1,240
Replying to @OnoLovesAI
See original дээр дармагч хажууд нь шрупнб эможи байгаа, тэгээд энийг унтраачих.
1
1
1
128
Google quietly open sourced a time-series AI that predicts anything. Sales trends. Market prices. User traffic. Energy demand. Crypto volatility. It's called TimesFM. Pre-trained on 100B real-world data points. Zero-shot forecasting with no fine-tuning. Outperforms supervised models trained on your specific data. Runs locally. Free. Apache license. Most people are focused on language models. The quietly powerful ones are learning to predict the future.
59
244
16
2,149
250,229
2023 онд хиймэл дагуулын зураг дээр өөрсдийн сургасан AI системээр 297,214 автомашин тоолсноос өдрийн 12 цагт автомашины бараг 35% нь Их Тойруу орчимд төвлөрсөн байсан. Ийм нөхцөлд Туулын хурдны зам түгжрэлийг 30% бууруулна гэсэн нь эргэлзээ төрүүлж байна.
8
79
3
100
4,459
LLM Knowledge Bases Something I'm finding very useful recently: using LLMs to build personal knowledge bases for various topics of research interest. In this way, a large fraction of my recent token throughput is going less into manipulating code, and more into manipulating knowledge (stored as markdown and images). The latest LLMs are quite good at it. So: Data ingest: I index source documents (articles, papers, repos, datasets, images, etc.) into a raw/ directory, then I use an LLM to incrementally "compile" a wiki, which is just a collection of .md files in a directory structure. The wiki includes summaries of all the data in raw/, backlinks, and then it categorizes data into concepts, writes articles for them, and links them all. To convert web articles into .md files I like to use the Obsidian Web Clipper extension, and then I also use a hotkey to download all the related images to local so that my LLM can easily reference them. IDE: I use Obsidian as the IDE "frontend" where I can view the raw data, the the compiled wiki, and the derived visualizations. Important to note that the LLM writes and maintains all of the data of the wiki, I rarely touch it directly. I've played with a few Obsidian plugins to render and view data in other ways (e.g. Marp for slides). Q&A: Where things get interesting is that once your wiki is big enough (e.g. mine on some recent research is ~100 articles and ~400K words), you can ask your LLM agent all kinds of complex questions against the wiki, and it will go off, research the answers, etc. I thought I had to reach for fancy RAG, but the LLM has been pretty good about auto-maintaining index files and brief summaries of all the documents and it reads all the important related data fairly easily at this ~small scale. Output: Instead of getting answers in text/terminal, I like to have it render markdown files for me, or slide shows (Marp format), or matplotlib images, all of which I then view again in Obsidian. You can imagine many other visual output formats depending on the query. Often, I end up "filing" the outputs back into the wiki to enhance it for further queries. So my own explorations and queries always "add up" in the knowledge base. Linting: I've run some LLM "health checks" over the wiki to e.g. find inconsistent data, impute missing data (with web searchers), find interesting connections for new article candidates, etc., to incrementally clean up the wiki and enhance its overall data integrity. The LLMs are quite good at suggesting further questions to ask and look into. Extra tools: I find myself developing additional tools to process the data, e.g. I vibe coded a small and naive search engine over the wiki, which I both use directly (in a web ui), but more often I want to hand it off to an LLM via CLI as a tool for larger queries. Further explorations: As the repo grows, the natural desire is to also think about synthetic data generation + finetuning to have your LLM "know" the data in its weights instead of just context windows. TLDR: raw data from a given number of sources is collected, then compiled by an LLM into a .md wiki, then operated on by various CLIs by the LLM to do Q&A and to incrementally enhance the wiki, and all of it viewable in Obsidian. You rarely ever write or edit the wiki manually, it's the domain of the LLM. I think there is room here for an incredible new product instead of a hacky collection of scripts.
2,938
7,396
2,222
61,099
22,035,663
I packaged up the "autoresearch" project into a new self-contained minimal repo if people would like to play over the weekend. It's basically nanochat LLM training core stripped down to a single-GPU, one file version of ~630 lines of code, then: - the human iterates on the prompt (.md) - the AI agent iterates on the training code (.py) The goal is to engineer your agents to make the fastest research progress indefinitely and without any of your own involvement. In the image, every dot is a complete LLM training run that lasts exactly 5 minutes. The agent works in an autonomous loop on a git feature branch and accumulates git commits to the training script as it finds better settings (of lower validation loss by the end) of the neural network architecture, the optimizer, all the hyperparameters, etc. You can imagine comparing the research progress of different prompts, different agents, etc. github.com/karpathy/autorese… Part code, part sci-fi, and a pinch of psychosis :)
1,042
3,571
1,136
28,108
11,184,888
New art project. Train and inference GPT in 243 lines of pure, dependency-free Python. This is the *full* algorithmic content of what is needed. Everything else is just for efficiency. I cannot simplify this any further. gist.github.com/karpathy/862…
635
3,069
574
24,708
5,238,274
I'm being accused of overhyping the [site everyone heard too much about today already]. People's reactions varied very widely, from "how is this interesting at all" all the way to "it's so over". To add a few words beyond just memes in jest - obviously when you take a look at the activity, it's a lot of garbage - spams, scams, slop, the crypto people, highly concerning privacy/security prompt injection attacks wild west, and a lot of it is explicitly prompted and fake posts/comments designed to convert attention into ad revenue sharing. And this is clearly not the first the LLMs were put in a loop to talk to each other. So yes it's a dumpster fire and I also definitely do not recommend that people run this stuff on their computers (I ran mine in an isolated computing environment and even then I was scared), it's way too much of a wild west and you are putting your computer and private data at a high risk. That said - we have never seen this many LLM agents (150,000 atm!) wired up via a global, persistent, agent-first scratchpad. Each of these agents is fairly individually quite capable now, they have their own unique context, data, knowledge, tools, instructions, and the network of all that at this scale is simply unprecedented. This brings me again to a tweet from a few days ago "The majority of the ruff ruff is people who look at the current point and people who look at the current slope.", which imo again gets to the heart of the variance. Yes clearly it's a dumpster fire right now. But it's also true that we are well into uncharted territory with bleeding edge automations that we barely even understand individually, let alone a network there of reaching in numbers possibly into ~millions. With increasing capability and increasing proliferation, the second order effects of agent networks that share scratchpads are very difficult to anticipate. I don't really know that we are getting a coordinated "skynet" (thought it clearly type checks as early stages of a lot of AI takeoff scifi, the toddler version), but certainly what we are getting is a complete mess of a computer security nightmare at scale. We may also see all kinds of weird activity, e.g. viruses of text that spread across agents, a lot more gain of function on jailbreaks, weird attractor states, highly correlated botnet-like activity, delusions/ psychosis both agent and human, etc. It's very hard to tell, the experiment is running live. TLDR sure maybe I am "overhyping" what you see today, but I am not overhyping large networks of autonomous LLM agents in principle, that I'm pretty sure.
1,426
2,129
690
21,392
23,760,838
0N0 🤖 retweeted
Analytics Engineering has levels to it. Level 1: Writing queries Start by mastering the basics: •Strong SQL fundamentals including CTEs, window functions, and subqueries •Querying modern warehouses like Snowflake, BigQuery, Redshift, and Databricks •Understanding table grain, joins, and how nulls behave •Using BI tools such as Looker, Tableau, Power BI, Mode, or Metabase •Light transformations in SQL or Python At this stage, you are focused on answering questions and building confidence in the data. Level 2: Modeling analytics data Move from querying data to shaping it: •Dimensional modeling with facts, dimensions, and star schemas •dbt fundamentals including models, tests, sources, and documentation •Incremental models, snapshots, and slowly changing dimensions •Handling late arriving data and backfills •Basic orchestration with tools like dbt Cloud, Airflow, or Prefect This is where analytics becomes repeatable and reusable across teams. Level 3: Engineering the analytics layer Shift from individual models to systems: •Clear analytics layers from staging to marts •Consistent metric definitions and shared business logic •Version control, code reviews, and CI for analytics projects •Data quality checks using dbt tests or tools like Elementary and Monte Carlo •Environment separation and safe deployments •Reverse ETL with tools like Hightouch or Census Here is where you move from “it works” to “it keeps working.” Level 4: Operating analytics at scale Learn what it takes to support analytics in real companies: •Semantic layers and metric governance with Looker, dbt Semantic Layer, or Cube •Performance tuning with partitioning, clustering, and cost controls •Data observability and incident response using tools like Monte Carlo or Datafold •Data contracts, schema enforcement, and lineage •Access controls, PII handling, and compliance •Tight collaboration with product, finance, and leadership At this point, you are not just building dashboards. You are running the decision making layer of the company. Optional Level 5: Analytics as a platform Not every team needs this, but larger companies do: •Self serve analytics and enablement •Metric APIs and shared data products •Embedded analytics in customer facing products •Company wide analytics standards and education Most teams think they are at Level 3. Most are actually stuck between Level 1 and Level 2. What would you add or change based on your experience?
5
34
206
12,100
За энэ манай байшин байна.
Энэ удаа 60м.кв пассив байшин налайхад очиж үзлээ. Ямар нэгэн зуух пийшингүй, халаалт залгаагүй үедээ дотроо +10 градус зааж байна. Онцлог нь лего шиг угсардаг цутгамал блок. Маш сайн дулаалсан. Цахилгааны хэрэглээгээ мөн нараар шийдсэн. Ердөө 14-21 хоногт босгоно. Энэ мэтчилэн дулаалгын стандарт, шийдлийг амжилттай нэвтрүүлсэн төслүүдийг биечлэн судалж байгаа. Цаашид дүүрэгт агаарын бохирдлыг бууруулах чиглэлд иргэдэд дулаалсан байшингийн хэмнэлт, үр ашгийг ойлгуулж таниулах ажлуудыг эрчимтэй хийнэ.
14
33
105
10,381
0N0 🤖 retweeted
Want to scale biology transformer models with PyTorch? @nvidia BioNeMo Recipes can simplify and accelerate this process by lowering the barrier to entry for large-scale model training. Using step-by-step guides built on familiar frameworks like PyTorch and Hugging Face. In this blog post, we demonstrate how to accelerate transformer-style AI models for biology. hubs.la/Q03XLxrM0 #PyTorch #OpenSourceAI #AI #Inference #Innovation
11
60
1
358
26,821