An acronym for Reflexive Persistent System. This is an ambitious research project (still unfunded, in 2019 it is a hobby project; also very risky!), done on spare time with an open science mindset and ethics.
We have in 2019 a lot of ideas, but not much code (on gitlab). Done by passionate developers on their spare time. Volunteers wanted; please send an email (introducing yourself) to email@example.com (near Paris, France, homepage here) for more.
The following persons are working (at end of 2019) on RefPerSys on their spare time from their home and are the copyright owners of the embryonic software.
(born in 1959, PhD in AI),
|firstname.lastname@example.org||starynkevitch.net/Basile/||project leader and architect|
West Bengal, India
Madhya Pradesh, India
A draft document giving some design ideas is downloadable as refpersys-design.pdf. We are improving it in 2019.
The currently existing (in 2019, on gitlab) code base is a bit disappointing, even to the Refpersys team. But we have a lot of fun doing it. It is constantly improving, publicly available, still unreleased, α-stage.
We list here some uncommon dependencies, and give a source tarball (compressed by bzip2) for them.
The RefPerSys software depends on many other common stuff, notably a recent GCC compiler for C++17, a recent Linux kernel and C standard library (e.g. GNU glibc or Musl Libc), and the Qt graphical toolkit. A multi-core x86-64 Linux computer with more than 16Gbytes of RAM and at least 100Gbytes of free disk space is recommended.
α-stage embryonic free
software source code of RefPerSys is on gitlab.com/bstarynk/refpersys.
Only the master
branch is interesting. Other git branches are
obsolete or might not even compile.
We practically are using git as a
centralized version control system, because we are very
few and sill don't understand well in 2019 how a genuinely
version control system could play nice with a
reflexive, orthogonally persistent,