prismadic / magnet Goto Github PK

it's just the data, it should be meta like origin filename, etc. (need to use JSON from NATS documentation: they require a schema)

rest is here

create mega class hierarchy

basically there should be built in callbacks for the NATS magnet.ic.field.Resonator other than print() and pymongo's insert_document could be first

need to add params for instruction prepend, whatever else I find.

ggml or something, there are great libraries we may depend on if they are small enough

Seems n->∞ duplicates are observed after indexing and using retrieval later.

Since these are processed directly from NATS using a durable consumer session, there must be an issue with the distributed messaging protocol or perhaps the inserts.

Another possibility is duplicates are created as a part of the processing part of the workflow but since the number of them seems to increase without relation to the order in the stream, this seems unlikely.

put this in as _f argument and add levels for info warn fatal.

should have a default writable log path for unix machines minimum with timestamps prior to what otherwise would have just been printed to stdout

#11

title

https://github.com/ConnectEverything/nats-by-example/tree/main/examples

what a coincidence:

https://milvus.io/blog/milvus-embraces-nats-messaging.md

All data entries going into NATS should be hashed.

spit stream volume equal lengths, create new NATS stream for jobs with pull_subscribe consumer model using index as job criteria (and other criteria)

NATS has integrated a lot more connection parameters and likely some in other classes besides the client.

Should implement all of them.

can query on the fly on the node with the magnet.ron llm but cannot query remotely to a distributed llm node

title

NATS has improved the object meta data for the consumer/producers of data, should absolutely be used for basic bandwidth transparency

Make it possible to do accelerated embedding on Macs.

title