HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
dioptra-ai
katiml
Shell2023–2023
dioptra-ai / katiml

katiml

Discover this repository through its Hacker News conversations.

2Distinct people
2Mentions
0Explicit recommenders
56GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2023-06-07 18:11:22 UTC to 2023-06-08 13:43:56 UTC.

012023-06-07 18:00:00 UTC to 2023-06-07 19:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJun 7, 18:002023-06-07 19:00:00 UTC to 2023-06-07 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-07 20:00:00 UTC to 2023-06-07 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-07 21:00:00 UTC to 2023-06-07 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-07 22:00:00 UTC to 2023-06-07 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-07 23:00:00 UTC to 2023-06-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-08 00:00:00 UTC to 2023-06-08 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-08 01:00:00 UTC to 2023-06-08 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-08 02:00:00 UTC to 2023-06-08 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-08 03:00:00 UTC to 2023-06-08 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 8, 03:002023-06-08 04:00:00 UTC to 2023-06-08 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-08 05:00:00 UTC to 2023-06-08 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-08 06:00:00 UTC to 2023-06-08 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-08 07:00:00 UTC to 2023-06-08 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-08 08:00:00 UTC to 2023-06-08 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-08 09:00:00 UTC to 2023-06-08 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-08 10:00:00 UTC to 2023-06-08 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-08 11:00:00 UTC to 2023-06-08 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-08 12:00:00 UTC to 2023-06-08 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-08 13:00:00 UTC to 2023-06-08 14:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJun 8, 13:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jun 7, 18:002023-06-07 18:00:00 UTC2023-06-07 19:00:00 UTC110
Jun 7, 19:002023-06-07 19:00:00 UTC2023-06-07 20:00:00 UTC000
Jun 7, 20:002023-06-07 20:00:00 UTC2023-06-07 21:00:00 UTC000
Jun 7, 21:002023-06-07 21:00:00 UTC2023-06-07 22:00:00 UTC000
Jun 7, 22:002023-06-07 22:00:00 UTC2023-06-07 23:00:00 UTC000
Jun 7, 23:002023-06-07 23:00:00 UTC2023-06-08 00:00:00 UTC000
Jun 8, 00:002023-06-08 00:00:00 UTC2023-06-08 01:00:00 UTC000
Jun 8, 01:002023-06-08 01:00:00 UTC2023-06-08 02:00:00 UTC000
Jun 8, 02:002023-06-08 02:00:00 UTC2023-06-08 03:00:00 UTC000
Jun 8, 03:002023-06-08 03:00:00 UTC2023-06-08 04:00:00 UTC000
Jun 8, 04:002023-06-08 04:00:00 UTC2023-06-08 05:00:00 UTC000
Jun 8, 05:002023-06-08 05:00:00 UTC2023-06-08 06:00:00 UTC000
Jun 8, 06:002023-06-08 06:00:00 UTC2023-06-08 07:00:00 UTC000
Jun 8, 07:002023-06-08 07:00:00 UTC2023-06-08 08:00:00 UTC000
Jun 8, 08:002023-06-08 08:00:00 UTC2023-06-08 09:00:00 UTC000
Jun 8, 09:002023-06-08 09:00:00 UTC2023-06-08 10:00:00 UTC000
Jun 8, 10:002023-06-08 10:00:00 UTC2023-06-08 11:00:00 UTC000
Jun 8, 11:002023-06-08 11:00:00 UTC2023-06-08 12:00:00 UTC000
Jun 8, 12:002023-06-08 12:00:00 UTC2023-06-08 13:00:00 UTC000
Jun 8, 13:002023-06-08 13:00:00 UTC2023-06-08 14:00:00 UTC110

What Hacker News says

2 sources
farahg·Jun 7, 2023Submission

Show HN: Open-source vector & data lake to debug, curate and version AI data

Hi HN! I’m Farah, co-founder of Dioptra.ai. We just open sourced katiML (https://github.com/dioptra-ai/katiml) this week and wanted to get your take. katiML is a vector+data lake to debug, curate and version AI data. With katiML, teams avoid the “garbage in, garbage out” effect by taking control over the quality of their data. They quickly and effectively curate high quality data for training, fine-tuning, and fixing hallucinations and edge cases. Features include: - Data Curation: interactive embedding visualization and similarity search, mislabeling and hallucination scores as well as SOTA Active Learning miners. - GenAI 4 explainability: uncover drift and bias in your data with multi-modal foundational models that describe in human language what’s in your data. - ML Data Lake: zero copy, highly efficient ML data lake to store and query
Read the rest
any ML data (vectors, metadata etc). - Data Versioning: to track changes in datasets, prompts, and model performance; and pinpoint the causes behind those changes. Check out our github repo(https://github.com/dioptra-ai/katiml), documentation(https://dioptra.gitbook.io/dioptra-doc/EIKhoPaxsbOt062jkPon/) and new slack community channel. Here is a video to show you how we use GenAi 4 explainability(https://www.loom.com/share/c6916272b9914894bddd1a21df0321b4). We'd love to hear about your experiences with iterating on your data to improve models, the challenges you faced, and how katiML could prove useful to your efforts. Let us know what you think we can do better or differently. Looking forward to your comments!
12 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.