Tablicious provides tabular/relational data structures for Octave. You can think of it as "pandas for Octave".
WARNING: This library is currently beta quality. Please do not use it in any production or business code! Seriously!! |
---|
This package attempts to provide a set of mostly-Matlab-compatible implementations of the table class and related structures and functions. It provides:
- A
table
array class, and related functions.- (That's kind of our whole thing.)
datetime
,string
, andcategorical
array classes.- (Because they're pretty useful when working with tables, and base Octave doesn't have them yet.)
- Auxiliary functions related to those classes.
It currently does not provide, but we would like to maybe add at some point:
timetable
- Table I/O, such as
readtable
,writetable
, andcsvread
/dlmread
table
support
Tablicious 0.4.x requires Octave 7.0 or newer. It may well work on earlier versions, but is not really tested against them.
Tablicious does not require the Octave Forge Statistics package, but you will probably want it, because Statistics supplies functions that are frequently useful for data analysis in a tabular context. In particular, ismissing()
and the related missing-filling functions are useful, and the Statistics package supplies the general implementation of them.
To get started using or testing this project, install it using Octave's pkg
function:
pkg install https://github.com/apjanke/octave-tablicious/releases/download/v0.4.4/tablicious-0.4.4.tar.gz
pkg load tablicious
If you want to hack on the Tablicious code itself, set it up like this:
- Clone the repo
git clone https://github.com/apjanke/octave-tablicious
- Add the
inst/
directory from the cloned repo to your Octave path withaddpath
.
That should get everything working except for time zone conversions inside datetime
, which require a compiled oct-file. See the developer doco in the repo for that.
Once you have Tablicious installed, the user manual will show up in the Octave GUI’s documentation browser.
You can also run help <foo>
or doc <foo>
for any of the classes or functions in Tablicious.
The documentation for Tablicious can be viewed online at https://apjanke.github.io/octave-tablicious. That site has the Tablicious User Guide containing the API reference, plus some additional general and developer-oriented documentation, and alternate formats of the User Guide. See the main doco page there for details.
Developers, especially see the Developer Notes and Design and Justification pages there, which discuss how and why this library is written. There's a TODO page that lists what might be coming. Also see CONTRIBUTING if you would like to contribute to this project.
Within this repo, you can see all that in the docs/
directory for notes on this project. It's a local copy of the GitHub Pages site.
See CONTRIBUTING.md for more details.
To avoid issues with the Matlab license's Non-Compete clause, this project needs to be developed entirely using Octave, and not using Matlab at all, including for testing or benchmarking purposes. Please do not submit any Matlab test or benchmark results, or any code produced using Matlab. And if you know anything about how the Matlab internals work, please do not tell me!
Tablicious is mostly GNU GPL v3, with some other Free and Open Source licensed code and files redistributed with it. I believe this is all compatible with redistribution as a GNU GPL licensed package, but I am not a lawyer.
The main code of Tablicious is licensed under the GNU GPL version 3. See the LICENSE
file.
The date/time portion of Tablicious includes some Unicode data files licensed under the Unicode License Agreement - Data Files and Software license. See the LICENSES/LICENSE-Unicode
file.
The test suite contains some files, specifically some table-related tests in inst/t
using MP-Test, which are BSD 3-clause licensed. See the LICENSES/LICENSE-MATPOWER
file.
The Fisher Iris dataset is Public Domain.
Tablicious is created by Andrew Janke.
Thanks to Polkadot Stingray for powering my coding sessions.
Shout out to Mike Miller for showing me how to properly structure an Octave package repo, and encouraging me to contribute.
Thanks to Sebastian Schöps for getting me more involved in Octave development in the first place, via his Octave.app project.