Cognitive Computations

community

https://erichartford.com

erhartford

ehartford

Activity Feed

AI & ML interests

Supervised Fine Tuning, DPO, and unalignment

Recent Activity

ehartford updated a dataset 5 days ago

cognitivecomputations/OpenCoder-LLM_opc-sft-stage1-DolphinLabeled

ehartford new activity 6 days ago

cognitivecomputations/Dolphin3.0-Llama3.1-8B:Tool usage

ehartford updated a dataset 6 days ago

cognitivecomputations/allenai_tulu-3-sft-mixture-DolphinLabeled

View all activity

cognitivecomputations's activity

cfahlgren1

posted an update 2 days ago

Post

1152

Wow, I just added Langfuse tracing to the Deepseek Artifacts app and it's really nice 🔥

It allows me to visualize and track more things along with the cfahlgren1/react-code-instructions dataset.

It was just added as a one click Docker Space template, so it's super easy to self host 💪

ehartford

updated a dataset 5 days ago

cognitivecomputations/OpenCoder-LLM_opc-sft-stage1-DolphinLabeled

Viewer • Updated 5 days ago • 3.01M • 31 • 6

bartowski

posted an update 6 days ago

Post

4521

Switching to author_model-name

I posted a poll on twitter, and others have mentioned the interest in me using the convention of including the author name in the model path when I upload.

It has a couple advantages, first and foremost of course is ensuring clarity of who uploaded the original model (did Qwen upload Qwen2.6? Or did someone fine tune Qwen2.5 and named it 2.6 for fun?)

The second thing is that it avoids collisions, so if multiple people upload the same model and I try to quant them both, I would normally end up colliding and being unable to upload both

I'll be implementing the change next week, there are just two final details I'm unsure about:

First, should the files also inherit the author's name?

Second, what to do in the case that the author name + model name pushes us past the character limit?

Haven't yet decided how to handle either case, so feedback is welcome, but also just providing this as a "heads up"