SPFlow

SPFlow copied to clipboard

We want to provide high-level gradient-descent based optimization procedures. The idea is that a user constructs some model structure with parameters $\theta$, has a dataset $\mathcal{D}$ and can now maximize...

braun-steven

As suggested by @felixdivo, we could use one of - https://github.com/clemtoy/pptree - https://github.com/AharonSambol/PrettyPrintTree to offer some pretty version of textual graph output. See also: https://github.com/SPFlow/SPFlow/issues/152#issuecomment-1851840617

braun-steven

Decide on and document versioning scheme

1

Conceivable are: - gut feeling versioning - [Semantic Versioning](https://semver.org/) - [Calendar Versioning](https://calver.org/overview.html)

felixdivo

It should contain the current: - Into & usage examples - Badges at the top - Plots - References to license, documentation, changelog, contribution guidelines - Citation - Contributors and...

felixdivo

This is to prevent duplicate lines of code, that could become out of sync. Connected to #101.

braun-steven

Add contribution guidelines

1

Create a proper contribution guidelines document.

braun-steven

Clean up old branches

2

1. Delete `struct-marg`, `learnspn_b_test` 2. Merge `dev_tensorly` into `development` 3. Rename `development` into `main` 4. Branch off new `development` branch from `main`

braun-steven

Remove blobs from repository history

3

As observed by @felixdivo, the repository(-history) seems to be polluted with large blobs: ```sh $ git clone [email protected]:SPFlow/SPFlow.git Cloning into 'SPFlow'... remote: Enumerating objects: 25226, done. remote: Counting objects: 100%...

braun-steven

Add visualization for simple graph structures. We should stick to networkx for ease of use. More complex structures (layers etc.) can be added in a later release (1.X.Y).

braun-steven

braun-steven