rosejn/cortex

Defined save-file-format

Open

#94 opened on Feb 9, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Clojure (1,269 stars) (109 forks)batch import
easierenhancementhelp wanted

Description

Cortex will need a defined save format that we believe has a decent chance for forward compatibility. We want something that is very minimal but just a bit vetted because I would like to promise that from 1.0 any data created with cortex will be useable indefinitely with future versions of cortex. This is a heavy burden if it is not treated with some respect.

Contributor guide

Tech stack
None
Domain
machine learning
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Basic Clojure knowledgeUnderstanding of serialization formatsFamiliarity with Cortex framework
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate existing save/load patterns in the Cortex codebase, particularly in the 'cortex.serialization' namespace if it exists. Review common machine learning file formats like HDF5, ONNX, or NumPy's .npy for inspiration. Propose a minimal binary or EDN based format that supports forward compatibility. The proposal should include a draft specification and discuss trade offs between simplicity and extensibility.