LynxKite is a complete graph data science platform for very large graphs and other datasets. It seamlessly combines the benefits of a friendly graphical interface and a powerful Python API.
Based on the "Science and Data Analysis" category.
Alternatively, view LynxKite alternatives based on common mentions on social networks and blogs.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of LynxKite or a related project?
LynxKite is a complete graph data science platform for very large graphs and other datasets. It seamlessly combines the benefits of a friendly graphical interface and a powerful Python API.
LynxKite is under active development. Check out our Roadmap to see what we have planned for future releases.
Quick try:
docker run --rm -p2200:2200 lynxkite/lynxkite
Setup with persistent data:
docker run \
-p 2200:2200 \
-v ~/lynxkite/meta:/metadata -v ~/lynxkite/data:/data \
-e KITE_MASTER_MEMORY_MB=1024 \
--name lynxkite lynxkite/lynxkite
If you find any bugs, have any questions, feature requests or comments, please file an issue or email us at lynxkite@lynxkite.com.
You can install LynxKite's dependencies (Scala, Node.js, Go) with Conda.
Before the first build:
tools/git/setup.sh # Sets up pre-commit hooks.
conda env create --name lk --file conda-env.yml
conda activate lk
cp conf/kiterc_template ~/.kiterc
We use make for building the whole project.
make
target/universal/stage/bin/lynxkite interactive
We have test suites for the different parts of the system:
Backend tests are unit tests for the Scala code. They can also be executed with Sphynx as the
backend. If you run make backend-test it will do both. Or you can start sbt and run
testOnly *SomethingTest to run just one test. Run ./test_backend.sh -si to start sbt with
Sphynx as the backend.
Frontend tests use Protractor to simulate a user's actions
on the UI. make frontend-test will build everything, start a temporary LynxKite instance and run
the tests against that. Use xvfb-run for headless execution. If you already have a running
LynxKite instance and you don't mind erasing all data from it, run npx gulp test in the web
directory. You can start up a dev proxy that watches the frontend source code for changes with
npx gulp serve. Run the test suite against the dev proxy with npx gulp test:serve.
Python API tests are started with make remote_api-test. If you already have a running
LynxKite that is okay to test on, run python/remote_api/test.sh. This script can also run a
subset of the test suite: python/remote_api/test.sh -p *something*
*Note that all licence references and agreements mentioned in the LynxKite README section above
are relevant to that project's source code only.
Do not miss the trending, packages, news and articles with our weekly report.